Reference

Open white slot Privacy Policy Clearly

Our white slot Privacy Policy explains what we collect when you open an account, check DANA or QRIS status, and move from login to the lobby.

Account accessWallet recordsDevice choicesPolicy requests
white slot Open white slot Privacy Policy Clearly
REQUEST HELP SAFELY

Switch To The Right Privacy Contact

A clear request path helps you ask about Privacy Policy handling without sending unnecessary credentials. Start with the account reference connected to your question, describe the record you want checked, and keep wallet passwords and one-time codes private. We use the same approach for a DANA receipt, a device-access concern or a request to correct phone details.

Team online

Account access

For a Privacy Policy question about phone verification or login history, give us your account reference and the approximate event time. We can check the relevant access record without asking you to share a password, PIN or one-time code.

Wallet status

If a DANA, OVO, GoPay or QRIS receipt appears against the wrong account, send the payment reference and amount shown on your receipt. We use those details to trace the record while keeping your wallet credentials private.

Policy changes

To request correction, access or deletion of personal details, state the exact account field or record involved. We may ask for an account step that confirms ownership before changing data, and we explain the result through the same support path.

DATA HANDLING

Explore How Privacy Works On Your Device

Privacy controls matter most at the moments when your account, wallet and device meet. Our Privacy Policy separates information needed for account access from activity used to protect sessions and investigate a…

Account creation

When you open an account, we handle the contact details needed for account access and phone verification. This lets us connect your login activity with the correct account record and answer a Privacy Policy request about that record.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a cashier event to your account. We do not need your wallet password to investigate whether a receipt belongs to the right account.

Device sessions

Your phone, browser and session events can create technical records used to recognise unusual access. The same path applies whether you open Baccarat on mobile or check account settings from a desktop browser.

Cookies

Cookies and similar browser storage may keep a session active or remember a setting you selected. You can clear them in your browser, although doing so may require another login and can remove saved access preferences.

Retention

We retain account, payment and support records only for the operational, security or legal need described in our Privacy Policy. When a record is no longer needed for that purpose, our handling follows the applicable retention process.

Your requests

You can ask to access, correct or delete personal details through our support path. Include the account reference and the specific record, such as a phone field or QRIS receipt, so we can review the request without broad data sharing.

Ask About white slot Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. Each answer points to a practical account step, device choice or payment reference so you know what to prepare. Access to the service and any related request depends on local law.

The white slot Privacy Policy covers account creation, phone verification, login events, device and browser signals, cookies, payment references and support records. It also explains how you can request access, correction or deletion of personal details where local law permits.

We use phone verification before account access to connect the login with the correct account and reduce mistaken or unusual access. The Privacy Policy explains how that contact detail is handled, and you can ask us to correct an inaccurate phone record.

Yes. The policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. If a receipt needs checking, provide the payment reference and account details shown on it, never your wallet password or one-time code.

Cookies or similar browser storage can keep a session active and remember selected settings when you access the lobby from a phone. You can clear them through your browser controls, but the next visit may require a fresh login and phone verification.

You can ask for access to, or correction of, a specific personal record through the policy contact path. Include your account reference and identify the field, such as a phone detail or payment reference, so we can confirm ownership before responding.

You may request deletion of personal details through our support path where local law permits. Some account, payment or security records may need to remain for an operational or legal reason, and we explain which record is affected and why.

Send your account reference, a short description of the Privacy Policy question and the relevant event time or receipt reference. Do not send a password, PIN, wallet login or one-time code; those details are not needed to start the request.