Reference

Privacy Policy For Your dbl189 Account

Our Privacy Policy explains how dbl189 handles the details you provide when you open an account, verify your phone, enter the lobby, or use DANA, OVO, GoPay and…

Account dataWallet recordsDevice detailsCookie choices
Explore lobby Read FAQ
dbl189 Privacy Policy For Your dbl189 Account
HELP WITH PRIVACY

Get Policy Help Beside Your Account

Questions about our Privacy Policy should be easy to raise while you are signed in.

Account privacy requests Use the support contact path from your signed-in account to ask what personal details…
Wallet record questions For DANA, OVO, GoPay or QRIS records, send the transaction date, rail name and…
Access and deletion contact Ask through the same support route if you want a copy, restriction or deletion…
DATA HANDLING

What We Do With Your Details

Privacy at dbl189 is handled through practical account controls rather than broad promises. We separate login details from payment references where our systems allow, limit internal access to operational needs, and use…

Account and phone checks

When you open an account, we collect the details needed to create it and confirm your phone before account access. This helps us connect requests to the correct account and reduce mistaken changes when you ask about personal records.

Payment references

A DANA, OVO, GoPay or QRIS action can create a reference, amount, timestamp and status in our records. Bank transfer and virtual account activity may add bank or channel identifiers, while wallet credentials remain with the payment service.

Device and session signals

Your browser, device type, approximate network details and session events can be recorded to keep sign-in working and detect unusual access. On mobile, this supports the path from login to the lobby without requiring a separate app.

Cookies and browser choices

We use necessary cookies for sessions, security and saved settings, plus limited measurement where enabled. You can clear or block cookies in your browser settings, but doing so may require another login or interrupt account and policy access.

Retention and removal

We keep personal details only as long as needed for the stated account, security, support and record purposes, subject to legal or dispute-related retention. A deletion request does not automatically remove records that we must preserve where local law permits.

Requests and corrections

You can ask for access, correction, restriction or deletion through our support contact path. Include the account phone or email and the request you want handled; we may verify ownership before releasing or changing any personal detail.

Answers About dbl189 Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. They explain the practical steps for Indonesian access, including phone verification, device records, payment references and requests sent through support. If your situation is not covered, contact us from your account so we can check the relevant record and apply the current policy where local law permits.

It covers details connected with your account, phone verification, login sessions, device signals, cookies, support messages and payment references. It explains how we use, protect, retain and correct those details when you access the site or use DANA, OVO, GoPay or QRIS.

Phone verification helps us confirm that an account request comes from you before access or an account change is completed. It also lets support distinguish your request from another person’s request. We do not ask you to place a verification code in a public message.

Yes. The policy covers transaction references and status details received when you use those rails through your account. We may also record identifiers from bank transfer or virtual account steps, but your wallet PIN and full payment credentials are not requested in support chats.

Send an access request through the support contact path after signing in, with the account phone or email connected to your profile. We may complete an ownership check before sharing records. We will explain the available format and any details that must remain protected.

You can request a correction or deletion through support and describe the exact field or record. We assess the request against account security, unresolved transactions and retention duties. Where local law permits, we remove or restrict eligible details after confirming account ownership.

We may record browser type, device type, approximate network details and session events connected with login and security. On a phone, these signals help keep the route from account access to the lobby working. You can manage cookies and browser permissions on your device.

Yes. Account access and eligibility depend on local law, and the way a request is handled can vary by jurisdiction. We apply the current Privacy Policy where local law permits and will explain if a legal or security rule limits a requested action.

Related Pages

dbl189 Indonesia Access guide Indonesia Red Wheel 502 Account information dbl189 Casino