Reference

Privacy Policy for Your Indonesia Account

data china 2025 Privacy Policy explains what we collect when you open an account, check wallet status or use the lobby from a phone or desktop.

Account clarityWallet recordsCookie choicesRequest access
data china 2025 Privacy Policy for Your Indonesia Account
REQUEST HELP

Three Ways To Raise A Privacy Request

A clear request path helps you ask about stored account data without guessing which department to contact. We route privacy questions through the account support path, especially when your request concerns phone verification, wallet status, a payment receipt or a device session. Include the account identifier you use with us, but do not send a wallet PIN or sign-in password. We may ask for a matching account step before discussing private records.

Team online

Account support route

Use the support path attached to your account when you want to ask what personal records we hold. Tell us whether the request concerns sign-in, phone verification, DANA, OVO, GoPay, QRIS or a bank reference so we can direct it correctly.

Payment record question

If a privacy question involves a receipt or wallet status, include the transaction reference and payment name, such as QRIS or virtual account. We use those details to locate the relevant record while avoiding requests for your wallet PIN or bank password.

Access correction path

For a correction or removal request, describe the exact account detail that needs attention and the device path where you saw it. We may confirm phone verification first, then explain what can be changed under local law.

DATA HANDLING

Six Practical Privacy Controls We Apply

Privacy protection is handled through ordinary account operations rather than a separate promise. We separate sign-in checks from payment references, use session details to investigate unusual access, and keep a written path…

Account collection

We collect account details you submit, including contact details needed for phone verification. A completed account step helps us distinguish your request from another person’s request and reduces the chance of sending private records to the wrong contact.

Wallet matching

DANA, OVO, GoPay and QRIS references help us connect a payment event to the correct account. Bank transfer and virtual account records may also be used to check receipt status, but we do not ask for your wallet PIN or banking password.

Cookie choices

Cookies or similar storage can keep a sign-in session, remember a selected setting or help us understand a failed page load. You can adjust cookie controls through your browser, although restricting session storage may interrupt account access.

Device security

We may record device type, browser details, approximate session timing and sign-in events to help protect your account. If a phone shows an unfamiliar session, change your account credentials and contact support through the account path.

Retention purpose

We retain records only while they support account security, payment reconciliation, dispute handling, service operation or a legal requirement. When a purpose ends, we delete, aggregate or restrict the record where that action is available.

Change requests

You can ask us to access, correct or remove eligible personal data through support. State the requested action and account identifier; we may verify phone ownership before making a change or explaining why a record must remain.

Answers About Privacy Policy And Access

These Privacy Policy answers cover the account questions you are most likely to ask before opening access or contacting us. They explain why we use phone verification, how wallet records are handled, what cookies do, and how you can request a copy or correction. If your situation is specific, use the account support path and describe the relevant payment or device step.

It covers personal data collected through account creation, phone verification, sign-in, cookies, support contact and payment references. That includes records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details are needed for account or payment checks.

Phone verification helps us confirm that an account request comes from the person connected with the account. We may use that step before discussing private records, correcting account details or responding to a request to access data.

Yes, you can contact us through the account support route and ask for access to eligible records. Include your account identifier and explain the request. We may verify account ownership first, and the response depends on local law and applicable retention duties.

DANA and QRIS references are used to match a payment event with the correct account, check receipt status and investigate a wallet question. We do not need your wallet PIN. We keep the reference only for the account, security or payment purpose described in the policy.

Yes. Cookies or similar storage can preserve a mobile session, remember a setting or help us identify a failed page load. Your browser controls these choices. Blocking session storage can prevent the account path from working as expected on your phone.

Send a correction request through account support and identify the exact field that is wrong, such as a contact detail or phone verification record. We may request an account check before changing it, and some payment or security records may need to remain.

You can ask us to remove eligible personal data through the support route. We first check the account and the requested records. Removal may not apply where data is needed for payment reconciliation, account security, dispute handling or a legal duty.