Reference

Privacy Policy For Your net89 Account

Your net89 Privacy Policy explains how we handle account details, device signals, cookies and wallet records when you use our site.

Account dataCookie choicesWallet recordsPhone verification
net89 Privacy Policy For Your net89 Account
POLICY HELP ROUTE

Contact Us About Privacy Policy Requests

A clear contact path helps you act on this Privacy Policy when a record looks wrong or you need an explanation.

Account data request Ask us to confirm which account details we hold, explain their source or provide an accessible copy where the request can be verified. Include your account identifier and phone-verification status so we can avoid sending personal data to the wrong person.
Wallet record question For a DANA, OVO, GoPay or QRIS record, send the payment reference and status shown in your account. We can check the matching record and explain what we retain for reconciliation, while the wallet provider remains responsible for its own separate data.
Policy change request Use our account-help path to request correction, restriction or removal where applicable. We may ask for a verification step before changing records, because confirming identity protects your account and prevents another person from altering your Privacy Policy preferences.
DATA PRACTICE

What We Do With Your Account Data

We keep this policy practical: each data category has a reason connected to account access, payment reconciliation, site operation or security.

Account details

We use details such as your contact information and phone-verification result to create, protect and maintain your account. We may compare submitted details with account records when you request access or a change, so the response reaches the correct account holder.

Device signals

When you move from login to the lobby on a mobile browser or desktop browser, technical signals can help us detect unusual access, maintain sessions and diagnose display problems. These signals support security and service operation; they do not replace the account checks we require.

Cookies and settings

Cookies can remember session choices, language settings and certain security controls. Our Privacy Policy treats these small files as operational data, and you can manage browser permissions, although blocking required cookies may prevent login or a requested account action from working.

Payment matching

A DANA, QRIS, OVO or GoPay status may be linked to an account reference so we can identify whether a transaction is pending, completed or mismatched. We do not use a wallet reference as permission to access the separate provider account behind it.

Account security

Phone verification, session controls and access logs help us investigate suspicious account activity. If you see an unfamiliar login or payment status, contact us through the account-help path promptly and avoid sharing passwords, one-time codes or full wallet credentials.

Retention and changes

We retain data only while it supports the stated purpose, account security, dispute handling or a required record. You can request correction or deletion through support; we will explain any part that must remain and record the outcome of your request.

Privacy Policy Answers For net89

These Privacy Policy answers focus on the questions you may have before opening an account or asking us to change a record. We explain what is collected during login, how wallet references are used, what cookies do on each device and how to contact us. Access depends on local law, and any request still needs enough account detail for us to verify the correct person.

The net89 Privacy Policy covers account details, phone verification, device signals, cookies, payment references, security logs and retention. It explains why we use each category, how you can request access or correction, and when records may need to remain for security, disputes or required transaction handling.

We may collect details you submit for an account, verification results, login and session data, browser or device signals, cookie settings and payment-status references. If you use DANA, OVO, GoPay or QRIS, the provider also processes data under its own terms and Privacy Policy.

We use a DANA or QRIS reference and its status to match an account transaction, investigate a mismatch and maintain a payment record. We do not treat that reference as access to your separate wallet. OVO, GoPay, bank transfer and virtual account records follow the same matching purpose.

Yes. Contact us through the account-help route with your account identifier and describe whether you want access, correction, restriction or removal. We may complete a phone-verification step before responding. Where local law permits, we will explain the result and any record that must remain.

We retain each category for as long as it supports account access, security, payment reconciliation, dispute handling or a required record. When the purpose ends, we assess deletion or anonymisation. A request may be limited where removing a record would undermine security or transaction obligations.

Cookies and device signals can differ between your mobile browser and desktop browser because each has separate sessions and settings. We use them for login continuity, selected preferences and security checks. You can manage permissions in your browser, but required cookies may be needed for account access.

Yes. Account access and any related data request depends on local law and applies where local law permits. We may need to limit access, retain a record or request additional verification when a legal, security or payment obligation requires it. Our support route can explain the result.