Reference

nafa55 Privacy Policy For Your Account

Our Privacy Policy explains what nafa55 collects when you open an account, use DANA or QRIS, and move between the lobby and cashier path.

Clear data purposesWallet record detailsAccount access choicesDirect contact path
nafa55 nafa55 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Account Support

A clear contact route matters when a Privacy Policy question concerns your login, wallet record or identity check.

Account message Use the account support path when your question concerns phone verification, a login event or a data record connected with Live Roulette Turbo. Include your account identifier and the approximate date, but never send your password or a one-time verification code.
Wallet query For DANA, OVO, GoPay or QRIS records, share the payment reference and status shown in your account. We use those details to locate the relevant event and explain what was stored, rather than asking you to repeat your full wallet credentials.
Privacy request Ask us to access, correct, restrict or delete eligible personal data through the available support route. We may first confirm account ownership by phone verification so a request cannot expose your records to another person.
HANDLING DETAILS

QRIS Cookies And Account Security

We keep this policy practical by connecting each data practice to an account action you can recognise.

Account data

We use your phone number and verification result to create and protect account access. Login history can be linked to the device and browser path used to reach the lobby, helping us investigate an unfamiliar session without treating every device change as misuse.

Payment records

A DANA, OVO, GoPay or QRIS event may carry a reference, amount, status and time needed for reconciliation. Bank transfer and virtual account records can follow the same operational purpose, so support can match a receipt without requesting your banking password.

Cookies

Cookies can remember session choices, security settings and basic navigation signals. They help the account path move from phone verification to the lobby, but they do not give us access to your wallet password. You can manage browser cookie controls on your device.

Device security

We may compare device, browser and login signals when an account opens from an unusual path. If a security check interrupts access to Crash Skyrise Arena, contact support through the account route instead of creating a second account.

Record retention

We keep personal data for the period needed to operate the account, resolve a payment query, protect against misuse or meet a legal requirement. When a stated purpose ends, we assess whether the record can be deleted, anonymised or retained for a narrower reason.

Your requests

You can ask what personal data we hold, request a correction, question a processing purpose or seek deletion where eligible. We may request account details and phone verification to confirm that the request comes from the person connected to the record.

nafa55 Privacy Policy Questions

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder before opening an account or connecting a wallet. We explain the practical steps for data access, payment references, cookies, device checks and account changes. If your situation is not covered, send the question through the available support route with your account identifier, keeping passwords and verification codes private.

It covers account details, phone verification, device and login signals, cookies, payment references and support requests. It also explains purposes, retention and your request options for records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account request to the person opening it and supports later security checks. We may use the result to protect access, confirm a Privacy Policy request or investigate an unusual login, but you should never send a one-time code to support.

Yes. The Privacy Policy covers operational details such as a QRIS, DANA, OVO or GoPay reference, status and timestamp. These details help us reconcile an account event and answer a receipt question; they do not require us to receive your wallet password.

Use the support route available inside your account and state whether you want access, correction, restriction or deletion of eligible data. Include your account identifier and the relevant date or payment reference. We may confirm ownership before handling the request where local law permits.

We retain records for the operational, security, dispute or legal purpose stated in the Privacy Policy. A payment reference may remain while a receipt issue is being resolved. When the purpose ends, we assess deletion, anonymisation or a narrower retention need.

Cookies can support a session and remember selected settings, while device and browser signals can help identify an unusual login path. They may be associated with account activity for security, but cookie controls remain available in your browser and do not reveal your wallet password.

The policy is written for account access from Indonesia and applies to the relevant data handling where local law permits. If eligibility or access differs for your location, it depends on local law. Contact support if you need the policy position for your account.