Reference

nx303 Privacy Policy for Your Account

Our nx303 Privacy Policy explains what we collect when you create an account, verify your phone, sign in on mobile, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextPhone verification detailsPrivacy request path
nx303 nx303 Privacy Policy for Your Account
PRIVACY CONTACT

Where to Ask About Your Privacy

A direct support route helps you ask about the Privacy Policy without explaining your concern repeatedly. Sign in first when you can, because the account path lets us match a request with the correct phone verification record. If access is unavailable, include only the details needed to locate the account and never send a full password or wallet security code. We use the same support path for data questions, correction requests and concerns about a payment reference.

Team online

Account access

Use the account support route when you need to ask which personal details are connected with your phone verification. We may ask for an account identifier before discussing records, so your request does not expose private data to another person.

Wallet records

For DANA, OVO, GoPay or QRIS questions, select the wallet-related support path and include the date, amount reference and account identifier when available. Do not send your wallet PIN, one-time code or complete banking credentials with a privacy request.

Data requests

Ask through the privacy contact route if you want a copy, correction or clarification about retained account data. We review the request against account ownership details, explain any lawful restriction and reply through the contact method already connected to your account.

DATA CONTROLS

Inside nx303 Data Handling Controls

We keep this Privacy Policy practical by linking each data type to an account action: phone verification supports sign-in, device signals help detect unusual access, and wallet references help reconcile DANA, QRIS…

Account data

We may hold your account identifier, phone verification status, sign-in history and support messages. These details let us confirm ownership before discussing a Privacy Policy request and help connect a question to the correct account rather than another account with similar contact details.

Cookies and sessions

Our mobile and desktop pages can store session cookies or similar browser data so your sign-in state and selected page path work correctly. You can clear browser storage through your device settings, although doing so may require you to verify your phone again.

Wallet references

DANA, OVO, GoPay and QRIS may return a reference, status or receipt detail linked to your account action. We use that record to reconcile the transaction path and handle support questions; we do not ask you to place wallet PINs in chat.

Account security

Phone verification is required before account access, and device or login signals can be checked when activity appears unusual. If a sign-in concern involves Live Blackjack Salon or another lobby area, security checks still apply before we discuss account data.

Retention choices

We retain personal records only while they support account operations, security checks, dispute handling or a legal requirement. When a record no longer has a valid purpose, our handling process is to remove it, anonymise it or restrict access where appropriate.

Changes and contact

You can ask us to correct inaccurate account details or explain how a record is used through the privacy contact route. Include the relevant account identifier, but omit passwords and wallet codes. We may request additional ownership proof before making a change.

Privacy Policy Questions About nx303

These Privacy Policy answers focus on the account steps and local wallet records you are most likely to ask about before opening an account. We explain what happens during phone verification, how browser data is used, what payment references mean and how to contact us. Where access or a request is affected by Indonesian requirements, the outcome depends on local law.

The nx303 Privacy Policy covers account details, phone verification, sign-in records, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security handling and how to request access or correction.

Phone verification helps us confirm that the person requesting account access or a data change controls the registered contact. It also supports account security when a sign-in or wallet question is raised. We may request another ownership check where local law permits.

Yes. The Privacy Policy covers payment references, status details and receipt information connected with DANA or QRIS activity. We use these records to reconcile an account action and answer support questions. Wallet PINs, one-time codes and complete banking credentials should not be sent to us.

On a mobile browser, we may use session cookies or similar storage to keep your sign-in path working and remember selected page settings. Clearing browser data can end the session and trigger phone verification again. Your device browser controls how these stored items are removed.

Use the privacy contact route linked with account support and identify the account connected to your request. Tell us whether you want access, correction or clarification. We verify ownership before responding, and the available action depends on local law and required retention.

We keep records for the period needed for account operations, security checks, payment reconciliation, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we remove it, anonymise it or restrict access according to our internal process.

Yes. Contact support through the account or wallet route and provide the account identifier, approximate time and relevant DANA, OVO, GoPay or QRIS reference. Do not include passwords or security codes. We can investigate the record after confirming account ownership.