Reference

doi88 Privacy Policy For Your Account

Our doi88 Privacy Policy explains how we collect, use, protect and retain details connected with your account, wallet activity and device access.

Account dataWallet recordsDevice accessPolicy requests
Explore Our Lobby Read FAQ
doi88 doi88 Privacy Policy For Your Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear privacy question should reach the team that can connect it to your account record. Start with the support route available after sign-in and state whether your request concerns phone verification…

Account access For a Privacy Policy request linked to phone verification or sign-in, use the account support route and provide the contact detail attached to your doi88 account. We use that step to identify the correct record before discussing personal data.
Wallet records If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, mention the wallet type and transaction date. We can then connect your privacy request with the relevant account record without asking for an unrelated payment credential.
Device concerns When a privacy request follows access from a new phone or browser, tell us which device path you used and whether the session remains open. That context helps us check security events while keeping your account conversation focused.
DATA PRACTICE

Six Ways We Handle Your Data

We keep this policy practical by connecting each data use to an account action you can recognise.

Account details

We use the name, phone or contact details you submit to create and maintain your account. During a privacy request, we compare the request with the account detail already attached to you before discussing access, correction or deletion options.

Phone verification

The phone verification step connects account access with the contact detail you supplied. We keep the resulting status as an account-security record, while the Privacy Policy explains why that status is needed and how you can ask about its handling.

Device signals

A phone, tablet or browser can create technical signals such as session identifiers, language settings and connection details. We use them to recognise an active session, investigate unusual access and protect your account rather than to replace your account identity.

Cookies

Cookies can preserve a sign-in session or remember a setting on the policy page. Your browser controls whether cookies are accepted. Blocking them may affect account access, and our policy describes the purpose of each cookie category used on the site.

Wallet references

Payment records can show a method such as QRIS, DANA or bank transfer, plus a reference, amount and status. We use that limited context to reconcile account activity and handle a privacy question without requesting your wallet password or security code.

Retention requests

We retain account and security records only as long as needed for the stated service, protection and legal purposes. You can ask why a record remains, request a correction where available or seek deletion where local requirements allow it.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the searches we expect before an Indonesian customer opens an account. They explain what we collect, how a request is checked and what changes when you use a phone, wallet or browser to reach doi88. Where a question depends on location or a legal requirement, access depends on local law. Use the support route connected with your account when you need a response about a specific record rather than a general policy explanation.

The doi88 Privacy Policy covers account details, phone verification, device signals, cookies, wallet references and support requests. It explains why we use each category, how we protect access and how you can ask about correction, retention or deletion where local law permits.

Yes. Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use method, reference and status details to reconcile your account, while wallet passwords and security codes should remain with you.

Phone verification links your account with the contact detail you supplied and helps us identify the correct account during sign-in or a privacy request. We retain the verification status for account security and describe its handling in our Privacy Policy.

You can request a correction through the account support route. Include the contact detail attached to your account and describe the field that needs attention. We may verify ownership first, then explain whether the requested change is available under the Privacy Policy.

Privacy Policy treats device signals and cookies as technical data used for session continuity, settings and unusual-access checks. Your browser controls cookie acceptance, while a device path can help us investigate a sign-in concern without replacing your account identity.

We keep account, wallet-reference and security records for the period needed for account administration, protection and lawful obligations. You can ask why a record remains and request deletion where available, with the result depending on local law and the record type.

Use the support route available after sign-in and identify the request as a Privacy Policy matter. State whether it concerns account data, a QRIS reference, phone verification or device access. If sign-in fails, provide the attached contact detail and explain the access issue.

Related Pages

doi88 Indonesia Basketball NBA Bet FAQ Live Baccarat Diamond Access guide