Reference

9nagawin Privacy Policy For Your Account

9nagawin Privacy Policy explains what we collect when you open an account, use the lobby, contact support or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity requests
9nagawin 9nagawin Privacy Policy For Your Account
CONTACT PATHS

Contact Us About Privacy Policy

A direct support route helps you ask what we hold, why we use it or how to correct an account record. Start from the support link while signed in, include the email or phone tied to your account, and avoid sending a password or wallet PIN. If you are in Makassar, the same account path applies as elsewhere in Indonesia, where local law permits.

Team online

Account request

Use our account support path to ask for a copy of personal data, a correction to your contact detail or clarification about a security check. We may ask you to confirm ownership through the account step before releasing private records.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the transaction reference and date in your message. We use those details to locate the relevant status without asking you to reveal a wallet PIN.

Access concern

If a sign-in alert, device change or account lock concerns you, contact support through the site path and describe what you saw. We can review the account trail and explain the next verification step where local law permits.

DATA HANDLING

Browse How We Protect Your Privacy

We keep the Privacy Policy practical by linking each data use to an account action: sign-in, wallet matching, support or security review.

Data we collect

We may collect account identity, contact details, login events, device information, cookie settings, support messages and payment references. When you use QRIS or a named wallet, we use the transaction details needed to match status rather than requesting your private wallet PIN.

Why we use it

Account details help us create access and respond to you. Device and login records help detect unusual activity. Payment references help us trace a pending step. Support content lets us answer the Privacy Policy request you actually sent.

Cookies and devices

Cookies can remember a session, store preferences and help us understand whether a page loads correctly. You can review browser cookie controls on your phone or desktop, although changing them may affect sign-in or the display of account pages.

Account security

Keep your password private, sign out on shared devices and contact us when a login looks unfamiliar. We may compare account, device and verification details before changing access, so a request goes to the account holder rather than another person.

Retention approach

We keep personal records for as long as needed for the stated account, support, security or legal purpose. After that period, we remove, anonymise or restrict the record where the applicable process allows us to do so.

Requesting changes

Ask us to access, correct or delete relevant personal data through support. Include your account contact and the request type. We may need an account verification step, and we will explain any limit where local law permits the request only in part.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers address the searches we hear before an account is opened: what data we use, how wallet references are handled, what cookies do, how access requests work and how to reach us. If your question is not covered, send support the account contact and a short description rather than sharing secret credentials.

The 9nagawin Privacy Policy covers data connected with account creation, sign-in, device access, cookies, support messages, security checks and payment references. It explains why we use those records and how you can ask for access, correction or deletion where local law permits.

We do not ask you to send a wallet PIN through support. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we use the account and transaction references needed to check status, match a record and investigate a payment question.

Cookies may keep your session active, remember preferences and help us identify loading issues. You can manage them in your phone or desktop browser. Blocking some cookies can affect sign-in or account pages, but it does not remove records already required for security or legal purposes.

Yes. Contact support through the site account path and ask for a copy of the personal data connected with your account. Include the account email or phone, but never send your password or wallet PIN. We may verify ownership before responding.

You can ask us to correct inaccurate details or delete data that no longer needs to be kept. Send the request through support with the relevant account contact. We may retain records needed for security, payment tracing or legal duties where local law permits.

The handling described here applies to the site account path, while specific rights or access conditions can vary by jurisdiction. Access or eligibility depends on local law. We will explain the relevant process when you contact us from Indonesia or another supported location.

Contact support promptly through the account path, describe the device or login event and change your password from a secure device. Do not share secret credentials. We can review the account trail and request an ownership check before discussing private details.