Reference

Open the nagaselot77 Privacy Policy

The nagaselot77 Privacy Policy explains what we collect when you create an account, sign in from a phone, browse Live Roulette Elite or use DANA and QRIS.

Account dataWallet recordsCookie choicesAccess requests
nagaselot77 Open the nagaselot77 Privacy Policy
ASK ABOUT PRIVACY

Contact us when your data needs attention

A clear contact path helps you ask about the Privacy Policy without sending sensitive details through the wrong route. Use the account support path for access, correction, deletion or consent questions, and include the phone number linked to your account rather than a wallet password. If a receipt from BCA, BRI, Mandiri or BNI needs checking, share only the transaction reference requested by our support team. You can also raise a question beside the cashier path when the matter concerns a wallet record.

Team online

Account support path

Use our account support route for a copy of your personal data, a correction request or a question about how the Privacy Policy applies to your sign-in history. We ask for the account phone number so we can match the request without asking you to disclose a password.

Wallet record check

When your Privacy Policy question concerns DANA, OVO, GoPay or QRIS activity, send the relevant receipt reference through the cashier support path. We can check the account link while you keep your wallet PIN, one-time code and full authentication details private.

Access request route

For deletion, correction or a copy of stored data, state the exact request and the phone number attached to your account. We may ask for an account step to confirm identity, because changing private records without verification could expose your account.

DATA HANDLING

Explore the safeguards behind this policy

The Privacy Policy is connected to practical account controls rather than a general statement. We use sign-in and device signals to spot unusual access, separate wallet references from authentication secrets and apply…

Collected account details

We may collect your phone number, account identifiers, sign-in timestamps, device type, browser signals and messages you send to support. These details help us return you to the correct account and investigate a failed access step without treating every request as a new registration.

Cookies on your device

Essential cookies can remember an active sign-in path and support basic account navigation. Browser settings let you clear or restrict cookies, although some account functions may then ask you to authenticate again before showing private pages.

Wallet and cashier records

A DANA, OVO, GoPay or QRIS reference can be linked to your account record so a receipt status can be checked. We do not need your wallet PIN or one-time code for that matching step, and you should never send either to support.

Account access security

Phone verification is used before account access, while sign-in events and device signals can help us identify unusual activity. Keep your verification code private, sign out on shared devices and contact support if a login appears that you do not recognise.

Retention and deletion

We remove or anonymise data when it is no longer needed for account operation, security checks, dispute handling or legal duties. A deletion request may not erase records that must remain for those reasons, and we will explain the relevant restriction where applicable.

Your policy requests

You can ask how your data is used, request a copy, seek a correction or ask about deletion through the account support route. Access or action depends on local law, and we may verify the phone number attached to the account before responding.

Find answers about your Privacy Policy

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the account step, device behaviour, local wallets, cookies, retention and the route for requesting changes. If your situation is not listed, send the question through account support with only the details needed to locate your account.

It covers personal data connected with your account, including phone verification, sign-in events, device signals, support messages, cookies and wallet references. It also explains why we use those records, how long they may remain and how to request access, correction or deletion.

Phone verification helps us confirm that the person requesting account access is connected to the registered account. It also reduces mistaken changes to personal data. Keep the code private; our support route does not need your wallet PIN or one-time payment code.

Yes. The Privacy Policy explains how we use DANA and QRIS references to match a receipt or status with your account. OVO, GoPay, bank transfer and virtual account references follow the same account-matching purpose, while each provider keeps its own records.

We may record device type, browser signals, sign-in time and related access events when you use the account from a phone or desktop. These details support account security and troubleshooting. They are not a request for your device password or private wallet credentials.

Essential cookies can keep an account session and basic navigation working, while browser controls let you clear or restrict them. Clearing cookies may require another sign-in. The Privacy Policy explains this use so you can make a practical browser choice before accessing private account pages.

Send the request through the account support path and identify the account phone number, the data concern and the action you want. We may verify account ownership before responding. Access, correction and deletion requests depend on local law and applicable retention duties.

We retain records only while they serve account operation, security, dispute handling or legal duties. Some wallet references or access logs may remain after you stop using the account for those reasons. If you ask about deletion, we will explain what can be removed.