Reference

nomor slot Privacy Policy: Clear Data Choices

Our Privacy Policy explains what we collect when you open an account, sign in, browse Andar Bahar or use DANA and QRIS, and why each record is needed.

Account dataCookie choicesWallet recordsAccess requests
nomor slot nomor slot Privacy Policy: Clear Data Choices
CONTACT ROUTES

Where to ask about your stored details

A clear contact route matters when a name, phone number or wallet reference needs checking.

24/7 Support Choose the 24/7 Support route for a Privacy Policy question about account access, a…
Account help Our account help path sits close to the cashier route, making it easier to…
Receipt check For a receipt or withdrawal verification query, share the relevant date and payment rail…
DATA PRACTICE

What we protect across your account

Privacy is handled through practical account steps rather than broad promises. We separate identity details, device activity, cookie choices and payment references so a request can be checked against the right record.

Collected details

We may collect your phone number, verification result, sign-in time, device signals and payment reference when those details are needed to open, secure or service your account.

Cookie controls

Cookies can remember a session and help us understand which policy page you opened. You can clear browser cookies or adjust browser settings, though account access may ask you to sign in again.

Account security

Phone verification and sign-in checks help connect an account action to you. If a device session looks unusual, we may request an additional account step before showing wallet records.

Record retention

We keep account, cookie and payment records for the period needed for account service, dispute checks or applicable legal duties. When that purpose ends, records are removed or restricted.

Correction requests

If your account detail is inaccurate, contact us through the account help path and identify the field to change. We may verify your phone before applying a correction.

Policy contact

Privacy Policy questions can mention the account step, device path or payment rail involved. We use that context to find the relevant record without requesting your full account history.

Privacy Policy answers for Indonesian accounts

These Privacy Policy answers address the searches we hear most often before account access. They explain what happens to account details, cookies and wallet references, and show you which route to use when a record needs checking. Access remains subject to local requirements, so our wording uses depends on local law where eligibility is involved.

The Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account actions.

Phone verification connects account access with the details you submitted. We may use that step to correct a record, protect a session or confirm that a privacy request comes from the account holder.

The policy can cover activity needed to service an account, such as opening Andar Bahar, Crash Games or Fish Hunter. We use relevant records for access, security and account queries rather than unrelated purposes.

Use the account help path beside the cashier route and ask for a Privacy Policy data-access request. Include your account phone number through the secure contact path so we can verify the request.

Yes. Contact support with the specific field that needs correction, such as a phone detail or payment reference. We may complete a phone verification step before changing the stored account record.

Cookies can maintain a sign-in session and show which policy page was opened. You can clear or restrict them in your browser, but doing so may require another account sign-in.

Yes. Account access and eligibility depends on local law. Our Privacy Policy applies where local law permits, and support can explain which account or data request path is available to you.