Reference

zigzag66 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move through titles such as Live Blackjack Diamond or Aviator Mobile…

Account recordsWallet detailsDevice choicesPolicy requests
zigzag66 zigzag66 Privacy Policy For Your Account
REQUEST HELP

Privacy Help Beside Your Wallet Status

A clear request route matters when a privacy question appears beside a login or wallet issue.

ACCOUNT QUESTIONS Ask which account details we hold, why a phone verification record appears, or how…
WALLET STATUS For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, send the…
CHANGE REQUESTS Use our support route to request correction, access, or deletion where applicable.
DATA PRACTICE

Your Privacy Choices Around Aviator

We handle this policy area through practical account controls rather than broad promises. The records created around login, wallet status, and device use help us answer a specific request, while access to…

DATA WE USE

We use account contact details, phone-verification results, login events, device and browser signals, and payment references. A title such as Fortune Fishing Game may appear in activity records when needed to explain an account event or answer your request.

COOKIE CONTROL

Cookies and similar browser signals help keep a session connected and show whether a page, such as the payment status view, has loaded correctly. You can manage browser cookie settings, although some account functions may then require another login.

ACCOUNT SECURITY

Phone verification, login records, and device signals help us identify unusual account activity. We do not ask for your DANA, OVO, GoPay, or QRIS wallet password. Keep your account contact details current so a security question reaches you.

RETENTION PERIOD

We keep records only for the period needed for the stated account, payment, security, or legal purpose. A transaction reference may remain after a session ends when it is needed to reconcile a bank transfer or answer a later status request.

WHO CAN ASK

The person linked to the account can request a copy, correction, or eligible deletion of personal data. We may verify the registered phone or another account detail before releasing records, so one account's data is not sent to another person.

HOW TO CHANGE

Send your request through the support route and describe the record involved, such as a phone detail, device entry, or QRIS reference. We will assess the request under applicable requirements and explain if a record must remain for a stated purpose.

Privacy Policy Answers For Your Account

These questions address the points you are most likely to search before opening an account or sending a privacy request. Each answer relates to the zigzag66 Privacy Policy, from payment references and cookies to phone verification, retention, and access where local law permits.

It covers personal data connected with account creation, phone verification, login, device use, payment status, support requests, and lobby activity. It also explains cookies, retention, security checks, and how you can request access, correction, or eligible deletion of your records.

No. We use payment references and status details to match a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account request with your account. We do not need your wallet password to check whether a payment record belongs to you.

Device type, browser signals, and login events help us keep an account session working and identify unusual access. If you open Aviator Mobile Play on a phone and later sign in on desktop, these records can help explain the account path.

Use the support route connected with your account and state that you are making a privacy request. Describe the record you want, such as a phone-verification entry or payment reference. We may confirm your registered contact detail before sending account data.

Yes, you can ask us to correct an inaccurate or outdated personal detail where applicable. Include the account contact detail, explain what is wrong, and provide the replacement. We may verify ownership first, particularly when the request affects wallet or login records.

Retention depends on why the record was created. Login and device data may be kept for security purposes, while payment references can remain when needed for reconciliation, support, or legal requirements. We remove or anonymise records when the relevant purpose ends where applicable.

The policy applies to your account activity from Indonesia, including requests connected with Semarang or Makassar, but access depends on local law. If local rules do not permit access, do not continue. You can still contact us about a data question where a request route is available.