Reference

nila88 Privacy Policy for Your Account Data

Your DANA, OVO, GoPay and QRIS records stay connected to the account details needed for access, and our Privacy Policy explains each use in plain English.

Clear data purposesWallet record contextRequest paths
nila88 nila88 Privacy Policy for Your Account Data
REQUEST HELP

Ask nila88 About Privacy Policy Requests

A clear support path helps when your Privacy Policy question concerns a login record, wallet status or an old device session. Start from the support route linked in your account and include the phone number or receipt reference connected to the request. If you are in Yogyakarta, the same online privacy path applies, while access still depends on local law.

Team online

Account privacy request

Use the account support route to ask what personal details are linked to your phone verification. We may ask for an account step that confirms your identity before releasing private records.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, send the payment receipt reference through support. We compare the reference with the account record and explain the status without requesting your wallet password.

Device access concern

Tell us if a browser or phone session no longer belongs to you. We can review the related security event, help secure the account and explain which data the Privacy Policy covers.

DATA HANDLING

Explore How Our Privacy Policy Works

We keep the Privacy Policy practical by tying each data category to an account action, from phone verification to a receipt check.

Data collection

We collect account details you provide, verification results, selected settings and support messages. Device and session signals help us identify an unusual login without treating every browser visit as a new account.

Cookie choices

Cookies can keep your login path working and help us detect repeated security failures. You can manage browser cookie controls, although turning them off may affect the account session described by this Privacy Policy.

Account security

Phone verification comes before account access, and security checks may compare a new device with prior session activity. Never send us your wallet password; DANA, OVO, GoPay and QRIS credentials remain with their providers.

Retention period

We retain account, receipt and support records only for the period needed for the stated purpose or an applicable legal duty. When a record is no longer needed, our handling follows the deletion process available to us.

Changing your details

Ask support to correct a phone detail, contact detail or account record by using the privacy request path. We verify the request against your account before changing information that could affect access.

Who receives requests

Our support team receives privacy questions through the account contact route. Payment providers may separately hold their own transaction data, so a DANA, OVO, GoPay or QRIS request may also require their process.

Browse nila88 Privacy Policy Questions

These Privacy Policy answers cover the searches we hear most often before account creation. We explain the data connected to phone verification, wallet receipts, cookies, device access and deletion requests so you know which step to take. If your situation involves a local requirement, access and available rights depend on local law.

It covers account details, phone verification, device and session signals, cookies, support messages, game-session references and payment receipts linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use the verification result to connect the account to the correct access step and help detect unusual sign-ins. The Privacy Policy explains this use and the request path for checking related records.

Yes. We may retain transaction references and status details for DANA, OVO, GoPay and QRIS so support can match a receipt to your account without asking for your wallet password.

Cookies can preserve your session and help identify repeated security failures. You control them through your browser, but disabling cookies may interrupt the account path described in the Privacy Policy.

Yes. Send a correction request through the account support route and identify the relevant phone or account detail. We confirm your identity first, then explain whether the change is available under local law.

Use the privacy contact path in your account and specify the records you want removed. We assess the request against retention duties, transaction references and local law before confirming the result.

Our support team handles questions sent through the account contact route. For data held directly by DANA, OVO, GoPay, QRIS or a bank, you may also need that provider's own privacy process.