Reference

Open the dtg288 Privacy Policy

The dtg288 Privacy Policy tells you what account, wallet, device and support details we collect, why we use them, and how you can request access or correction.

Account clarityWallet contextCookie choicesRequest access
dtg288 Open the dtg288 Privacy Policy
CONTACT ROUTES

Ask about Privacy Policy through account help

A clear support route matters when you want to understand a record or correct a detail. Start from the account help area and include the phone number or account identifier connected to your request; do not send a wallet password or full payment credential. We can use the relevant receipt, login event or cashier status to locate the issue, while requests about your personal data stay within the Privacy Policy process.

Team online

Account access request

Use account help when you need a copy of personal data linked to your dtg288 account. We may ask for phone verification before releasing details to the account holder.

Wallet record question

Mention DANA, OVO, GoPay, QRIS, bank transfer or virtual account when a payment reference looks incorrect. We compare the receipt and status record without requesting your wallet password.

Correction or removal

Tell us which profile field or stored preference needs changing. We review identity, account activity and any retention need before confirming an edit, restriction or removal request.

DATA PRACTICES

See how dtg288 handles device and account data

We handle Privacy Policy requests through the same account path used for sign-in and payment-status questions, so the record can be checked against the correct account.

Account creation

When you open an account, we use the submitted contact details and clear phone verification step to establish account access. If a detail changes, ask us to update the record through support.

Payment references

DANA, OVO, GoPay and QRIS may create transaction identifiers, while bank transfer and virtual account records can include matching references. We use these details to reconcile status and investigate disputes.

Cookies

Cookies can preserve a signed-in session, remember selected settings and help us detect unusual access. You can manage browser cookie controls, although restricting them may affect account verification.

Device signals

Your browser, operating system and connection signals can be logged for session safety and fault diagnosis. The mobile path does not require a separate app, and the same policy applies on mobile and desktop.

Retention checks

We keep account, payment-status and support records for the period needed for service operations, security, disputes or legal duties. When that purpose ends, records are deleted or anonymised where practical.

Request handling

For access, correction or deletion requests, we may confirm your phone or account details first. State the exact request and preferred contact path so we can respond without exposing another person’s data.

Find Privacy Policy answers before account access

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain what data connects to dtg288, how wallet references are treated, what happens on mobile, and how to ask for a copy, correction or removal. If your situation involves local eligibility, access depends on local law, so include that context when contacting support.

It covers account details, phone verification, sign-in and device signals, cookies, support records, payment references and retention. It also explains your route to request access, correction or removal of applicable data.

Our Privacy Policy distinguishes wallet transaction references from wallet credentials. DANA, OVO, GoPay and QRIS status details may be recorded for reconciliation, but you should never send us a wallet password.

Use the account help path and state that you want a copy of your personal data. Include the connected phone number or account identifier; we may complete phone verification before responding.

Yes. Privacy Policy requests can include a correction to your contact details, preferences or account record. Identify the field, explain the change and complete any identity check needed to protect your account.

We retain records while needed for account operation, payment-status checks, security, disputes or legal duties. After the relevant purpose ends, we delete or anonymise them where practical under the applicable requirement.

Yes. The Privacy Policy applies when you sign in from a mobile browser or desktop. Device and browser signals may support session safety, while cookies can affect verification if you restrict them.

Start through account help and describe the specific data concern, such as a login record, QRIS receipt or profile correction. Do not include passwords, and mention if access depends on local law.