Reference

Privacy Policy For Your 9n9n Account

Your 9n9n Privacy Policy explains what we collect when you open an account, sign in from a phone, or check DANA and QRIS status.

Account dataWallet recordsDevice controlsRequest changes
9n9n Privacy Policy For Your 9n9n Account
HELP WITH DATA

Get Privacy Policy Help Before Account Changes

A clear support route helps you ask about the Privacy Policy without guessing which account detail matters.

Account questions For a Privacy Policy question about your name, phone number or login record, share…
Wallet status If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, tell us the payment…
Data requests To ask for a copy, correction or deletion assessment, describe the specific record and…
SIX DATA CONTROLS

Six Privacy Controls Behind Your Account

Our Privacy Policy is tied to practical account controls rather than broad promises. We separate login details from wallet status, limit internal access to records needed for account support, and use device…

Collection

We collect details you provide during the account step, including your phone number and account identifier. Login events, selected wallet rail and payment status records may also be stored so we can connect a request to the right profile.

Purpose

Account data supports sign-in, payment matching, security checks and responses to your Privacy Policy requests. We use DANA, OVO, GoPay and QRIS references to identify transaction status, not to request your wallet PIN.

Cookies

Necessary cookies can keep your session and selected settings available as you move from login to the lobby on a mobile browser. You can clear browser cookies, although doing so may require you to complete the account step again.

Account security

We compare sign-in details with device and session signals to spot unusual access. If a login does not match your normal pattern, we may pause the account step and ask you to confirm details before continuing.

Retention

We keep each record only for the period connected to its purpose, such as account security, payment reconciliation, dispute handling or a lawful request. When a record is no longer needed, we assess it for removal or restricted storage.

Your requests

You can ask what personal data we hold, request a correction, or ask how a deletion request applies to your account. Include your phone-linked account reference so we can check identity before changing or releasing private records.

Privacy Policy Questions For 9n9n Accounts

These Privacy Policy answers cover the account and payment questions you are most likely to have before opening access. Each answer points to a practical step, from checking a wallet reference to requesting a correction, so you can decide what to share and how to contact us. Account eligibility depends on local law, including the rules that apply to your location in Indonesia.

The 9n9n Privacy Policy covers data collected during account creation, login, mobile browsing and payment status checks. It explains how we handle phone details, account identifiers, device signals, cookies, wallet references and records connected with DANA, OVO, GoPay, QRIS or bank transfer.

We use your phone number to connect the account step with your profile, support a clear login path and confirm that a Privacy Policy request comes from the right account. Keep your password and wallet PIN private; we do not need either for a standard data question.

Yes. The Privacy Policy covers payment references and status records connected with DANA, OVO, GoPay and QRIS. We use those details to match a payment event with your account and investigate a stalled status, while your wallet PIN remains outside the request.

We use device and session signals to support account security, remember necessary mobile-browser settings and identify unusual sign-in patterns. These signals can help us pause an account step for confirmation; they are handled for the stated security and access purposes in the Privacy Policy.

You can contact us with your phone-linked account reference and describe the data you want copied or corrected. We check the request before sharing or changing private records. Some records may need to remain stored for security, payment reconciliation or where local law permits.

Retention depends on why the record exists. Login and device events may support security checks, while wallet and bank transfer references may support payment reconciliation or disputes. We assess records for removal or restricted storage when the relevant purpose ends, subject to local law.

Use our account support route and include your account identifier, the Privacy Policy section you mean, and whether the request concerns login, cookies, device data or a wallet status. Do not send a password, wallet PIN or complete payment credential in your message.