Reference

Indo Casino Portal Privacy Policy

The Indo Casino Portal Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesSecure access
Indo Casino Portal Indo Casino Portal Privacy Policy
PRIVACY HELP ROUTES

Choose Your Privacy Support Route

A clear contact path matters when you want to understand or change personal data. We keep privacy help separate from general game questions, so your request can refer to an account step…

Account access If phone verification or a login event looks unfamiliar, send the privacy request through the account help route. We use the account identifier to locate the relevant access record without asking you to repeat unnecessary details.
Wallet records For a DANA, OVO, GoPay or QRIS record, include the transaction reference and date shown in your receipt. We can then connect the privacy question to the correct cashier event rather than the full wallet history.
Policy questions For questions about cookies, retention or a correction, use the privacy contact option beside the policy link. State the action you want, such as access, correction or deletion, so we can route it clearly.
DATA HANDLING

Browse How We Handle Your Records

We keep the Privacy Policy practical by connecting each data category to an account action. Your phone verification supports account security, payment references support reconciliation, and device signals help us investigate suspicious…

Data we collect

We may receive account details, phone verification results, login timestamps, device and browser signals, wallet references, support messages and activity needed to maintain account security. We collect only what relates to the stated account or service purpose.

Cookie controls

Cookies can keep a session active, remember selected settings and help us identify technical errors. Your browser provides controls for clearing or blocking them, although some account steps may require a working session cookie.

Account security

We use phone verification, session checks and unusual-login signals to reduce unauthorised account access. Never send a full password in a support message; our privacy route needs an account reference, not your secret login credential.

Payment references

A DANA, QRIS, bank transfer or virtual account receipt may be retained with its status and reference number. These records help us answer a wallet question without treating the entire contents of your payment account as ours.

Retention choices

We retain records for the period needed for account security, transaction reconciliation, support handling and applicable legal duties. When a record no longer has a valid purpose, our processes address its removal or continued restricted storage.

Requests and corrections

You can ask which personal data we hold, request an inaccurate detail be corrected, or ask about deletion and retention. Include your account reference and requested action; eligibility and fulfilment depend on local law.

Find Answers About Privacy Policy

These Privacy Policy answers cover the account and wallet questions we expect you to ask before sharing personal details. If your request concerns a specific login, receipt or device, use the privacy contact route with the smallest useful set of details.

It covers account details, phone verification, cookies, device signals, support messages and payment references connected with your access. It also explains requests, retention and the way we handle account security.

DANA and QRIS references help us match a receipt, status or cashier event to your account. We use the transaction reference and related status for that purpose, rather than asking for unrelated wallet content.

We retain the verification result and related account security record when needed to confirm access or investigate an unusual login. The retention period depends on the purpose and applicable local law.

Use the privacy contact option in your account area and request access to your personal data. Add your account reference and a reachable contact route; we may need account checks before releasing details.

Yes. Send a correction request through the privacy route and identify the inaccurate field, such as a phone detail or account name. We may ask for verification before changing the account record.

Cookies can support login sessions, settings and technical diagnostics. You can manage them through your browser, but blocking required cookies may interrupt phone verification, account access or the transition from login to the lobby.

You can submit a deletion question through the privacy contact route. We assess it against account security, transaction reconciliation and legal retention needs, then explain which records can be removed or must remain restricted.