Reference

cph2773 Privacy Policy For Your Account

The cph2773 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between Live Roulette Grand and Live In-Play Football.

Clear data purposesWallet activity contextAccount request pathPolicy access
cph2773 cph2773 Privacy Policy For Your Account
CONTACT ROUTES

Ask Support About Your Privacy Policy

A clear support route helps when your Privacy Policy question involves a phone number, wallet reference or device record. Start from the account help path and describe the exact request, such as correcting a contact detail or checking why a QRIS receipt is linked to your account. We use the account step already completed to locate the right record, while access remains where local law permits. Keep your receipt reference ready so we can reduce back-and-forth.

Team online

Account privacy request

Tell us whether you want a copy, correction or clarification about personal data connected with your cph2773 account. Include the phone verification detail you used, but never send a password or wallet PIN through a support message.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, share the transaction date and visible reference from your receipt. We compare that detail with the account record and explain what we can confirm under the Privacy Policy.

Device access concern

For an unfamiliar sign-in or a device change, use the account help route and state when you noticed it. We may ask for account details already on file before discussing records, helping keep your personal data away from another requester.

DATA PRACTICES

Browse How cph2773 Handles Your Data

We keep each Privacy Policy practice tied to a practical account event: opening an account, signing in on mobile, checking a wallet reference or asking for a change.

What we collect

We may receive your phone verification detail, account settings, sign-in events and support messages. Payment records can contain a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference needed to match an account event.

Cookies and devices

Cookies and similar device signals help keep a session working, remember selected settings and identify unusual sign-in patterns. On mobile, we may record browser or device details connected with the route from account access to the lobby.

Account security

Phone verification and sign-in checks help us distinguish your account from an unfamiliar request. If you open Aviator Mobile Play or another lobby page after signing in, related session records can help us investigate access questions.

How long we retain

We retain account, support and transaction references only for as long as needed for the purpose described in the Privacy Policy, account administration and applicable legal duties. When a record is no longer needed, our process removes or de-identifies it.

When data is shared

We limit disclosure to service and operational needs connected with account access, security, payment matching or legal requests. We do not treat your wallet reference as a public detail, and we do not disclose it simply because another person asks.

Request a change

You can ask us to access, correct or clarify personal data through the support route. State the requested change and the account detail that helps us locate it; we may verify your identity before making an update.

Check Privacy Policy Answers Before Access

These Privacy Policy answers cover the questions we expect before you complete account access in Indonesia. They explain the records connected with phone verification, local wallet activity, cookies, device sessions and requests for changes. If your situation is different, contact us through the account help route with the smallest useful detail. We will handle the request according to the policy and where local law permits.

It covers personal details supplied during account opening, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It also explains why we use those records, how long we retain them and how you can request access or correction.

Yes. The Privacy Policy explains that DANA and QRIS references can appear in account records when we match a receipt or payment event. We may also handle OVO, GoPay, bank transfer and virtual account references for the same account purpose.

We may record the phone detail used for verification, the account step completed and related sign-in events. That record helps us answer access questions and distinguish your request from another person’s request. We do not ask you to send a password.

You can request a correction through the account help route. Describe the detail that appears wrong, such as a contact value or wallet reference, and include enough account context for us to locate it. We may verify your identity before changing the record.

Cookies can keep your session active, remember selected settings and help us identify unusual device activity. If you move from phone verification to a lobby page such as Fishing War Quick Arena, related session data may support account-security checks.

We keep account, support and payment references for the period needed to operate the stated purpose, handle disputes and meet applicable legal duties. After that period, our process removes or de-identifies records when retention is no longer required.

Yes. Send an access request through the account support path and identify the account detail you used during phone verification. We may ask for confirmation before responding, so personal data is not released to an unauthorised requester. Access depends on local law.