Reference

neo69 Privacy Policy For Your Account

The neo69 Privacy Policy explains what we collect when you open an account, enter the lobby from a phone or desktop, and use local wallet routes in Indonesia.

Account clarityWallet recordsCookie choicesSecure access
neo69 neo69 Privacy Policy For Your Account
CONTACT THE TEAM

Reach Support About Privacy Questions

A clear contact route matters when your account record, wallet reference or phone verification needs attention.

Account requests Ask us to explain the personal details connected with your account or to correct a phone number after verification. We may ask for account identifiers before discussing records, so your request reaches the correct profile rather than another account.
Wallet records For a DANA, OVO, GoPay or QRIS reference, send the transaction date and visible status from your account. We use that context to investigate a receipt or matching issue while keeping wallet credentials and one-time codes out of support messages.
Policy contact Questions about collection, cookies, retention or a requested change can be sent through our support contact path. Describe the section that concerns you and we will explain the next step, including any identity check needed before releasing account data.
DATA HANDLING

Explore How We Handle Your Records

We treat the Privacy Policy as an operating rule for account access, wallet checks and support work, not as a generic statement.

Account details

We collect the details you provide during account opening and phone verification, then use them to identify your profile and respond to account requests. If a detail changes, contact us with the updated information and be ready to confirm ownership.

Device sessions

When you move from a mobile login to the lobby or return on desktop, technical session details may be recorded for access control and troubleshooting. These signals help us examine unusual activity without treating your device as a permanent identity.

Wallet checks

A wallet status or receipt request can include a payment reference, amount status and account identifier. We use these fields to trace the request across DANA, OVO, GoPay or QRIS, while bank transfer and virtual account checks follow the same account-matching purpose.

Cookie controls

Cookies can keep policy choices and essential page behaviour consistent during your visit. Your browser settings can restrict or clear them, although some account or sign-in functions may then require another session step.

Retention timing

We retain account, security, support and payment records only for the period needed for their stated purpose, dispute handling or a legal requirement that applies. The period can differ by record, so ask support which category your request concerns.

Change requests

To request correction, access or another permitted change, contact us using the account contact path and describe the record involved. We may verify your phone or account details first, then explain what we can change and where local law permits.

Browse Privacy Policy Questions

These Privacy Policy answers cover the searches we hear before an account is opened or a wallet request is checked. We keep the wording practical: what we collect, why a device or payment reference appears, how to ask for access, and what happens when you contact us. If your situation is specific, include the account step or transaction reference so support can identify the right record.

It covers information collected during account opening, phone verification, sign-in, lobby access, wallet requests, cookies and support contact. It also explains how we use, retain, protect and change those records, with availability and eligibility handled where local law permits.

We may collect the contact details you submit, phone verification results, account identifiers, session activity, device signals and messages sent to support. The purpose is to provide account access, examine security events, resolve requests and connect a wallet reference to the correct profile.

DANA and QRIS references can appear when you ask about a deposit, withdrawal or receipt status. We use payment references and account identifiers to trace the request. The same purpose applies to OVO, GoPay, bank transfer and virtual account records.

You can contact support with the email or phone detail linked to your account and ask which personal records are held about you. We may verify ownership before responding, and the available response depends on local law and the record category involved.

Send a correction request through the account contact path and identify the detail that needs updating, such as a phone number. We may ask you to complete phone verification or another account check before changing the record.

Cookies may support essential page behaviour, policy choices and session continuity when you use a mobile browser. You can clear or restrict them through browser controls, but sign-in or account access may then require another verification step.

Retention varies by record type and purpose. Account, security, support and payment references may be kept for access management, dispute handling or a legal requirement. Contact us with the record category and we will explain the applicable retention position.