Reference

asu66 Privacy Policy for Your Account

Our Privacy Policy explains how we handle the details you provide when you open an asu66 account, sign in from a phone, or use DANA, OVO, GoPay and…

Account clarityWallet recordsDevice choicesPolicy requests
Explore Our Lobby Read FAQ
asu66 asu66 Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Wallet Records

A clear contact path matters when a Privacy Policy question concerns your own account rather than a general request. Start from the signed-in account help route so we can connect your message with the correct login, wallet reference or phone verification record. If you are in Yogyakarta or elsewhere in Indonesia, the same request structure applies. Please avoid sending a wallet password or full payment credential; a receipt reference and the email or phone attached to your account are usually more useful.

Team online

Account help

Use the account help route while signed in when you need a copy of your personal data, a correction to your account details, or an explanation of a Privacy Policy section. We may ask for an account step that confirms you are requesting data about yourself.

Wallet status

For a DANA, OVO, GoPay or QRIS question, send the payment receipt reference and the date shown in your account. We use those details to trace a status without asking you to reveal a wallet PIN or unrelated financial credentials.

Access concern

If a login or phone verification event looks unfamiliar, contact us through the account support path and include the device type and approximate time. We can compare that report with sign-in records and explain the next account-security step.

DATA HANDLING

How asu66 Applies This Policy

We keep this Privacy Policy practical by connecting each data category to an account action you can recognise.

Data collected

We may receive your account name, phone or email, verification result, login timestamps, device signals, cookie identifiers, support messages and payment references. The exact fields depend on the action you take, such as opening an account or checking a QRIS status.

Cookie choices

Cookies and similar signals can keep a mobile session connected to the right account and help us understand whether a page loaded correctly. You can manage browser cookie settings, although changing them may affect sign-in continuity or the path back to your lobby.

Account security

Phone verification helps connect account access to the contact detail you supplied. We record relevant sign-in and verification events so we can investigate an unfamiliar device or repeated access attempt. Never send a password, wallet PIN or one-time code in a support message.

Retention timing

We retain records for the period needed to provide account support, reconcile wallet activity, investigate security events and meet applicable legal duties. Retention can differ by record type, so a request about a DANA receipt may not follow the same schedule as a cookie record.

Request changes

You can ask us to correct inaccurate account details or explain the personal data connected with your account. Include your registered phone or email and the specific change. We may verify ownership before making an amendment, especially when the request affects wallet or login records.

Policy contact

For a Privacy Policy request, use account support and state whether you want access, correction, deletion or clarification. Include a receipt reference only when relevant. We assess the request under applicable rules, and access or eligibility depends on local law.

Privacy Policy Questions for asu66

These answers address the questions we expect you to ask before opening an account or sending a wallet receipt. They focus on the asu66 Privacy Policy, including mobile access, local payment references, cookies, retention and requests for personal data. If your case is different, use the account support path and describe the exact record or action you want us to check.

The asu66 Privacy Policy covers data connected with account creation, phone verification, sign-in, mobile browsing, cookies, support messages and wallet activity. It explains why we use those records, how retention works, and how you can request access or correction where local law permits.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account references when they appear in your account history. We use a receipt reference to match status and do not need your wallet PIN.

When you sign in from a phone, we may process device type, browser signals, cookie identifiers, login time and verification events. These details help maintain the correct session and investigate unfamiliar access. You can adjust browser cookie settings, though some account paths may then behave differently.

Send the request through the signed-in account support path and state that you want access to your personal data under the Privacy Policy. Include the phone or email linked to your account. We may verify ownership before sharing records connected with that account.

You can ask us to correct an inaccurate name, phone detail, email detail or other eligible account record. Use account support, identify the field that needs changing, and explain the correction. We may request a verification step before changing login or wallet-linked information.

The Privacy Policy explains that retention depends on the type of record and the reason it was kept. Account, payment reconciliation, security and legal records can follow different schedules. Ask support about a specific record, such as a QRIS receipt or cookie identifier.

You can submit a deletion request through account support, and we will assess it under applicable rules. Some records may need to remain for account security, payment reconciliation or legal duties. Access and eligibility depends on local law, so our response will explain the applicable outcome.

Related Pages

asu66 Indonesia Basketball IBL Bet FAQ asu66 Casino About Us