Reference

nona88 Privacy Policy for Indonesia Accounts

The nona88 Privacy Policy explains what we collect when you open an account, why we use it, and how you can ask about your data.

Clear data purposesPhone verification explainedIndonesia wallet contextAccess depends on local law
nona88 nona88 Privacy Policy for Indonesia Accounts
CONTACT DATA HELP

Open Support When Privacy Questions Stall

A direct support request gives you a practical route when a Privacy Policy question concerns login, phone verification or wallet status.

Account access request Ask us to check a phone verification record or sign-in detail through the support…
Wallet data question For DANA, OVO, GoPay or QRIS records, share the date and visible reference only.
Correction request If your name, contact detail or account record needs correction, describe the exact field…
DATA CONTROL POINTS

Browse How We Handle Your Records

Privacy choices are easier to use when each part of the account journey has a clear purpose.

Account details

We use your account details to create access, send account messages and connect requests to the correct record.

Phone verification

Before account access, phone verification helps us distinguish the account holder from an unknown sign-in attempt.

Cookies and devices

Cookies can keep a mobile browser session active and remember selected settings.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a cashier event with your account.

Retention choices

We keep personal records for account operation, security, dispute handling or legal needs, then remove or restrict them when those…

Your request route

Contact support to ask for access, correction, deletion where local law permits, or clarification about use.

Find Privacy Policy Answers Before Access

These Privacy Policy answers address the questions you may have before opening an account or returning through a mobile browser. Each answer stays focused on personal data, account access, wallet references and the support route. If your situation is not listed, contact us with the smallest useful set of details, and remember that access depends on local law.

It covers account details, phone verification, sign-in events, device signals, cookies, payment references, support messages, retention and requests to access or correct personal data.

Phone verification helps protect account access and connect a request to the correct account. We record the result and related access event, not your phone password or wallet PIN.

No wallet PIN or one-time code is needed for our payment reference checks. We may retain a DANA, OVO, GoPay or QRIS status reference to match an account event.

Cookies can keep your mobile browser session active and remember settings. They may also help us diagnose access errors, while your support request can ask how cookie data is being used.

Yes, contact support and state that you want an account data request. We may ask for account identifiers or phone verification to confirm ownership before sharing relevant records.

Send support the account field that is wrong and the corrected detail. We check the request against your account before updating records, and local law determines the available correction process.

You can request removal or restriction through support where local law permits. Some records may remain when needed for account security, payment reconciliation, disputes or legal obligations.