Reference

neo99 Privacy Policy For Your Account

The neo99 Privacy Policy explains what account, device and wallet details we handle when you open an account and use the lobby.

Clear data purposesWallet status explainedContact path includedLocal law applies
neo99 neo99 Privacy Policy For Your Account
CONTACT YOUR WAY

Where To Ask About Privacy Policy

A direct contact path helps you resolve a Privacy Policy question without guessing which account screen to use.

Account contact Use the account support path for questions about your Privacy Policy rights, phone verification record or sign-in details. We ask for enough information to locate your account, but you should not send a password, wallet PIN or full payment credential through a support message.
Cashier status When a DANA, OVO, GoPay or QRIS receipt needs checking, identify the payment method and the account reference shown in your cashier path. We use those details to trace status without asking you to disclose unrelated personal data.
Data request For a copy, correction or removal request, state the exact account detail involved and the action you want us to take. We may ask for an account check before changing records, so a request is handled for the correct person.
DATA HANDLING PRACTICE

What We Do With Account Details

We keep our Privacy Policy tied to practical account events rather than vague statements. A phone verification step helps connect access to the right account, while device and session details help us…

Account data

We may handle your account identifier, phone verification status and selected account settings so we can provide access and respond to account requests. We keep these details connected to the account activity they support, rather than using them as a general profile.

Device signals

Your browser or phone can send session, device and security signals when you sign in. These details help us identify repeated access patterns and investigate an account alert. They do not replace your account checks or give us your device passcode.

Cookies

Cookies can preserve a sign-in session, remember a language choice or support basic page operation. You can clear or restrict them in your browser settings, although some account pages may then ask you to sign in again.

Wallet records

A payment reference, amount status and method label can remain attached to an account transaction so we can reconcile a receipt. This may include DANA, OVO, GoPay, QRIS, bank transfer or virtual account details needed for the request.

Account security

We use phone verification and account checks when access or a data request needs confirmation. Keep your password and wallet credentials private. If a sign-in looks unfamiliar, contact us through the account support path before sharing any further details.

Changes and retention

You can ask us to correct an account detail, explain a data use or remove information where local law permits. We assess the request against open payment, security and support records before confirming what can be changed.

Privacy Policy Answers For neo99

These Privacy Policy answers cover the account questions you are most likely to have before opening or using an account. They explain what we handle during phone verification, how wallet records are connected to your account, how cookies behave on mobile and where to send a data request. If your situation is not listed, contact us with a focused question and avoid including passwords or wallet PINs.

The neo99 Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references, security checks and support records. It applies when you open an account, sign in, use the lobby or ask us to explain, correct or remove data where local law permits.

Phone verification helps us connect access requests to the correct account and identify unusual sign-in activity. We use the verification result for account security and support handling; it does not mean you should send a password, wallet PIN or full payment credential to us.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account requests. These records help us trace a receipt or resolve a cashier question without asking for unrelated personal information.

When you sign in, we may receive session, browser and device signals used for access control and security checks. We do not need your device passcode. On mobile, clearing cookies can end your session and cause the account path to request sign-in again.

Use the account contact path and identify the exact detail you want corrected, explained or removed. We may ask for an account check before acting. Where local law permits, we confirm the outcome after checking related payment, security or support records.

We retain account, payment, security and support records only for the stated operational, legal or dispute-handling purpose, subject to local law. The period can differ by record type. Contact us if you want us to explain why a particular record remains.

Send a focused request through the account support path and describe whether it concerns access, correction, removal, cookies or a wallet receipt. Include your account reference when needed, but do not include your password, wallet PIN or complete payment credentials.