Reference

Open akar66 Privacy Policy Before Account Access

akar66 Privacy Policy shows what we collect when you create an account, verify your phone, browse Live Roulette Prestige or use DANA and QRIS.

Account dataWallet recordsCookie choicesPhone verification
akar66 Open akar66 Privacy Policy Before Account Access
CONTACT ROUTES

Switch To The Right Privacy Contact

A clear contact path matters when a Privacy Policy question affects your account or wallet record. Start with Live Chat Support and include the account step, date and payment reference involved; we use those details to locate the right record without asking you to repeat the full story. If you are contacting us from Jakarta or elsewhere in Indonesia, access depends on local law and our support team may ask for a safe account check before discussing private data.

Team online

Live Chat Support

Use Live Chat Support for Privacy Policy questions about account data, cookies, phone verification or a request to correct your details. Share your account identifier, but never send a password or wallet PIN in the chat.

Wallet receipt check

For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate time through the support route. We compare the receipt with the account record and explain which data can be changed or retained.

Account access help

If a privacy request is blocked by a sign-in issue, tell us which account step stopped, such as phone verification or a device change. We confirm ownership before discussing private account details or making a change.

HANDLING PRACTICE

Browse How We Handle Your Data

Our Privacy Policy is practical: it connects each data type with a reason, an access rule and a request path.

Account creation

When you open an account, we use submitted contact details and phone verification status to create the account record and…

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce reference data rather than a wallet password.

Mobile sessions

A mobile browser can send device, browser and session signals when you sign in or move through account pages.

Security checks

Before we disclose private records or change account details, we may ask you to complete an account check.

Retention timing

We retain account, support and payment-reference records only for the period needed for the stated purpose, account security or a…

Policy changes

If this Privacy Policy changes, we place the updated wording on this page and identify the revision date where applicable.

Check Privacy Policy Answers

These Privacy Policy answers address the account, wallet and device questions we hear before account access. They also show the practical route for a data request, from identifying the account to checking a DANA or QRIS reference. If your situation is unusual, use Live Chat Support and describe the exact step involved.

The akar66 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual accounts. It also explains purposes, retention, security checks and ways to request a change.

Yes. Contact us through Live Chat Support with your account identifier and a clear request to access your records. We first confirm account ownership, then explain the available data and any reason a legal or security duty requires part of it to remain.

Send a correction request through Live Chat Support and identify the field that is wrong, such as a contact detail or phone verification status. We may request an account check before editing it, so another person cannot change your record.

Yes. The policy covers payment references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual accounts. We use a reference, time and account match to check a receipt or wallet status; do not send a PIN or password.

Cookies and similar session files can help keep sign-in steps working and record browser choices. Our Privacy Policy explains their purpose and your available settings. Device signals may still be used for account security, even when optional cookie choices are changed.

We keep records for as long as needed for the stated account, security, support or legal purpose. When you request removal, we review whether a payment reference, security record or legal duty requires continued retention and explain the result through the contact route.

Yes, account access and eligibility depend on local law. If you are in Indonesia, the policy applies to the data created during permitted account activity, including phone verification, mobile sessions and local wallet references. Ask Live Chat Support if your location creates a specific question.