Reference

cryptobet77 Privacy Policy For Your Account

Our Privacy Policy explains what cryptobet77 collects when you open an account, verify your phone, use DANA or QRIS, and access titles such as Aviator or Lightning Roulette.

Account dataWallet detailsDevice controlsPrivacy requests
cryptobet77 cryptobet77 Privacy Policy For Your Account
PRIVACY HELP DESK

Where To Send A Privacy Request

A clear contact path helps you act on this Privacy Policy without repeating your account history. Use the support route shown after login and include the email or phone number attached to your account. We may ask you to confirm ownership before discussing account data, wallet references or device records. Keep your payment receipt available when a DANA, OVO, GoPay or QRIS question is part of the request.

Team online

Account contact

Send a privacy request through the signed-in support route, using the email or phone number attached to your cryptobet77 account for identity matching.

Wallet records

For DANA, OVO, GoPay or QRIS records, include the payment reference and date; we use those details to locate the relevant account entry.

Access concerns

If a device or phone verification issue blocks your request, describe the account step that stopped and avoid sending passwords or wallet security codes.

CONTROL YOUR DATA

What This Policy Covers In Practice

We keep privacy controls close to the account actions that create data. Opening an account creates profile and verification records; using a phone or mobile browser can add device and connection signals…

Account creation

When you open an account, we process the details you enter and the phone verification result so the correct person can reach account settings.

Mobile devices

A mobile browser may provide device, connection and cookie signals linked to your session; clearing browser storage can remove saved preferences.

Cookies

Cookies help keep a signed-in session working and remember selected settings. Your browser controls whether these files remain after the session ends.

Account security

We may check unusual sign-ins or account changes before releasing personal details, updating contact data or discussing wallet-linked activity.

Retention

We keep account, payment-reference and security records only for operational, dispute, fraud-prevention or legal needs, then review whether continued storage is required.

Change requests

You can ask us to correct, access, export or delete eligible personal data through support; we verify ownership before applying a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account steps and payment references you are most likely to ask about before opening access. They explain what we collect, why we use it, how you can request changes, and what happens when local access rules apply. If your question is not listed, contact us through the signed-in support route.

It covers account details, phone verification, payment references, cookies, device signals, security records, retention and requests to access, correct, export or delete eligible personal data.

No. We receive transaction references and status details needed to match DANA, OVO, GoPay or QRIS activity. You should never send a wallet password or security code.

Phone verification helps connect an account request to the correct account holder. We may use that record when protecting sign-in access or checking a request about personal data.

Yes. Send a request through the signed-in support route with your account email or phone number. We verify ownership, then assess which records can be provided.

We retain records for operational, security, dispute or legal needs. When a record is no longer required, we remove it or restrict further use where applicable.

Yes. Tell us which account detail is incorrect and provide the attached email or phone number. We may request additional confirmation before changing the record.

Yes. Privacy rights and service access depend on local law. We handle requests for accounts available where local law permits and explain any applicable restriction.