Reference

gt 108 Privacy Policy For Your Account

The gt 108 Privacy Policy explains what we collect when you open an account, use the lobby, or check wallet status through DANA, OVO, GoPay and QRIS.

Account accessWallet recordsDevice controlsPrivacy requests
gt 108 gt 108 Privacy Policy For Your Account
REQUEST PATHS

Privacy Policy Help When Account Details Stall

A clear contact path helps you act on this Privacy Policy without guessing which team handles your request. Start from the account support route when a phone verification step, login record or wallet reference needs checking. Include the email or phone linked to your account and a short description of the change you want. In Bandung or elsewhere in Indonesia, we use the same account-based path so requests can be matched to the correct record.

Team online

Account privacy request

Use the account support path to ask what personal details we hold, request a correction, or ask why a verification record is connected to your account. Include your linked phone detail so we can check identity before discussing private account data.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction date, amount reference and wallet name through account support. We use those details to locate the relevant record without asking you to share a wallet password or login code.

Access and device help

When a new phone or browser interrupts access, tell us the device path and the last successful login step. We can review the security event, explain the account check and direct you to the next privacy request step where local law permits.

DATA HANDLING

Six Privacy Controls Inside gt 108

We handle Privacy Policy requests alongside the account checks that keep payment and login records connected to the right person.

Account details

We may hold the contact details you provide during account opening, including the phone detail used for verification. These details help us send account notices, identify your request and prevent one person from receiving another person’s private account response.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can create a payment reference in your account history. We use the reference to match status checks and support questions, not to request your wallet password or banking login.

Device signals

Browser type, device details, login time and related security signals can help us identify an unusual access attempt. These records support account protection when you move from a mobile login to a desktop session or use a new device.

Cookies

Cookies and similar browser storage can remember session settings, support security checks and preserve choices connected to your account. You can manage browser cookie controls, although changing them may affect login continuity or the way policy choices are saved.

Retention

We keep personal and transaction records for the period needed to operate the account, resolve support matters, protect against misuse and meet applicable legal duties. When a record is no longer needed for those purposes, we follow our deletion or de-identification process.

Your requests

You can ask for access, correction, clarification or a suitable deletion request through account support. We may verify your phone or account details first, then explain what we can change and any reason a record must remain where local law permits.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers focus on the account actions you are most likely to take before opening or using gt 108 in Indonesia. You can check how payment references, phone verification, cookies, device changes and account requests fit together. If your question concerns access or eligibility, the answer depends on local law and the service is available where local law permits.

The gt 108 Privacy Policy covers account details, phone verification, login events, device signals, cookies, payment references and support requests. It explains why we use those records, how retention works and how you can ask for access, correction or clarification through account support.

We collect the reference needed to match a DANA or QRIS transaction with the correct account and status check. The record can help us investigate a missing update without asking for your wallet password. OVO, GoPay, bank transfer and virtual account references follow the same purpose.

Phone verification links an account request to the contact detail supplied during access. We may compare that step with login and security records before discussing private details or changing them. This reduces the chance that another person receives an account response or changes your data.

Yes. Send a correction request through the account support path and identify the phone or email connected to your account. We may complete an identity check before changing the record, then explain the result and any information we must retain for security or legal reasons.

We may record the browser, device type, login time and security signals when you move from mobile to desktop or use a new phone. Those details help us assess unusual access. If the check blocks your route, contact account support with the last successful login step.

We retain payment and login records for the account, security, support and legal purposes described in the Privacy Policy. The period can vary by record type and applicable duties. When the purpose ends, we follow the relevant deletion or de-identification process.

Use the account support path for a Privacy Policy request about access, correction, deletion or clarification. Include your linked contact detail and the record involved, such as a QRIS reference or device event. We will verify the request before discussing private account information.