Reference

ratu123 Privacy Policy for Your Account

ratu123 explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet recordsDevice protectionCookie choices
ratu123 ratu123 Privacy Policy for Your Account
HELP WITH YOUR DATA

Get Privacy Policy Help Directly

A clear support route matters when a phone check, wallet reference or account record looks unfamiliar.

Account privacy request Ask us to explain the personal data linked to your account, including phone verification records and sign-in details. We will confirm ownership before discussing private account information.
Wallet record check For a DANA, OVO, GoPay or QRIS reference, share the transaction date and visible reference only. We can check the record while keeping your wallet PIN and full credentials private.
Correction pathway If your contact detail or account record needs correction, send the requested change through support. We may ask for an account step or phone check before applying the update.
OUR DATA PRACTICES

What We Do With Account Data

We keep this policy practical by connecting each data use to an account action you can recognise.

Collection at account opening

When you create an account, we collect the contact and verification details needed for that step. We do not treat your browsing of Fish Hunter or Boxing Betting pages as a reason to request unrelated identity data.

Use for account safety

We use login events, phone checks and device signals to protect your account from unusual access. These checks can appear when you move from a mobile browser into the lobby or cashier path.

Cookies and browser settings

Cookies can remember a session, language setting or consent choice. You can manage or clear them through your browser controls, although removing necessary cookies may require another login step.

Payment reconciliation

A payment reference lets us match a requested DANA, QRIS, bank transfer or virtual account action with the correct account. We do not need your wallet PIN to perform that record check.

Retention and deletion requests

We keep records only as long as needed for account security, payment reconciliation, dispute handling or legal duties. You may ask what can be removed, with some records retained where a duty still applies.

Requesting policy changes

Send a correction, access or deletion request through support and identify the account contact detail. We verify that you control the account before releasing data or changing a private record.

Privacy Policy Answers Before You Join

These Privacy Policy answers address the searches we hear most often before an account is opened. You can see what we collect, why a phone or device check may occur, how wallet records are handled, and where to send a request. If your question concerns a specific account event, include its date and reference so our support path can respond with the right record.

It covers account details, phone verification, login events, device signals, cookies and payment references connected with your requests. It also explains retention, correction, deletion requests and the support path for privacy questions.

We use your phone number for account verification and account recovery steps. A phone check helps connect a private request to the correct account, and we do not ask you to share your verification code with support.

Yes. The Privacy Policy covers operational references for DANA, OVO, GoPay and QRIS requests, along with bank transfer and virtual account references. These records help us match an action without collecting your wallet PIN.

We may record device and browser signals linked to a sign-in, such as session details and security events. This helps identify unusual access when you move between a mobile browser and desktop session.

You can ask support which personal data is linked to your account and request an accessible copy where applicable. Include your account contact detail, and we will verify ownership before sharing private records.

Send the requested correction through the account support path, naming the field that is wrong and the accurate replacement. We may complete a phone or account check before changing the record.

We consider deletion when data is no longer needed for account security, payment reconciliation, dispute handling or legal duties. Some records may remain for a required period, and support can explain the reason.