Reference

level789 Privacy Policy For Your Account

level789 Privacy Policy explains what we collect when you open an account, verify your phone, browse on mobile, or use DANA, OVO, GoPay and QRIS.

Clear data categoriesWallet record contextPhone verification stepsAccess request path
level789 level789 Privacy Policy For Your Account
REQUEST HELP CLEARLY

Ask About Account Data Changes

A clear request helps us locate the right record without asking you to repeat your account history. Start from the account help route, include the phone number linked to access, and describe whether your question concerns a wallet receipt, cookie choice, verification detail or another Privacy Policy matter.

Team online

Account access

Use account help when your phone verification detail looks wrong or login access stalls. We can check the account record connected with your request and explain the next step without exposing another person's data.

Wallet records

For a DANA, OVO, GoPay or QRIS receipt question, keep the reference visible and use the cashier support path. We use that reference to separate payment status from unrelated account activity.

Correction requests

Ask us to correct an inaccurate account detail through account help. Include the old value, the requested change and enough account context for us to confirm that the request comes from you.

SEE OUR DATA PRACTICE

Browse How Cookies And Data Work

Privacy Policy choices should match what happens during an ordinary account session. We connect a phone verification step with the account record, use device and session signals to protect access, and keep…

Data we collect

We may handle your account phone number, verification result, session details, device signals and activity records needed to operate access. Payment references from QRIS or bank transfer help us identify a matching transaction.

Cookies and sessions

Cookies and similar session tools help remember an active sign-in and protect the path from mobile login to the lobby. You can ask us to explain their purpose when a cookie question concerns your account.

Account security

Phone verification is an account step before access, while device and session checks help identify unusual sign-in activity. Never send a full password or another person's payment details in a support request.

Retention approach

We retain account, verification and payment references only for the operational, security and dispute-handling needs described in the Privacy Policy. Ask through account help if you need the retention basis for a specific record.

Who to contact

Our account help route is the first contact for Privacy Policy questions, including data access, correction, cookies and wallet references. Give us the account phone number so we can direct the request correctly.

Change or removal

You can request a correction or ask whether eligible data can be removed. We may need to confirm your account before acting, because changing a record must not expose or alter another account.

Find Privacy Policy Answers For Your Account

These questions address the account and payment details Indonesian customers most often need clarified before opening access. Each answer points back to the Privacy Policy process, including verification, cookies, wallet records, retention and requests made through account help.

It covers account details, phone verification, device and session signals, cookies, lobby activity records, payment references, retention, security handling and ways to request access or correction.

We use your phone number to create and verify the account, connect support requests with the correct record and help protect access. Verification is required before account access is completed.

Yes. It explains that DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be handled to match receipts, check status and resolve account payment questions.

Use account help and state that you want an access request under the Privacy Policy. Include your linked phone number and a clear description so we can confirm the request and locate the right records.

Yes. Send a correction request through account help with the inaccurate detail, the replacement value and account context. We may confirm your identity before changing information connected with access or payment records.

Cookies and session tools can remember sign-in state and help protect the mobile path from verification to the lobby. You can ask account help to clarify a cookie connected with your session.

Access depends on local law and is available where local law permits. The Privacy Policy still explains our handling of account and payment records for an eligible Indonesian account.