Reference

nagaplay99 Privacy Policy Explained Clearly

nagaplay99 Privacy Policy explains what we collect when you create an account, sign in from a mobile device, or check DANA, OVO, GoPay and QRIS status.

Account dataWallet detailsDevice controlsYour privacy choices
nagaplay99 nagaplay99 Privacy Policy Explained Clearly
CONTACT ROUTES

Privacy Help From Your Account

A clear support route matters when a privacy question appears beside a login or wallet status issue. We ask you to contact us from the account support path where possible, because that lets us connect your request with the correct account record. Include the phone number linked to your account, the subject of your request and any relevant payment reference, while leaving out passwords or one-time codes. For access concerns, our team can explain the next verification step where local law permits.

Team online

Account privacy request

Use the support path connected to your account when you want to ask what personal details we hold, why a field is needed or how a record relates to your login. We may ask you to confirm the phone number on the account before discussing private details.

Wallet record question

For a DANA, OVO, GoPay or QRIS status question, send the relevant receipt reference through account support. We use the reference to locate the payment event, while you should never send a wallet PIN, password or one-time verification code.

Access correction path

If your name, phone number or verification detail is wrong, tell us which field needs attention and why. We can explain the available correction step and may request account checks before changing data that protects access.

DATA PRACTICES

How We Handle Your Personal Details

We keep privacy work close to the actual account actions you take: creating access, confirming a phone number, checking a wallet state and asking for support.

Account creation

When you open an account, we use the details needed to create and maintain that account, including your phone number and verification state. We use this record to connect sign-in activity with your access request and to avoid sending private account details to the wrong person.

Phone verification

Phone verification helps us check that an account access request belongs to the person who controls the linked number. Keep your verification code private. If a code arrives when you did not request access, contact support through the account path rather than sharing it.

Device signals

When you sign in on a phone, tablet or desktop browser, we may record device and browser signals connected with security checks. These signals can help us spot unusual access without reading private content stored on your device.

Cookies and sessions

Cookies and session records help keep your account connected while you move from login to the lobby or return to a payment status page. You can manage browser cookie settings, though changing them may require another sign-in or affect some account functions.

Retention controls

We retain account, security and payment-reference records for as long as needed for the purposes described in this policy, account administration and applicable legal duties. When a record is no longer needed, our handling follows the retention process attached to that record type.

Change or deletion request

You can ask us to correct, access or delete personal details through account support. Some records may need to remain when they relate to account security, a payment reference or a legal duty; we will explain the reason and the available next step.

Privacy Policy Questions Before Access

These Privacy Policy answers address the searches we hear before an account is opened and the questions that arise after a phone verification, mobile sign-in or wallet status check. We keep the answers tied to nagaplay99 account records rather than making broad claims about unrelated services. Where access or a request depends on a legal requirement, we will explain that condition through the available support path.

Our Privacy Policy treats your linked phone number as account data used for access and verification. We may use its verification state to connect a sign-in request with your account. Do not send the number's one-time code to support; we will explain any required check through the account support path.

Yes. The Privacy Policy covers payment references and status connected with DANA, OVO, GoPay and QRIS. We use those records to match a receipt or status event with your account. We do not need your wallet PIN or password for a privacy request.

You can request access to personal details held in your account record through account support. Include the phone number linked to the account and describe the records you want to ask about. We may verify your identity before discussing private data or providing an access response.

Send a correction request through the account support path and identify the field that is inaccurate, such as a phone number or verification detail. We may ask for an account check before changing it. This protects your access and helps prevent another person from altering your record.

It does. Cookies and session records can keep your mobile browser connected while you move between sign-in, the lobby and a QRIS status page. Browser settings can limit cookies, but that may end a session or require you to sign in again before continuing.

Our Privacy Policy says we keep records for the period needed for account administration, security, payment-reference handling and applicable legal duties. Retention differs by record type. You can ask support about a particular record and whether correction or deletion is available where local law permits.

Use the support path connected with your account and state that your request concerns the Privacy Policy. Include a clear subject and the relevant account or receipt reference, but omit passwords, wallet PINs and one-time codes. We will explain the verification step and next action.