Reference

Open t0288 Privacy Policy details

t0288 Privacy Policy explains how we handle your account details, phone verification, device activity and payment references when you use our Indonesia service.

Clear data categoriesPhone verification contextWallet record handlingPrivacy contact path
t0288 Open t0288 Privacy Policy details
PRIVACY HELP

Check support paths for policy requests

A privacy question should not get lost inside a payment query. We keep the policy contact route close to the account help and cashier areas, so you can identify the account concerned and describe the request without sending wallet credentials. Include the phone number or account reference linked to your profile, but never share a PIN or one-time code. We use the details you provide only to locate and handle the privacy matter.

Team online

Account help route

Open the account help area and select the privacy request path when you need to ask about stored details, phone verification or a correction. Adding your account reference helps us match the request without asking you to repeat payment credentials.

Cashier-side question

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, describe the payment status beside the cashier path. We can separate a transaction reference question from a request about your wider account data.

Device access check

When a privacy concern follows a phone or browser change, tell us the device path and approximate time shown in your account activity. Do not send a password or verification code; we use the report to investigate access records.

DATA PRACTICE

Manage privacy choices beside your account

We make the Privacy Policy useful at the moments your data is actually handled: account creation, phone checks, mobile browsing, payment matching and support contact.

Account details

We collect the details needed to create and maintain your account, then use them to match your phone verification and protect the correct profile. Before access is granted, review the submitted contact details for spelling and accuracy.

Cookies on devices

Cookies and similar device markers can help remember a session, detect unusual access and keep the mobile path connected to the right account. You can clear browser data, but doing so may require another phone verification.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference, amount and status records. We use those records to reconcile your account, not to request or store your wallet PIN.

Account security

Phone verification before account access helps us distinguish your session from an unfamiliar attempt. If your device changes, sign out of old sessions where possible and contact account help if the activity does not belong to you.

Retention decisions

We retain account, security and payment records only for the operational, dispute-handling and legal purposes described in the Privacy Policy. Retention can depend on local law, so a request may need a lawful reason and account match.

Changes and contact

To request a correction, deletion where available or a copy of personal data, use the privacy route in account help and identify the affected account. We may ask for verification before changing details or disclosing records.

Browse Privacy Policy answers before opening

These Privacy Policy answers address the searches we hear before an Indonesian account is opened. They explain the connection between your account, phone verification, mobile device, payment reference and support request without turning a privacy question into a general service description. If your situation is unusual, use the account help route and quote the relevant policy point.

The t0288 Privacy Policy covers account details, phone verification, device and cookie records, security events, support messages and payment references. It explains how we use, retain and protect those categories when you use the Indonesia service where local law permits.

Yes. Privacy Policy covers references and status information connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us match a payment to your account and resolve a status question; they do not give us your wallet PIN.

Phone verification helps connect the person requesting account access with the correct profile and helps identify unusual device activity. We may use the verification result as an account-security record, while the specific process can depend on local law.

The policy can cover browser type, device markers, session details and security events related to your mobile or desktop path. We use these details to keep a session connected, detect suspicious access and investigate a privacy request.

Use the privacy request path inside account help and state which detail is incorrect, such as a contact field or payment reference. Include the account reference needed for matching, but do not send a password, wallet PIN or one-time code.

You can submit a deletion request through account help, and we will assess which records can be removed. Some account, security or payment records may need to remain for dispute handling or legal duties where local law permits.

Start with the privacy route in account help, including the account reference and a short description of the concern. For an incorrect DANA, OVO, GoPay or QRIS status, mention the cashier-side reference so we can route the request correctly.