Reference

Privacy Policy for des99 Account Data

Our Privacy Policy explains what we collect when you open a des99 account, sign in from a phone or computer, browse Blackjack or Rocket Crash, and use DANA…

Account dataWallet recordsDevice signalsCookie choices
des99 Privacy Policy for des99 Account Data
PRIVACY HELP PATH

Get Privacy Help Near Your Account

A clear contact path helps when your account data or wallet record does not look right.

Account help Use the account help route when you need to ask about stored profile data, a phone verification record or a sign-in event. Include your account identifier and the device path involved, such as mobile browser or computer, so we can connect your request to the right privacy record.
Wallet record check For a question about DANA, OVO, GoPay or QRIS data, send the payment date and reference shown in your receipt. We can check whether the record is attached to your account without asking you to disclose your password, one-time code or full wallet credentials.
Data request Ask us to access, correct or explain data held for your account through the available support path. State the request clearly, confirm the phone linked to your profile and remove unrelated payment details from any screenshot before sending it to us.
SIX DATA PRACTICES

Six Data Practices Behind Your Account

We handle Privacy Policy requests as account matters, not as general lobby questions. Our records help us understand whether a login came from your usual device, whether a phone verification step was…

Account details

When you open an account, we collect the details needed to create and maintain your profile, including your phone number and account identifiers. Those details let us send your login activity, cashier references and requests to the correct account instead of mixing records between accounts.

Device activity

A mobile browser or computer can create device and session signals such as browser type, sign-in time and security events. We use those signals to spot unusual access and help explain a login question; they are not a replacement for your phone verification step.

Cookies

Cookies can keep a session connected, remember selected settings and help us understand whether a page request worked. You can manage cookie settings through your browser, although changing them may affect account access, saved preferences or the path from login to the lobby.

Payment matching

Wallet and bank records are used to match an account action with a payment reference. This includes DANA, OVO, GoPay, QRIS, bank transfer and virtual account details. We do not need your wallet password or one-time code to investigate a receipt reference.

Retention steps

We retain account, security and payment records for as long as needed for the stated account purpose, dispute handling and applicable legal duties. When a record is no longer needed, our handling follows deletion, anonymisation or restricted-access procedures where those steps apply.

Changes and contact

If your phone number, account detail or stored preference is wrong, contact us through the account help route and describe the correction. We may ask for account verification before changing data, because a correction must not give another person access to your profile.

Privacy Policy Questions Indonesian Account Holders Ask

These answers focus on the Privacy Policy questions that arise before account access: what data is collected, how payment references are handled, what happens on a phone and how to request a change. If your situation is not covered, use the account help route with a short description and the relevant account or receipt reference.

The Privacy Policy covers data connected with account creation, phone verification, sign-in, device sessions, cookies, support requests and payment references. It explains how we use account details linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to create or identify your account, complete the required phone verification step and help protect sign-in access. It also helps us locate the correct profile when you ask about a stored detail or a wallet reference.

Yes. The Privacy Policy includes device and session signals from a mobile browser, such as browser type, sign-in time and security events. These signals help us investigate unusual access and keep a phone session connected to the correct account.

We use payment references and status details to connect an account action with the selected rail and investigate a receipt question. We do not ask for your wallet password or one-time code. Keep the receipt reference available when requesting a record check.

Yes. Contact us through the account help route, identify the data that appears wrong and confirm the phone linked to your profile. We may complete an account check before making a correction so another person cannot alter your details.

We keep account, security and payment records for the period needed for the stated purpose, account questions, disputes and applicable legal duties. When retention is no longer needed, handling may involve deletion, anonymisation or restricted access where appropriate.

Start with the account help route and state whether you want access, correction, an explanation of stored data or a cookie question. Include your account identifier and relevant date, but never send your password or one-time code. Access depends on local law.