Reference

nirwana88 Privacy Policy for Your Account

Your account details, DANA activity and device access are handled under the nirwana88 Privacy Policy, so you can see what we collect and why.

Account dataWallet recordsDevice accessCookie choices
nirwana88 nirwana88 Privacy Policy for Your Account
CONTACT PATHS

Ask About Your Privacy Policy Rights

A clear contact path matters when you want to understand a stored record or change an account detail. We route privacy questions through the account help area, close to the cashier history, so your request can include the relevant reference without exposing wallet credentials. If you are in Denpasar, the same policy and contact route applies where local law permits.

Team online

Account help

Use the account help route for a copy request, correction request or question about phone verification. Include your account identifier, but never send a password, wallet PIN or complete payment credential.

Payment record

For DANA, OVO, GoPay, QRIS or bank transfer questions, share the visible transaction reference and status. We use that detail to locate the relevant record without asking for unnecessary wallet access.

Access concern

If a device session or login record looks unfamiliar, contact us through account help and describe the date and device path. We can direct the security check while keeping your private credentials out of the request.

HANDLING YOUR RECORDS

How We Apply Privacy Controls

We keep this policy practical by linking each data use to an account action, such as phone verification, wallet status or a request to access the lobby.

Data handling

We collect account details, verification results and relevant transaction references to operate your requested account actions. We limit the use of DANA, OVO, GoPay and QRIS records to matching status, support and security needs.

Cookies and sessions

Cookies can keep a session active, remember selected settings and help us identify an unusual login path. You can manage browser cookie controls, although changing them may require another login before account access.

Account security

Phone verification and device-session checks help us assess access requests. We do not need your wallet PIN or password in a support message, and we ask you to review unfamiliar sessions through the account path.

Retention periods

We retain account and payment records only for the operational, security and legal purposes connected with the account relationship. Retention can vary by record type, including QRIS status, bank reference and verification history.

Access requests

You can ask what account, device or payment records we hold by contacting account help. We may request verification before releasing details, so a private record is not disclosed to the wrong person.

Changes and contact

To correct a name, phone detail or other account field, send the requested change through the contact route shown after login. We record the request, check the account and explain any limit that applies.

Privacy Policy Questions About nirwana88

These answers address the searches we hear most often about the nirwana88 Privacy Policy. They cover the records created during account access, local wallet activity, device sessions and requests for copies or corrections. If your case involves a specific reference, use the account help route so we can check the correct record.

The Privacy Policy covers account details, phone verification, device sessions, cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps connect an access request with the correct account and supports security checks. We use the result for account protection and do not ask you to place a password or wallet PIN in a message.

Yes. The Privacy Policy covers QRIS, DANA, OVO and GoPay status records, including references used to match a cashier request. We do not need your wallet password to check a transaction status.

Use the account help route after login and ask for a data copy. Include your account identifier and complete any verification request; we may limit disclosure when identity cannot be confirmed.

You can request a correction through account help for details such as your phone number or account name. We check the request against your account before changing the relevant record.

Cookies can remember a session and selected settings when you move from login to the lobby on mobile. Browser controls can remove them, but you may need to verify access again.

The Privacy Policy applies to account and payment records handled for Indonesian access where local law permits. Eligibility and access depend on local law, which can affect whether an account action is available.