Reference

do06 Privacy Policy For Your Account

The do06 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet activity.

Account dataWallet recordsCookie choicesSecurity requests
do06 do06 Privacy Policy For Your Account
GET POLICY HELP

Find A Clear Route For Privacy Questions

A direct contact path matters when your account record or payment reference looks wrong. We keep privacy questions separate from general lobby requests so you can explain the specific detail you want…

Account contact path Use the account help and contact path to ask how your personal details are used, request a correction, or ask which records relate to your do06 account. We may verify ownership before discussing account-linked data.
Wallet record request If a DANA, OVO, GoPay or QRIS reference needs checking, include the date, amount reference shown in your account and the wallet name. We use those details to locate the relevant record without asking for your wallet password.
Device access concern For an unfamiliar login or a privacy concern on your phone, tell us the device type, approximate login time and account phone number. We can check the access record and explain the next account-security step.
HOW WE HANDLE DATA

Practical Privacy Controls Inside do06

Privacy controls work best when they match the way you actually use your account. Our handling covers sign-in, wallet status, device access and requests about stored records rather than broad claims about…

Account details

We use your account details to create access, complete phone verification and connect activity to the correct account. Giving accurate details helps us answer a privacy request and prevents a correction from being applied to the wrong record.

Cookies on mobile

Cookies and similar device storage can remember session choices and help us detect an unusual sign-in. On your mobile browser, you can clear or restrict them through browser settings, though some account steps may need to be repeated.

Wallet matching

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account records, we keep payment references needed to match status and resolve disputes. We do not need your wallet PIN or banking password for that process.

Account security

Phone verification and sign-in records help us identify account access that does not look familiar. If your device changes, contact us through the account path with safe identifying details; never share a password or one-time code.

Retention choices

We retain personal records only while they serve account operations, security checks, dispute handling or legal duties. When a purpose ends, we delete, restrict or anonymise the relevant record where that action is permitted.

Change requests

You can ask us to correct eligible account details, explain a data use or clarify a retention period. State the request plainly and include the phone number linked to the account so we can verify ownership before replying.

Answers About The do06 Privacy Policy

These Privacy Policy answers address the account, payment and device questions you are most likely to have before opening access. We keep the wording tied to do06 processes, so you know what to send, what may be checked, and when local law affects an account request.

It covers account details, phone verification, sign-in records, cookies, device signals, payment references and requests about stored data. It also explains retention, security checks and how to contact us about correction or access where local law permits.

We use your phone number to create and verify account access, connect a privacy request to the right record and help identify unusual sign-ins. We do not ask you to send your password or one-time code through a contact request.

Yes. The policy covers the payment references needed to match DANA, OVO, GoPay, QRIS, bank transfer and virtual account status. These references help us check a receipt or dispute without requiring your wallet PIN or banking password.

Use the account help and contact path, state which detail is incorrect, and include the phone number linked to your account. We may verify ownership before changing a record, and the request remains subject to local law.

Cookies can keep a session choice and help detect unusual access. You can clear or restrict them in your mobile browser settings. If you do, some account steps may need to be completed again when you return.

We keep a record while it supports account operation, phone verification, security checks, dispute handling or a legal duty. After that purpose ends, we delete, restrict or anonymise it where local law permits.

Start through the account help and contact path and describe the data question clearly. For a wallet record, add the date, reference and payment name; for device access, add the device type and approximate login time.