Reference

Privacy Policy for Your dtg288 Account

Our Privacy Policy explains how we handle the details you provide when opening and using a dtg288 account, including contact data, phone verification and wallet records.

Clear data purposesWallet record contextAccount access choicesIndonesia policy wording
Explore Our Lobby Read FAQ
dtg288 Privacy Policy for Your dtg288 Account
CONTACT PATHS

Privacy Help Through Your Account

A clear contact route matters when you want to ask about personal data rather than a wallet balance.

Account contact Use the support contact shown after login to ask about stored account details, phone verification or a privacy request. Include the email or phone linked to your account so we can locate the correct record without asking you to publish sensitive details.
Cashier context When your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, mention the payment reference rather than a wallet password or PIN. We use that reference to trace the relevant record and keep unrelated data out of the request.
Access assistance If login or phone verification stalls, contact us through the account support path and describe the device step you reached. We may ask for account identifiers needed to confirm ownership, but we will not ask you to send a password through a support message.
DATA PRACTICES

How We Handle Your Account Data

Our approach is practical: collect what an account action needs, use it for a stated purpose and limit access to the records required for that task.

Account details

We may use your contact details and phone verification status to create, protect and recover your account. When you request a change, we compare the request with the account record so another person cannot alter your details through an unverified message.

Payment references

DANA, OVO, GoPay and QRIS can return a status or reference linked to an account action. We use that limited record to reconcile the cashier step, investigate a missing status and respond to your question without treating the wallet account as ours.

Device activity

Your mobile browser may send login time, browser type and security signals when you move from account access to the lobby. These details help us identify unusual access and diagnose a failed phone verification step; they are not a request for your device contents.

Cookies

Cookies and similar browser storage can remember a session choice, support security and show whether a page loads correctly. You can manage browser permissions on your device, although removing essential storage may require you to sign in again or repeat an account step.

Retention

We retain records for as long as needed for the purpose described in this policy, account security, dispute handling or a legal requirement that applies to us. When a record no longer has a valid purpose, our process is to remove or anonymise it where feasible.

Policy requests

To request access, correction or removal of eligible information, use the support contact available inside your account area. Tell us what you need and include an account identifier; we may verify ownership first, and the outcome depends on local law and the record involved.

Privacy Policy Questions for dtg288

These answers address the privacy searches we hear most often before an account is opened or a wallet is connected. They explain what we collect, why a payment reference may appear, how mobile access is handled and where to send a request. If your situation involves a specific account record, use the support contact inside your account area so we can check the relevant detail.

It covers account details, phone verification, login and device records, cookies, payment references and support requests. It explains why we use each type of data, how we protect access and how you can request access or correction, where local law permits.

Phone verification helps connect an account request with the person seeking access and can help us respond to recovery or security issues. We record the verification result and related account event, not a request for your phone contents or private messages.

Yes. The policy includes payment references and status information connected with DANA, OVO, GoPay and QRIS. These details can help us match a cashier event or investigate a missing status. Wallet credentials remain with the relevant payment provider.

When you sign in from a mobile browser, we may receive technical details such as browser type, session timing and security signals. We use them for account protection and fault diagnosis while you move from login to the lobby, not to inspect unrelated device content.

You can ask for access or correction through the support contact inside your account area. State the account identifier and the specific record you want checked. We may confirm ownership before acting, and the available response depends on local law and retention duties.

We keep information for the period needed for its stated purpose, account security, payment questions, dispute handling or an applicable legal requirement. Retention can differ by record type. When continued storage is no longer needed, we aim to remove or anonymise it where feasible.

Use the support contact displayed inside your account area and describe the privacy matter clearly. For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account issue, include the transaction reference but never send a password, PIN or full wallet credentials.

Related Pages

dtg288 Indonesia Loyalty Points Guide FAQ FAQ Sportsbook Help Access guide