Reference

999zk Privacy Policy for Clear Account Data Choices

Our Privacy Policy explains what we collect when you open an account, verify your phone, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account recordsWallet activityCookie choicesAccess requests
999zk 999zk Privacy Policy for Clear Account Data Choices
REQUEST HELP DIRECTLY

Get Help With Privacy Requests

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

Account help route Use the account help path when you want to know what profile, phone verification or sign-in data we hold. We may request an account identifier before releasing private details.
Wallet status request For DANA, OVO, GoPay or QRIS records, include the payment reference and date. Our support team can match the entry with the account ledger without asking you to resend a full wallet password.
Correction request If your contact detail or account record needs correction, send the requested change through support. We verify the request against your account before updating stored data or explaining why a record remains.
SECURITY IN PRACTICE

Keep Wallet And Device Data Safer

We treat privacy as an operating task rather than a link placed at the bottom of the account screen.

Data handling

We use phone, account and payment reference data for sign-in, verification, reconciliation and support. DANA, OVO, GoPay and QRIS details are treated as transaction records, not as a request for your wallet password.

Cookie controls

Cookies and similar device storage can help keep your session active and remember settings. Your browser controls can remove or restrict them, although some account screens may then require another sign-in.

Account security

Phone verification helps us connect an account request to the right person. We also check sign-in events and device signals when access looks unusual, then may ask for an account step before sharing records.

Retention timing

We keep account, payment and support records only for the operational or legal period that applies. A request to delete data may not remove records that must remain for payment reconciliation or legal duties.

Who handles requests

Our account support route receives privacy questions and sends them for handling by the team responsible for the relevant record. We may separate a wallet query from a device or profile query.

Changing your details

Ask us to correct a phone number, contact detail or other account entry through support. Include the affected field, and we will confirm identity before making a change or explaining the result.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers address the searches we hear before an account is opened: what data is collected, how wallet records are handled, what happens on mobile devices, and how to request a change. If your question concerns a specific DANA, OVO, GoPay or QRIS reference, include that reference when contacting account support.

It covers account creation, phone verification, sign-in devices, cookies, payment references, support messages, retention and requests to access or correct personal data. It applies to our Indonesia-facing account process where local law permits.

Yes. The Privacy Policy covers DANA and QRIS references used to match a payment request with your account, check receipt status and answer support questions. We do not need your wallet password for that process.

We may collect your phone number, verification result, account settings, device details, sign-in events and payment references. We use these records for access, security, reconciliation, support and duties required where local law permits.

Use the account help route and ask for a data access request. Tell us which records you need, such as phone verification, device events or wallet references, then complete the identity check before disclosure.

Yes. Send a correction request through account support and identify the field that is wrong. We verify the account before changing it, and we explain if a payment or legal record must remain unchanged.

Cookies or similar storage can keep your session and selected settings available while you use the mobile lobby. You can restrict them through browser controls, but sign-in may be required again afterward.

Retention depends on the purpose and the rule that applies to the record. Payment reconciliation, account security or legal duties may require continued storage, even after a deletion request is submitted.