Reference

neo69 Privacy Policy For Your Account

The neo69 Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity in Indonesia.

Account clarityWallet recordsCookie choicesSecurity requests
neo69 neo69 Privacy Policy For Your Account
CONTACT DATA HELP

Where To Ask About Privacy Policy

A clear support route helps you resolve a privacy question without sending account details through an unrelated channel.

Account privacy request Use the support path inside your account when you want to ask what personal details we hold or request a copy. Include the phone number linked to your account only through the protected form, so we can verify ownership before discussing account records.
Wallet record check If a DANA, OVO, GoPay or QRIS receipt appears connected with the wrong account, send the transaction reference through support. We compare the reference with the account ledger and explain the status without asking you to disclose a wallet password or security code.
Access and correction For a wrong phone number, duplicate profile detail or device-access concern, describe the exact field and account step affected. We may request phone verification before making a change, because correcting identity data without that check could expose your account.
DATA HANDLING DETAILS

What We Do With Your Account Data

We keep this Privacy Policy practical: each data use connects to an account action, a security need or a support request.

Account details

We use the contact and verification details you submit to create access, confirm that a request comes from you and send account-related replies. We do not need a game title such as Sumatra Tiger Slots to identify you, so keep support requests focused on the account issue.

Device signals

Login time, browser or device signals can help us spot an unusual return to the account. These checks support access protection when you move from a mobile browser to desktop, and they may lead to an extra verification step before account details are shown.

Cookie choices

Cookies can remember session state, language or a preference that keeps the account path usable. You can manage browser cookie settings, but blocking required cookies may interrupt login, phone verification or the handoff from the lobby to a payment status page.

Payment references

A wallet or bank reference lets us match a payment receipt with the correct account request. We use DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references for status checks when supplied, rather than requesting your wallet password.

Retention periods

We retain account, security and transaction records only for the period needed for the stated purpose, dispute handling and duties that apply where local law permits. A deletion request may remove data from active use while some records remain for a required reason.

Policy changes

When our handling changes in a material way, we place a notice on the relevant site or account path and update the Privacy Policy date. Check this page before changing account details, especially if you return after a long gap or use a new phone.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to have before opening or updating access. If your situation is not covered, use the account support path and describe the specific record, device or request involved. We will handle the question according to the policy and where local law permits.

The neo69 Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access and how you can request a copy, correction or deletion question through support.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account requests. We use those references to match a receipt or investigate a status issue, not to request your wallet password.

Open the support path inside your account and ask for a data copy. State the phone number linked to the profile through the protected form, then complete any ownership check we request. We use that step to avoid releasing account details to another person.

You can request a correction for an inaccurate phone number, profile field or similar account detail through support. Tell us which field is wrong and what should replace it. Phone verification may be required before the change, particularly when it affects account access.

Cookies can retain session state and selected preferences so your browser can move between account access and payment status pages. You can adjust browser settings, but blocking required cookies may stop phone verification or sign you out before the account request is completed.

We keep records for the time needed to operate the account, protect access, answer disputes and meet duties that apply where local law permits. A deletion request does not always remove records that must remain available for security, payment tracing or legal reasons.

Yes. Account access and our handling of certain requests depend on local law. If a local rule affects access, retention or a data request, we apply that requirement and explain the relevant outcome through the account support path where we can.