Reference

KETUA10 Privacy Policy For Your Account

Clear records for DANA, QRIS and your login begin with a clear Privacy Policy.

Account dataWallet recordsDevice choicesPrivacy requests
KETUA10 KETUA10 Privacy Policy For Your Account
PRIVACY SUPPORT

Get Privacy Help Near Your Account

A clear support route matters when a privacy question appears beside a login or wallet status issue.

Account access Tell us which account step is blocked and include the phone verification status shown…
Wallet records For DANA, OVO, GoPay or QRIS questions, send the transaction reference and visible status…
Privacy requests Ask to access, correct or remove eligible personal data through the account support path.
SIX DATA CHECKS

Six Privacy Checks Behind Your Login

We keep this policy practical by linking each privacy choice to an account action you recognise.

Collection

We collect account details, phone verification results, device signals and transaction references when they are needed for login, wallet matching, security checks or a privacy request.

Cookies

Cookies and similar browser tools can remember session choices and help us understand whether a login request belongs to the same device. You can manage browser cookie settings.

Account security

We use phone verification, login records and device signals to identify unusual access. Never send a password, wallet PIN or full authentication code through a support message.

Retention

Transaction and account records remain while needed for service checks, disputes, security or legal duties. When the purpose ends, we remove, anonymise or restrict the record.

Your requests

You can ask what personal data we hold, request a correction or ask whether deletion is available. We verify account ownership before releasing or changing private details.

Policy contact

Use the account support path for Privacy Policy questions, including a DANA receipt check, a device-access concern or a request to clarify how retention applies.

Privacy Policy Questions About KETUA10

These Privacy Policy answers focus on the account questions you are most likely to have before opening access. We explain wallet records, mobile data, phone checks and request handling in plain language, while local access remains subject to local law. If your situation is not listed, use the account support path and describe the exact screen or record involved.

It covers personal data handled through your account pages, including login details, phone verification, device signals, cookies, payment references and messages sent through the privacy support route.

The verification result helps connect an access request with the correct account and reduces mistaken changes. We use the status for account security rather than asking you to share an authentication code.

Yes. The Privacy Policy covers payment references and visible status details connected with DANA, QRIS, OVO, GoPay, virtual account and bank transfer requests made through your account.

We may use browser type, device signals and login timing to maintain a consistent mobile session and identify unusual access. These details support security checks and are not a substitute for account verification.

Use the account support path and state whether you want access, correction or clarification. We verify ownership first, then identify the relevant account records and explain any legal or operational restriction.

You may request removal through the privacy contact path. We assess the request against security, dispute and legal needs; where retention is required, we explain why the record must remain.

The policy describes data handling for our Indonesia account path where local law permits. Access and eligibility depend on local law, so your available account steps may differ by location.