Reference

Privacy Policy For Your area66 Account

DANA, OVO, GoPay and QRIS records are handled alongside your account details under the area66 Privacy Policy, so you can see what we collect and why.

Clear data purposesWallet record contextDirect support path
Explore Our Lobby Read FAQ
area66 Privacy Policy For Your area66 Account
HELP WITH RECORDS

Privacy Questions Reach Our Account Team

A clear support route matters when a Privacy Policy question affects your login or wallet status.

Account requests Ask us to access, correct or remove personal data through the account support path.
Wallet records If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount…
Access concerns A sign-in alert, changed device or stalled verification can be reported from the same…
DATA CONTROL

What We Handle Behind Your Account

The Privacy Policy is practical: it connects each data category to an account action you can recognise.

Account details

We handle details such as your chosen account identifier and verified phone contact to create access and send account responses. Keeping these fields accurate helps us distinguish your request from another account and reduces confusion during a login check.

Device signals

When you move from a mobile browser to desktop, technical signals can record the device type, session time and security event. These details help us spot unusual access without treating a new device as proof that your personal details have changed.

Cookies

Cookies can keep a session active, remember basic display choices and support security checks. You can manage browser cookie settings, although blocking them may interrupt the account path or require you to verify your phone again.

Wallet matching

A payment reference from DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI may be linked to your account record to confirm status. We use the reference for reconciliation and do not need your wallet PIN.

Retention periods

We keep account, security and payment-related records only for the period needed for service operation, dispute handling, fraud checks or legal duties. When a record no longer has a valid purpose, we remove it or make it less identifiable.

Your requests

You can ask what data we hold, request a correction, question a cookie or seek deletion through support. We may request account ownership details before acting, and any access or eligibility decision depends on local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening an area66 account. They explain account data, cookies, wallet references, device checks and the support path in plain terms. If your situation is not listed, contact us from the account route and include only the details needed to locate your profile. Access remains where local law permits.

The area66 Privacy Policy covers account details, phone verification, device and session signals, cookies, wallet references, security records, retention and requests for access or correction. It applies when you use the account path or connected lobby features from Indonesia, where local law permits.

Phone verification helps us confirm that an account request belongs to you and supports account recovery or unusual sign-in checks. We may use the verified contact when handling a Privacy Policy request, but you should never send a password, wallet PIN or complete security code.

Yes. The Privacy Policy explains how DANA, QRIS, OVO, GoPay, bank transfer and virtual account references can be connected to an account record for payment-status matching. We use the reference needed for reconciliation and do not require your wallet PIN to investigate a status.

You can ask for a copy of the personal data linked to your account through the support path. We may confirm ownership using your verified phone or another account detail before responding. The scope and timing of a request depend on local law and applicable retention duties.

Send a correction request through account support and identify the field that appears wrong, such as a contact detail or account identifier. We may ask for verification before changing it. Payment references and security logs may need separate checking when they support an open status question.

Cookies can remember a session, basic display preferences and security state when you use the account route. Your browser can block or clear them, but doing so may sign you out or trigger phone verification again. Cookie handling remains subject to local law and your browser choices.

Use the support path inside your account and describe whether the concern involves personal data, a device alert, a cookie or a DANA, OVO, GoPay or QRIS reference. Include the account contact needed to locate the record, but never send a password or wallet PIN.

Related Pages

area66 Indonesia FAQ area66 Casino About Us Access guide