Reference

dim88 Privacy Policy For Your Account

Your dim88 Privacy Policy explains how we handle account details, phone verification, wallet references and mobile access before you open the casino or sports areas.

Account dataWallet recordsCookie choicesAccess requests
dim88 dim88 Privacy Policy For Your Account
SUPPORT ROUTES

Three Routes For Privacy Requests

A clear contact path matters when a login record or wallet reference looks unfamiliar. Open the support chat from your account area and describe the date, device and payment rail involved; do not send a full password or wallet PIN. We can route questions about access, correction, deletion or a receipt mismatch to the appropriate account team, while requests remain subject to identity checks and local law.

Team online

Account support chat

Open support from your logged-in account and ask about stored account details, phone verification or a login event. We may ask for account identifiers to confirm that the request comes from you.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference looks wrong, include the receipt date and reference shown in your account. We use those details to trace the payment record without requesting your wallet PIN.

Privacy change request

Ask through the same support route to correct account details, request a copy or question retention. We review identity first, then explain the available action and any local-law restriction.

DATA PRACTICE

Six Controls Behind Your Account Data

We treat privacy as an account operation rather than a footer link. The controls below explain how records move through login, payment checks and support handling.

Account details

We use your submitted account details and phone verification result to identify the account, respond to requests and connect the correct support history. Please keep your contact details current through the account path.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can appear as a reference or status. We use it to reconcile an account event, not to request your wallet PIN.

Cookies and devices

Cookies and device signals can keep a mobile browser session connected and help detect unusual login patterns. You can manage browser cookie settings, although some account functions may then need another sign-in.

Account security

We may compare phone verification, login time, device details and account activity when access looks unusual. This can pause a request until we confirm that the account holder is asking.

Retention

We keep records for the account, security checks, payment reconciliation, disputes or legal duties only while a stated purpose requires them. Retention questions can be sent through support for a case-specific explanation.

Your request

You can ask what account data we hold, request a correction or question its use through support chat. We verify identity before making changes and explain limits where local law permits.

Privacy Policy Questions For Your Account

These Privacy Policy answers cover the practical searches we expect before account access. They explain payment references, mobile cookies, identity checks, retention and the support route in terms that match how dim88 handles an Indonesian account. Where a request affects access or eligibility, the outcome depends on local law and applies where local law permits.

It covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It also explains how to ask for access, correction or clarification through support.

No. We may receive a DANA or QRIS payment reference and status needed for account reconciliation, but you should never send a wallet PIN, password or full security code to support.

Phone verification helps connect an account request to the correct account holder and can assist with unusual login checks. We use the result for access and support handling, subject to local law.

Open support chat from your account area and ask for an account data request. Include the account contact detail, but not your password. We verify identity before explaining what can be provided.

Yes. Send a correction request through support chat and identify the detail that is wrong. We may request verification, then update the account where the request is valid and local law permits.

Retention depends on the purpose, such as account security, payment reconciliation, disputes or legal duties. A support request can ask why a particular DANA, bank transfer or QRIS reference remains stored.

Cookies and device signals can maintain a mobile browser session and support unusual-login checks. You can adjust browser settings, though changing them may require another sign-in or affect account access.