Reference

Privacy Policy for Your ata168 Account

ata168 explains what account, device and wallet data we collect, why we use it, and how you can request access or changes.

Account dataWallet detailsDevice controlsPrivacy requests
ata168 Privacy Policy for Your ata168 Account
REQUEST HELP DIRECTLY

Get Clear Privacy Help Beside Support

A clear contact path matters when you want to ask about Privacy Policy rather than a game or wallet result.

Account privacy request Use the support link from your logged-in account to ask for a copy, correction or removal of personal data. Include your registered phone detail so we can compare the request with the account record before making any change.
Wallet data check If a DANA, OVO, GoPay or QRIS reference appears in your data request, send the receipt number rather than a wallet PIN. We can use that reference to locate the transaction record while keeping secret wallet credentials out of support messages.
Access concern When an unfamiliar device reaches your account, contact support through the account path and describe the login date, device type and affected session. We can review the access record and explain the security step applied to that session.
HOW WE HANDLE DATA

Privacy Controls That Follow Your Account

Our handling process follows the account actions you take, from phone verification to a wallet status check and a later request to change your details.

Data collection

We collect the account details you submit, phone verification results, login events and payment references connected to your activity. For a QRIS or bank transfer check, the reference helps us match a receipt without requiring your wallet password or banking PIN.

Cookie choices

Cookies and similar browser storage help keep your session open, remember selected settings and identify an interrupted account path. You can clear them through your browser settings, although clearing session data may require you to verify your phone again.

Device security

We may record device type, browser details, approximate network signals and login time when you open the lobby or account area. These signals help us spot an unfamiliar session before sensitive account or wallet actions continue.

Account verification

Phone verification connects an account request to the contact detail you provided. Before we discuss private records or process a correction, we may ask you to complete the same account check so another person cannot request changes on your behalf.

Retention periods

We keep account and payment-reference records for as long as needed for account operation, dispute handling, security checks or legal duties. When a record no longer serves one of those purposes, we remove it or use a form that no longer identifies you.

Change requests

You can ask what personal data we hold, request a correction, or ask about deletion through support. State the exact change and use your registered account contact; we will check identity first and explain any record that must remain for a valid operational or legal reason.

Privacy Policy Answers for ata168

These answers address the searches we receive about account data, wallet references, device records and access requests. They are written for your ata168 account, so you can decide what to send to support and what to keep private before opening the lobby.

The ata168 Privacy Policy covers account details, phone verification, login and device records, cookies, wallet references, support messages and retention. It explains why we use each category, how we protect account access, and how you can request a copy or correction through support.

No. Do not send a DANA, OVO, GoPay or QRIS PIN to us. Our records may contain a payment reference, amount status or receipt detail needed to match activity to your account, but secret wallet credentials should remain inside your own payment service.

Open the support route from your account area and state that you want a copy of your personal data. Include your registered phone or email detail and describe the records you need. We verify the request first, then explain the available data and delivery step.

Yes, you can ask support to correct an inaccurate account detail. Tell us which field is wrong and provide the registered contact used for verification. We may request a phone check before changing identity or wallet-related records, so another person cannot alter your account.

Device and browser signals help us recognise an unfamiliar login, protect the account path and investigate a disputed session. We may record device type, browser details, login time and approximate network signals, but you should never send a password or wallet PIN in a support request.

We keep payment references for the period needed to operate the account, reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, handle disputes and meet legal duties. After that need ends, we remove the record or make it non-identifying where practical.

The policy page is available for account questions, while account access and eligibility depends on local law. Where local law permits, you can use support to ask about collection, correction, deletion, cookies or retention, and we will explain any applicable restriction.