Reference

Open Your abcd66 Privacy Policy Path

abcd66 Privacy Policy explains how we handle the account details, device signals and wallet records connected with your access to Live Blackjack Prestige, Fan Tan Live Arena and…

Account dataDevice choicesWallet recordsPolicy requests
abcd66 Open Your abcd66 Privacy Policy Path
CONTACT PATHS

Choose Your Privacy Contact Route

A clear contact route helps you ask about the Privacy Policy without sending sensitive details through an unverified channel.

Account support Use the support link inside your signed-in account for questions about the Privacy Policy…
Wallet query For a DANA, OVO, GoPay or QRIS reference, keep the receipt number and transaction…
Access request If you want to ask about stored data or request a correction, identify the…
DATA PRACTICE

Browse How Our Policy Works

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

Account details

We handle the phone number and verification details you provide when opening an account so we can connect you with the correct account record. Do not send passwords through support; account checks use the sign-in and verification path already shown to you.

Mobile sessions

When you open the lobby on a phone, we may record session and device signals linked to sign-in activity. These signals help us spot unusual access around titles such as Aviator Quick Arena without reading unrelated content stored on your device.

Cookies

Cookies and similar browser files can keep a session active, remember basic choices and help a page load correctly. You can manage browser permissions on your phone or desktop, although restricting them may interrupt sign-in or return you to the account access step.

Wallet records

A DANA, OVO, GoPay or QRIS action can leave a reference, amount and status connected with your account event. Bank transfer and virtual account records may be checked in the same way, while full wallet credentials are not requested in support messages.

Retention approach

We retain records for as long as needed for the stated account, security, support or legal purpose, then assess whether they are still needed. The exact period can depend on the record type and local requirements, so ask support about a specific entry.

Change requests

To request correction, access or clarification, contact us through the account support route and name the data category involved. We may verify your identity first, then explain what can be changed, supplied or retained under the Privacy Policy.

Ask About Your Privacy Policy

These Privacy Policy answers focus on the account steps you are most likely to question before opening access from Indonesia. We address phone verification, mobile sessions, wallet references, cookies and requests for your records in plain language. If your case involves a particular DANA, OVO, GoPay, QRIS or bank transfer event, use the account support route and include its date or reference so we can respond to the right record.

The abcd66 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references connected with your access. It applies to records created when you sign in, use the mobile lobby or connect an account action with DANA, OVO, GoPay or QRIS.

Phone verification helps us connect you with the correct account and reduce confusion when access or wallet status needs checking. We use the verification result for account security and support handling, and you should never send your password or wallet PIN through a support message.

Yes. The Privacy Policy covers limited session and device signals created when you open abcd66 in a mobile browser or on desktop. These records help us identify sign-in issues and unusual access; they do not give us general access to unrelated files or content on your device.

We may keep a payment reference, date, amount and status needed to match an account event with DANA, OVO, GoPay or QRIS. Bank transfer and virtual account references may be handled similarly. Send only the receipt details needed for a support check.

You can request access, correction or clarification through the support route inside your signed-in account. State the account phone number and data category involved. We may confirm your identity first, then explain which record can be supplied or changed under local requirements.

We keep each record only for the account, security, support or legal purpose that requires it, subject to applicable local requirements. Retention can differ between a phone verification event, a cookie record and a QRIS reference. Ask support about a particular record for a precise response.

Yes. Account access and eligibility depend on local law, and this Privacy Policy is read together with requirements that apply where you are located. Where local law permits, we provide the account and support routes described here; contact us if your location creates a specific question.