Reference

na2121 Privacy Policy for Your Account

Your account, wallet references and lobby activity stay connected to a clear Privacy Policy, so you can understand what we collect before opening access.

Account clarityWallet data contextDevice accessCookie choices
na2121 na2121 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Near Wallet Status

A clear contact route helps when you want to ask about a stored account detail, a cookie choice or a wallet reference. From your signed-in account, use the support path placed near the cashier and include the phone number or email attached to your account. We use that account step to confirm that a privacy request comes from you, whether the question concerns DANA, QRIS or a device sign-in.

Team online

Account request

Send a privacy question from the signed-in account path beside the cashier. Include the account phone number and the subject of your request, so we can locate the relevant record without asking you to send a wallet password.

Wallet reference

If your question concerns DANA, OVO, GoPay or QRIS, share the transaction reference rather than private wallet credentials. We can use that reference to check which account record needs clarification while keeping the payment detail limited.

Access concern

For a device or sign-in concern, tell us whether you used the mobile browser or desktop path and when the prompt appeared. This gives our support team a practical route to check account security without collecting unrelated browsing data.

DATA PRACTICES

Cookies, Devices and Account Records

We keep this policy practical by separating account identity, payment references and browsing signals rather than treating every click as the same type of data.

Account identity

We use the phone number or email attached to your account to match sign-in and verification steps. If you ask us to correct a spelling or contact detail, we may request confirmation through the same account path before changing the record.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us connect a cashier event with the right account. We do not need your wallet password for that matching process, and support requests should never include it.

Mobile browser

On a phone, cookies can remember a session and selected privacy preferences in the browser path. Clearing browser data may remove those choices and require phone verification again when you return to the account.

Lobby activity

Records may include the account action associated with titles such as Fishing War Arcade, Crash Countdown Round or Gamelan Riches Slots. We use this context to investigate account access and support questions, not to create unrelated personal profiles.

Retention period

We keep account and transaction references for as long as needed to operate access, resolve an open request and meet applicable legal duties. When a record is no longer needed for those purposes, our handling moves toward deletion or separation.

Change requests

You can ask for a copy, correction or clarification through the signed-in support route. Tell us which record you mean, such as a device entry or QRIS reference, and we will assess the request under the law that applies to your account.

Privacy Policy Answers for na2121 Accounts

These Privacy Policy answers focus on the questions you may have before creating an account or returning from a new device. We cover wallet references, cookies, verification, retention and requests for access or correction. If a situation is not listed, use the signed-in support path and describe the specific record involved.

The na2121 Privacy Policy covers account identity, phone verification, device signals, cookies, wallet references and activity connected with account support. It explains how we use and retain those records when you access the website through a mobile browser or desktop path in Indonesia.

Yes. We may retain a DANA or QRIS transaction reference to connect a cashier action with your account. The same approach can apply to OVO, GoPay, bank transfer or virtual account records. We ask you not to send wallet passwords or unrelated credentials.

Phone verification helps us confirm that the person entering the account is connected to the registered contact detail. It also supports a device-access check when you return through a mobile browser. We use the verification record for account access and security purposes.

Cookies can remember your session and selected privacy settings in the browser. If you clear cookies on your phone or desktop, those choices may disappear and the account may request verification again. You can manage browser cookie settings before returning to the account.

You can request a copy, correction or clarification through the signed-in support route beside the cashier. Identify the record, such as an account contact detail, device entry or payment reference. We verify the request and assess it under the law applying to your account.

We retain records while they are needed for account operation, security checks, support resolution or applicable legal duties. The period can differ by record type and local requirement. When the purpose ends, we move toward deletion or separation from active account handling.

If you cannot reach the signed-in route, use the contact option presented on the account access screen and describe the issue without sending a password. Mention whether the problem appeared on mobile or desktop, so we can direct the request to the right privacy check.