Reference

Open the nos188 Privacy Policy Before Access

The nos188 Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby and use payment records such as DANA or QRIS.

Account dataWallet recordsCookie choicesContact requests
nos188 Open the nos188 Privacy Policy Before Access
CONTACT ROUTES

Ask nos188 About Privacy Access

A clear contact route matters when your account record or wallet status needs attention.

Account privacy request Send a request through the site support contact when you need to ask about account data, phone verification or a correction. We may ask you to confirm the account step involved before discussing details, so the request stays connected to the right nos188 record.
Wallet record question For a DANA, OVO, GoPay or QRIS record, include the date, payment rail and visible reference rather than a password or full wallet credential. Our support route can explain which record is held and what privacy action may apply.
Access and deletion request If you want a copy, correction or eligible deletion of personal data, state that request clearly through the support contact. We will use account verification before acting, because privacy changes must not expose your record to another person.
DATA PRACTICES

Browse How We Handle Your Account Data

The Privacy Policy is designed around the actions you take on the account rather than broad statements.

Account details

When you create an account, we handle the details needed to identify the account and complete phone verification before access. Keeping those details accurate helps us connect a privacy request to you without asking for unnecessary material.

Device signals

A mobile browser may send device, browser and session signals while you move from login to the lobby. We use these signals for account protection and access checks; they are addressed in the Privacy Policy separately from your submitted profile details.

Cookies

Cookies can remember session choices and help pages load in the path you selected. Our policy explains their role and the choices available through your browser. Removing them may require you to complete phone verification again during a later login.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create payment references linked to your account. We use the record needed to check status and support a transaction, not a request for your wallet password.

Account security

Phone verification, session checks and account contact details help us reduce the chance of an unauthorised privacy request. Never send your password in a support message. We may request reasonable confirmation before releasing, correcting or removing account data.

Retention and changes

We retain records for the period described in the Privacy Policy, taking account of account, security and transaction needs. If a detail is wrong or you want an eligible change, contact us with the requested action and we will explain the next step.

Check Common nos188 Privacy Policy Questions

These Privacy Policy questions focus on the account actions Indonesian customers ask about most often. You can use them before opening an account, while checking a DANA or QRIS reference, or after moving between a mobile browser and desktop. If your situation is not covered, send the request through the site support contact and include only the details needed to identify the account.

It covers details submitted during account creation and phone verification, device and browser signals, cookies, support messages and payment references. It also explains use, retention, security and request rights connected with account access, where local law permits.

Phone verification helps connect the account to the person making an access or privacy request. We use it as an account check before discussing personal records or changing them, and we do not ask you to place a password in a support message.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help us check a wallet or transaction status without asking for your full wallet credential.

You can request a correction through the site support contact. State which detail is inaccurate and identify the account using the requested verification step. We will explain whether the change is available under the Privacy Policy and local requirements.

Send a clear data-access request through the support contact and include the account phone number or another requested account reference. We may verify your identity first, then explain the records available and the format or timing for the response.

Retention depends on the type of record and the account, security or transaction reason for keeping it. The Privacy Policy sets out the relevant approach. You can ask support about a particular record without sending your password or full payment credentials.

You may ask about deletion through the site support contact. We will verify the request and explain which data can be removed, which records may need to remain for account or transaction reasons, and how local law affects the available action.