Reference

Privacy Policy for rock66 Indonesia Accounts

rock66 Privacy Policy explains how we collect, use and protect the details connected to your account, device and wallet activity, including DANA, OVO, GoPay and QRIS records.

Clear data purposesWallet record contextAccount contact routeLocal law wording
Explore rock66 Lobby Read FAQ
rock66 Privacy Policy for rock66 Indonesia Accounts
CONTACT YOUR WAY

Get Privacy Help Beside Account Support

A direct support route helps when your privacy question relates to a login, phone check or payment record.

Privacy request Send a request through our account support channel when you want to ask about stored data, its purpose or the way a Privacy Policy request is handled. We may ask for account details to confirm that the request comes from you.
Wallet record check For a DANA, OVO, GoPay or QRIS question, share the transaction reference and approximate date rather than a password or full wallet credential. We use the record to locate the relevant account event and explain its status.
Account correction If your phone number, email or profile detail is incorrect, contact us through the signed-in account path where possible. We may verify the account before changing the record so another person cannot redirect your access.
DATA HANDLING

What We Do With Your Privacy Choices

We keep the Privacy Policy practical by linking each data use to an account task you can recognise.

Account data

When you open an account, we may hold your contact details, phone verification result, sign-in history and selected account settings. These details support account entry and help us match a privacy request to the correct record.

Payment references

A wallet or bank transaction can leave a reference, amount, route and status in account records. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may appear in the payment trail, while sensitive credentials remain with the payment service.

Cookies and devices

Cookies can preserve a signed-in session, while device and browser signals can help identify repeated or unusual access. On mobile, you can clear site data in browser settings; clearing it may require phone verification at the next sign-in.

Account security

We use account checks around sign-in, phone verification and unusual activity to reduce unauthorised entry. Never send us a password, one-time code or complete wallet credential in chat, even when asking about a Privacy Policy request.

Retention period

We retain different records for different operational, dispute, security and legal needs. A payment reference may need to remain available after a session ends, while temporary browser data can disappear sooner; support can explain the category involved.

Your requests

You can ask what personal data we hold, request a correction, ask about deletion where permitted or question a stated use. Contact us through the account support path, provide enough detail to locate the record and complete any identity check we require.

Privacy Policy Answers Before Account Opening

These Privacy Policy answers cover the points most often raised before an Indonesian account is opened. We focus on the records created by sign-in, phone verification, device use and local payment routes, so you can understand the practical steps before sharing details. If your situation is different, use the support path and tell us whether your question concerns account data, cookies, payment references or a correction request. Any access or eligibility question depends on local law.

The rock66 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can ask for access, correction or another permitted change.

We use your phone number for account identification and the phone verification step before account access. It can also help support locate the correct record. We do not ask you to place a password or one-time code in a support message.

Yes. The Privacy Policy covers the account-side references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These can show a route, reference, date and status, while sensitive wallet credentials remain with the relevant payment service.

You can contact support through the signed-in account path and ask what personal data we hold. Include the account contact detail needed to locate your record. We may verify your identity first, then explain which data can be provided under applicable requirements.

Send a correction request through account support and identify the detail that needs changing, such as a phone number or email address. We may complete an account check before editing it, helping prevent another person from taking over your sign-in route.

Retention depends on the record and its operational, dispute, security or legal purpose. A payment reference may remain after a session closes, while temporary cookie data can end sooner. Support can explain the category and the applicable retention reason.

You can ask support whether deletion applies to a particular record. We assess the request against account security, unresolved payment questions, dispute handling and legal duties. Where retention is still required, we will explain why the record cannot yet be removed.

Related Pages

rock66 Indonesia Live Baccarat FAQ rock66 Casino Access guide