Reference

dtg88 Privacy Policy For Your Account

Our Privacy Policy explains how we handle the details connected with your dtg88 account, from phone verification and mobile browser access to DANA or QRIS activity.

Clear data purposesMobile account accessDANA and QRIS recordsRequest support directly
dtg88 dtg88 Privacy Policy For Your Account
CONTACT PATHS

Privacy Questions Reach Our Support Path

A clear contact route helps when you want to ask about the Privacy Policy, correct an account detail, or understand a wallet record. Start from the support contact displayed inside your account and include the email or phone detail linked to your profile. For a DANA, OVO, GoPay, or QRIS question, add the transaction reference rather than sending a password. We use those details to locate the right record and respond without asking you to repeat sensitive account data.

Team online

Account data request

Use the support contact shown after login to ask what personal details are linked to your account. Include your registered phone detail and the specific correction or access request so we can identify the right profile.

Wallet record query

For DANA, OVO, GoPay, or QRIS records, send the transaction reference through the displayed support route. We can check the matching account entry without asking you to share a wallet PIN, password, or full payment secret.

Policy clarification

If a paragraph in this Privacy Policy is unclear, quote the relevant wording in your message. We will explain the data purpose, retention approach, or access step connected with your question and tell you what further details may be needed.

DATA PRACTICE

Data Choices Across Your dtg88 Account

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

Account details

We use the phone or contact details you provide to create your account, complete the access step, and respond to a support request. Check that your details are current before asking us to locate a profile or change an account record.

Mobile signals

When you sign in through a phone browser, we may record device, browser, language, and session signals. These details help identify unusual access and keep a login connected to the correct account without reading unrelated content on your device.

Cookies

Cookies can retain a session choice and help us understand which policy pages are opened. You can manage cookies through your browser settings, although removing them may require you to sign in again or repeat a preference step.

Wallet matching

A DANA, OVO, GoPay, QRIS, virtual account, or bank transfer reference may be matched with your account and cashier status. We do not need your wallet PIN or bank password to investigate a receipt or payment status.

Retention

We keep account, security, and transaction records only for the period needed for the stated purpose, account support, dispute handling, or a legal request. You can ask which category applies when you want a retention explanation.

Security requests

If you suspect someone accessed your account, contact us through the in-account support route and mention the approximate login time and device. We may ask for account confirmation before changing details or discussing a private record.

Privacy Policy Questions About Access

These Privacy Policy answers address the searches we hear most often before an account is opened or a request is sent. They explain account data, mobile sessions, wallet references, cookies, retention, and correction steps in plain terms. If your situation is different, use the support contact shown in your account and describe the exact record you want us to check.

It covers personal details, phone verification, login and device signals, cookies, support messages, and payment references connected with your account. It also explains why we use those records, how retention works, and how you can request access or correction where local law permits.

Phone verification links account access to the contact detail you supplied and helps us reduce mistaken or unauthorised sign-ins. The Privacy Policy treats the verification record as account data, so you can ask what is stored and why it remains connected with your profile.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay, QRIS, virtual account, and bank transfer activity. We use a reference to match the correct account or investigate a receipt, not to request your wallet PIN or bank password.

A mobile session may create records about your browser, device type, language, login time, and session security. We use these signals to keep access connected with your account and investigate unusual activity. The policy does not give us access to unrelated files on your phone.

Send a request through the support contact displayed inside your account, identify the detail you believe is wrong, and provide the registered phone or email detail for account matching. We may ask for an account confirmation step before changing private records.

Retention depends on the type of record and its purpose. Account, security, payment-reference, and support records may remain while needed for service access, dispute handling, or a legal request. Ask support which category applies and whether removal is available under local law.

You can manage cookies through your browser controls and ask us what cookie purpose applies to your session. Removing cookies may sign you out or reset a preference, but it does not automatically remove account records. Send a policy request for a separate data action.