Reference

9n9n Privacy Policy for Your Account

Our 9n9n Privacy Policy explains how we handle the details connected with your account, device, wallet activity and support requests.

Account dataWallet recordsDevice controlsPolicy requests

Browse Our Lobby Read FAQ

How DANA And QRIS Data Is Used

9n9n Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy separates account details from transaction references so we can check a payment without keeping unnecessary wallet content. If you choose DANA, OVO, GoPay or QRIS, we may receive a reference, amount, status and time connected with your account, while the wallet provider handles

1
its own account records. Bank transfer and virtual account activity can add a bank reference and reconciliation status, including rails connected with BCA, BRI, Mandiri or BNI. We use these records to match a deposit, investigate a failed status and confirm a withdrawal request. Opening an
2
account requires the details shown on the registration screen, followed by phone verification before account access. Device signals such as browser type, operating system and session time help us detect unusual login activity. Access and eligibility depends on local law, and this policy applies where local
3
law permits. Our policy may change when processing methods change; we will show the current version on this page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Ask About Privacy Through Account Help

A direct support route helps you ask what data we hold, why a wallet reference is attached to your account or how to correct a registration detail.

Account help path Open the support path beside your account area to ask about collected data, phone verification or a correction. We may request account details to confirm that the request comes from you.

Payment status request For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference and date. We use those details to trace status without asking for a wallet password.

Access trouble If your phone verification or login is interrupted, contact us through the account support route and describe the device path. We use the report to investigate access signals and protect your records.

CONTROLLED HANDLING

What 9n9n Keeps And Why

We keep this Privacy Policy practical: each data group has a purpose, an access path and a point at which it is no longer needed.

Account records

We use registration details, phone verification status and account events to provide access and investigate sign-in issues. We do not ask you to send a wallet password when checking a payment.

Payment references

A DANA, OVO, GoPay or QRIS reference helps us match a status with your account. Bank transfer and virtual account records are used for reconciliation and payment enquiries.

Cookies and sessions

Cookies and session records help remember sign-in state, protect account pages and understand whether a device session is continuing. You can manage browser cookie settings, though some access steps may then fail.

Device security

Browser, operating system, approximate session details and unusual login patterns can be checked when you move from phone verification to the lobby. These signals help us flag access that needs attention.

Retention schedule

We retain records for the operational, security and dispute purposes described here, then remove or restrict them under our retention process. The period can differ by record type and legal requirement.

Your requests

Ask us to access, correct or clarify personal data through account support. We may verify your identity before acting, and we will explain if a request cannot proceed because local law requires a record.

Privacy Policy Answers For 9n9n Accounts

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. We keep the wording tied to actual account steps, payment references, device sessions and access requests, so you can decide what to do before sending a support message.

It covers account registration, phone verification, device sessions, cookies, payment references, support requests, retention and your options to access or correct personal data.

We use payment references and status details for reconciliation, but you should not send a DANA, OVO, GoPay or QRIS password to support. Wallet credentials remain with the relevant provider.

Browser and operating system details help us recognise a session, investigate unusual access and protect the step between phone verification and your account. We use these signals for security purposes.

Use the account support path and state which registration detail needs correction. We may ask for verification before changing it, so another person cannot alter your account record.

Retention depends on the record type, security need, dispute handling and legal requirement. We keep payment references only through the applicable retention process, then remove or restrict them.

Yes. Send an access request through account support with enough detail to locate your account. We verify the request, identify the relevant records and explain any lawful restriction.

This policy describes our handling for supported Indonesia access, while account access and eligibility depends on local law. It applies where local law permits and may vary by location or request.

9n9n Privacy Policy for Your Account

Ask About Privacy Through Account Help

What 9n9n Keeps And Why

Account records

Payment references

Cookies and sessions

Device security

Retention schedule

Your requests

Privacy Policy Answers For 9n9n Accounts

01 What does the 9n9n Privacy Policy cover?

02 Does 9n9n store my DANA or QRIS password?

03 Why does the Privacy Policy mention device data?

04 How can I correct my 9n9n account data?

05 How long does 9n9n keep payment records?

06 Can I request a copy of data held about me?

07 Where does this Privacy Policy apply in Indonesia?

Related Pages