Reference

Privacy Policy For Your zero 66 slot Account

The zero 66 slot Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account data explainedWallet records clarifiedCookie choices includedContact route available
zero 66 slot Privacy Policy For Your zero 66 slot Account
CONTACT ROUTES

Privacy Help Beside Account Support

A clear contact path helps you ask about the Privacy Policy without mixing a data request with a game question.

Account data request Ask us to identify the personal data connected with your zero 66 slot account.
Wallet record question For DANA, OVO, GoPay or QRIS records, include the payment reference and approximate time.
Security concern If a login, phone verification event or device record looks unfamiliar, contact our account-help…
DATA PRACTICE

Six Practical Privacy Commitments

We handle privacy through ordinary account controls rather than vague promises. Phone verification links access to the account step you started, while device and login records help us investigate unusual sign-ins.

Data collection

We collect details needed for account creation, phone verification, sign-in protection, payment reconciliation and support. This can include contact data, device signals, activity timestamps and the text you send when asking for help.

Cookie controls

Cookies can remember a session choice or help us understand essential page performance. Your browser settings can restrict cookies, although changing them may affect sign-in continuity or the way a policy request is submitted.

Account security

Phone verification and login checks help connect account activity to you. We do not ask for your wallet PIN in a support message. If a device or login appears unfamiliar, identity checks come before account changes.

Payment records

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference lets us match a status to your account. We keep the transaction detail needed for reconciliation without treating it as permission to access your wallet.

Retention review

We keep personal data for account operation, security investigations, dispute handling or legal duties only as needed for those purposes. When a record is no longer required, we review it for deletion, aggregation or restricted access.

Change requests

You can ask us to correct inaccurate account data or explain how a record is used. Send the request through account support with enough detail to locate it; we may verify identity before making a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep the wording practical: what data we collect, why a phone check appears, how wallet references are used, what cookies do and where to send a request. If your situation is not covered, use the support route described above and include only the details needed to identify your account.

It covers account creation, phone verification, sign-in events, device signals, payment references, cookies and support messages. It also explains retention, security checks and requests for access or correction. Account access depends on local law, including for Indonesian account holders.

Phone verification helps connect the account step to the person requesting access and helps us investigate unusual sign-ins. We may use the verified contact to discuss a privacy request, but you should never send a password, wallet PIN or banking credential.

No. We use DANA, OVO, GoPay, QRIS, bank transfer and virtual account references to reconcile payment status. Those references do not give us your wallet PIN or banking password. If support asks for payment proof, hide sensitive credentials before sending it.

Yes, where local law permits. Send an account-help request with your registered phone number and a clear description of the data you want to access. We may verify your identity first, then explain what can be provided and in which format.

Use the support route near the cashier path and describe the inaccurate field, such as a contact detail or payment reference. Include enough account context for us to find it. We may request phone verification before changing information linked to access.

We retain records for account operation, security checks, payment reconciliation, dispute handling or legal duties for as long as those purposes require. We then review them for deletion, aggregation or restricted access where local law permits.

You can manage eligible cookies through your browser settings. Cookies may remember session choices or support essential page measurement. Restricting them can affect sign-in continuity, phone verification steps or the way a Privacy Policy request is sent.