Reference

Open Your Privacy Choices Before Joining

Account creation, DANA wallet checks, cookie choices, and session security all rely on data you share with us, so this Privacy Policy explains what we collect before you…

DANA wallet dataOVO account checksGoPay and QRIS contextCookie choicesWIB support hours
cryptobet77 Open Your Privacy Choices Before Joining
HELP PATHS

Check Privacy Help Before You Share

Privacy requests work faster when you contact us from the same account and device you normally use.

Live chat privacy queue Use live chat from 09:00-23:00 WIB when you need help reading this policy, updating…
Account inbox requests Send privacy access, correction, or removal requests through the account inbox after login.
Wallet record questions For payment privacy questions, share the rail name and transaction time, not screenshots showing…
ACCOUNT CARE

Browse How We Protect Account Data

Privacy protection is part of the account flow, not a separate promise hidden after signup.

Account data collection

We collect signup details, login history, device type, IP signals, and wallet references so your account can open, recover, and receive payment confirmations. We do not ask for full DANA, OVO, GoPay, or QRIS wallet balances.

Cookie and device choices

Cookies help keep your session active, remember language choices, and measure page errors. On mobile Chrome, you can check them through Settings > Site settings > Cookies, then return to your account to confirm preferences.

Security checks

Login alerts, password resets, and unusual device checks use account and session data. If a new phone signs in before you open Blackjack or Aviator, we may ask for verification to protect your profile.

Retention handling

We keep account, wallet, and support records only while they serve operational, security, dispute, or legal needs. After that period, we reduce, archive, or remove data according to our internal retention schedule.

Correction requests

If your name, phone number, or wallet reference is wrong, contact us through the account inbox. We may ask you to confirm the last login device or a payment reference before changing stored records.

Shared service access

Only teams that need the data for support, account security, cashier checks, or technical repair can access it. Each access is tied to a work reason, and unnecessary exports are restricted.

Ask Clear Privacy Questions Before Joining

These answers focus on the privacy choices you usually ask about before opening an account or sending a wallet record. They explain what we collect, how we use it, and how you can reach us when something needs correction. For anything tied to access or eligibility, the result may depend on local law.

We collect details needed to create and protect your account, such as phone number, login credentials, device signals, IP data, and wallet references. We use them for access, security checks, cashier matching, and support history.

No. We may store transaction references, status, amount, and timing from DANA, OVO, GoPay, or QRIS flows, but we do not collect your full wallet balance or unrelated wallet activity.

Send a request through the account inbox after login and state the date range you want checked. We verify your identity first, then prepare the account, wallet, and support records we can lawfully share.

Yes, if the record is inaccurate and you can pass account checks. Contact live chat or the account inbox, provide the field to correct, and include a recent payment reference when the change involves wallet data.

Cookies keep your login session active, remember basic preferences, help detect page errors, and support account security. You can manage browser cookies, but some account and cashier features may need them to work.

Only staff assigned to support, account security, cashier checks, or technical repair can view the request when their role requires it. We limit access and keep an internal record of work handled on your account.

We keep records while they are needed for account operation, payment matching, dispute handling, security checks, or legal duties. When those reasons end, we reduce, archive, or remove the data according to retention rules.