Reference

9naga Privacy Policy for Indonesian Accounts

Clear control over your account, device and wallet data starts with this 9naga Privacy Policy.

Account data explainedWallet records clarifiedCookie choices availablePhone access protected

How DANA And QRIS Data Is Used

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

Our Privacy Policy explains how we receive, use and store details linked to your 9naga account. That can include your contact details, phone verification result, sign-in records, device signals, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We use

1
these records to open account access, match wallet status, check payment receipts, protect sessions and respond to requests. We do not describe access as universal: availability depends on local law. If you use a mobile browser in Bandung or another Indonesian location, device and connection data
2
may be recorded to keep the session working and investigate unusual access. The current policy sets out the applicable process for questions, corrections and removal requests.

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

CONTACT PATHS

Privacy Help Beside Your Wallet Status

A direct support path helps you ask about personal data without explaining your whole account history from the beginning.

Account access questions If your phone verification or sign-in record looks incorrect, send the account contact detail through our support route. We use it to locate the relevant profile and explain which data can be corrected before access is restored.

Wallet record requests For a DANA, OVO, GoPay or QRIS record, include the payment reference and approximate date. We compare that reference with the account ledger so a privacy request does not expose another account’s wallet activity.

Cookie and device help When mobile access behaves differently from desktop access, tell us the browser, device type and affected page. We use those details to separate a cookie setting from an account security event and explain the next step.

HANDLING PRACTICES

Cookies, Sessions And Account Records

We handle privacy as an operating task, not a label placed beside the account form. Our records show how a request moves from phone verification to account access, how a wallet reference…

Data collected

We may collect account contact details, phone verification results, sign-in timestamps, device signals, support messages and payment references. These records help connect a request to the correct account rather than relying on a display name alone.

Cookie settings

Cookies and similar device storage can keep a session recognised and remember selected access settings. Clearing them may require another sign-in, while rejecting optional storage can change how your mobile lobby pages load.

Session security

We examine sign-in patterns, device changes and unusual account actions to help protect your access. If a session appears unfamiliar, we may ask you to complete the account step again before showing private account or wallet records.

Retention periods

We retain account, support and payment-linked records only for the period needed for account operation, security checks, dispute handling or legal duties. The applicable period can differ by record type and local requirement.

Changing your data

You can ask us to correct a contact detail, phone record or other account data through support. Include the account connection and describe the requested change; we verify the request before editing the record.

Who receives requests

Privacy questions go to our support route for review by the team handling account and wallet records. We may request a matching account detail, but we do not need your full wallet credentials to assess a policy request.

Privacy Policy Questions About 9naga

These answers address the searches we hear most often before account access. They cover the Privacy Policy, personal data, wallet references, cookies and correction requests in practical terms. Where a request depends on identity, we use the account step already connected to your phone verification rather than asking you to send unnecessary payment credentials.

The 9naga Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how records are retained, and how you can ask about correction or removal.

We use payment references and status details to match an account transaction, but you should not send a DANA, OVO, GoPay or QRIS password through support. A receipt reference and account contact detail are normally enough to locate the relevant record.

Send the request through our support route using the phone or contact detail connected with your account. State which item is wrong and what it should say. We verify the request first, then explain the correction step under the Privacy Policy.

Yes. The Privacy Policy covers cookies and similar storage used to keep a session recognised or remember access settings. Clearing cookies can sign you out, while blocking optional storage may affect page preferences without changing the underlying account record.

Device and sign-in details help us protect account access, identify an unfamiliar session and diagnose a mobile page that differs from desktop. We may ask you to repeat phone verification before discussing private account or wallet records.

You can contact us with a removal request and the account detail needed to identify you. We assess the request against operational, security and legal record duties. Some records may need to remain for a defined retention period.

Yes. Access and eligibility depend on local law. Our Privacy Policy still explains the handling of account, device and payment-linked data for supported Indonesian access, including records connected with bank transfer or virtual account activity.

9naga Privacy Policy for Indonesian Accounts

Privacy Help Beside Your Wallet Status

Cookies, Sessions And Account Records

Data collected

Cookie settings

Session security

Retention periods

Changing your data

Who receives requests

Privacy Policy Questions About 9naga

01 What does the 9naga Privacy Policy cover?

02 Does 9naga store my DANA or QRIS password?

03 How can I request a correction to my account data?

04 Does the Privacy Policy cover mobile browser cookies?

05 Why does 9naga collect device and sign-in details?

06 Can I ask for removal of my 9naga data?

07 Does access to 9naga depend on local law?

Related Pages