Reference

Privacy Policy for Your doraplay Account

doraplay Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesCookie controls
doraplay Privacy Policy for Your doraplay Account
CONTACT ROUTES

Where To Ask About Privacy

A clear contact route helps you resolve a privacy question without repeating your account story. Use the account support path when you need to ask about stored details, a phone verification record or a wallet status connected with your account. Include the email or phone detail used for access, the relevant date and the request you want us to handle. We may ask for an account check before discussing personal data, and access depends on local law.

Team online

Account privacy request

Send your request through the account support path and identify the record you want us to find, correct or explain. We use the account detail you provide to locate the right profile before discussing its data.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment rail and transaction date. We can then match the request with the wallet or cashier entry without asking you to resend unrelated personal details.

Access and security help

If a sign-in or phone verification issue may expose your account, contact us from the recognised account route and describe the device involved. We may pause the request until we confirm that you are the account holder.

DATA PRACTICE

How We Handle Account Data

Our privacy process follows the way your account actually works: phone verification creates an access checkpoint, wallet activity creates payment records, and device sessions create security signals.

Phone verification

Before account access, we use the phone verification step to connect the sign-in request with the correct profile. This reduces confusion between accounts and gives our support route a specific identity to check when access stalls.

Payment matching

A DANA, OVO, GoPay or QRIS entry may be linked with your account reference, amount and time so we can check its status. Bank transfer and virtual account records follow the same matching purpose.

Device signals

We may retain browser, operating-system and session signals to recognise unusual access. Signing in on a mobile browser can create a new security event, while clearing cookies may remove saved preferences without deleting your account.

Cookie choices

Cookies can support sign-in continuity, page settings and security checks. You can manage browser storage through your device settings, but blocking required cookies may interrupt phone verification or return you to the account sign-in step.

Retention period

We keep account, payment and security records for the period needed to operate the service, resolve disputes, prevent misuse or meet a lawful requirement. When the purpose ends, we delete, aggregate or restrict the record where appropriate.

Change request

You can ask us to correct inaccurate account details, explain a data use or remove information where local law permits. We verify the request first, record the decision and tell you if a legal or security reason limits the change.

Privacy Policy Answers For Account Holders

These Privacy Policy answers focus on the account, device and wallet questions we expect from Indonesian customers. They explain what to include in a request, why verification matters and how local access rules affect a response. If your situation is not covered, use the account support path with the smallest useful set of details.

The doraplay Privacy Policy covers account creation, phone verification, sign-in events, device signals, cookies, wallet records and support requests. It also explains how we use information for account operation, payment matching, security checks and lawful requests where local law permits.

We collect the details needed to create and maintain your account, including contact information used for phone verification. We may also create sign-in, device and security records, plus payment references for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification connects an access attempt with the correct account and helps us respond safely when login details are disputed. It can also support a security check before we discuss personal data or change account details, subject to local law.

The Privacy Policy allows us to use payment references, dates and status details to match a wallet or cashier event with your account. This applies to DANA, OVO, GoPay, QRIS, bank transfer and virtual account records, without requiring unrelated data.

Yes. Send a correction request through the account support path and identify the field that is inaccurate. We verify that you control the account, check the relevant record and apply or explain the change where local law permits.

We retain account, payment and security records only for operational, dispute, misuse-prevention or legal needs. The exact period can depend on the record and local requirement. When the purpose ends, we delete, aggregate or restrict the data where appropriate.

Yes. Privacy rights, account eligibility and the information we may process depend on local law. We apply the rule relevant to your access region and explain any restriction when you contact us about a data request.