Reference

Open cod77 slot Privacy Policy

cod77 slot Privacy Policy explains what we collect when you create an account, use DANA or QRIS, and open the lobby from your phone.

Account dataWallet recordsDevice cookiesPolicy requests
Explore Our Lobby Read FAQ
cod77 slot Open cod77 slot Privacy Policy
CONTACT PATHS

Find privacy help beside account support

A clear contact path helps you ask what we hold, why we use it or how to correct it.

Account contact Use the support contact shown in your signed-in account when you want to ask about stored profile details, phone verification or a correction. We may request a matching account detail before discussing personal records, so another person cannot obtain information connected to your login.
Wallet record help If your privacy question concerns a DANA, OVO, GoPay or QRIS reference, send the transaction date and the account contact used at the time. We use those details to locate the relevant record without asking you to share a wallet password or full security code.
Access questions When you cannot reach the policy or account contact route, open the support link from the login screen and mention Privacy Policy in your message. We can direct the request to the right team, while eligibility and access remain dependent on local law.
HANDLING DETAILS

See how we protect policy requests

We handle privacy as an account process rather than a marketing statement. Our records connect your submitted details with sign-in, wallet and device events only when that connection helps provide access, prevent…

Data collection

We collect details you enter for an account, such as contact and verification information, together with technical signals from your browser or device. A mobile session opening Live Baccarat Grand can create access and device records, while the game title itself is used to understand the requested service.

Cookie choices

Cookies can keep your session recognised, remember basic settings and help us detect repeated sign-in problems. You can manage cookies through your browser controls, although blocking required cookies may prevent the account path from staying open between login and the lobby.

Account security

We use phone verification before account access and may compare sign-in details with earlier account activity. Never send us a password, wallet PIN or one-time code. If a sign-in looks unfamiliar, contact support through the account route and describe the device path involved.

Payment records

A DANA, OVO, GoPay or QRIS request can create a reference, amount and status record so we can match the cashier event to your account. Bank transfer and virtual account records may be handled in the same way, without storing your wallet password.

Retention process

We keep personal records for as long as needed to provide the requested account service, resolve a payment question, investigate misuse or meet a legal requirement. When a record no longer serves one of those purposes, our process is to remove it or restrict its use.

Change requests

You can ask us to correct inaccurate account details, explain how a record is used or clarify whether a record remains stored. Include your registered contact and the specific field or event, such as phone verification or QRIS status, so we can assess the request accurately.

Check Privacy Policy answers first

These Privacy Policy answers focus on the account questions you are most likely to have before opening an account or contacting us. They cover collection, cookies, wallet references, correction requests and access. If your question is not listed, use the support path above and identify the account record or device session involved.

It covers account details, phone verification, device and browser signals, cookies, wallet references and records created when you use the account path. It also explains retention, correction requests and contact steps. Access to any service depends on local law and the details you provide.

We use phone verification before account access to connect the sign-in attempt with the correct account and help identify unusual access. The related record can also support a correction request. Do not send a one-time code or wallet PIN through support.

Yes. A DANA or QRIS transaction can produce a reference, status and account link used to match the cashier event. OVO, GoPay, bank transfer and virtual account activity can be handled similarly. We do not need your wallet password to check that record.

Use the support contact shown in your account or from the login screen, and state the exact detail you want corrected. Include your registered contact and a short explanation, such as an incorrect phone verification record. We may confirm ownership before changing anything.

On mobile, cookies can keep the session connected between login and the lobby and remember basic settings. Your browser controls can restrict them. If required cookies are blocked, the account path may ask you to sign in again or fail to retain the session.

We keep records while they are needed for account access, payment questions, misuse checks or legal duties. After that need ends, our retention process removes the record or restricts its use. You can ask support whether a particular account or wallet record remains stored.

Yes. Send a request through the account support route and identify the contact attached to your login. We may ask for ownership checks before sharing personal records. Your request can mention account details, device activity, cookies or a payment reference such as QRIS.

Related Pages

cod77 slot Indonesia MotoGP Grand Prix About Us FAQ Account information