Reference

nexslot Privacy Policy For Your Account

nexslot Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Andar Bahar or use DANA and QRIS, and how we…

Account dataWallet recordsDevice controlsPrivacy requests
nexslot nexslot Privacy Policy For Your Account
PRIVACY HELP

Find Your Privacy Contact Path

A clear contact path helps when a Privacy Policy question concerns your login, wallet status or a receipt.

Account request Ask us to explain the personal data connected with your account.
Wallet receipt For a DANA, OVO, GoPay or QRIS privacy question, attach the transaction reference rather…
Device concern If a phone or browser signal appears in your account activity, contact us through…
DATA PRACTICE

See How We Handle Your Policy Rights

We treat the Privacy Policy as an operating rule for account access, not as a page kept apart from the lobby.

Data collection

We may collect account contact details, verification data, sign-in events, device characteristics and activity linked to games such as jokerking…

Cookie choices

Cookies may keep your session active, remember a language or preserve a page setting.

Account security

Phone verification and sign-in checks help us distinguish your account activity from an unfamiliar device.

Retention timing

We retain records only for the period needed for the purpose described in the Privacy Policy, account security, transaction reconciliation…

Correction requests

If your account name, phone number or contact email is outdated, ask us to correct it through the privacy contact…

Deletion questions

You can ask whether a record may be removed, subject to account security, transaction duties and local law.

Answer Your Privacy Policy Searches

These Privacy Policy answers focus on the account questions you are most likely to have before opening an account or checking a wallet record. They cover the data created by sign-in, phone verification, cookies and payment references, with the same local-law wording used throughout our policy. If your situation is not listed, use the privacy contact path rather than sending sensitive credentials.

The nexslot Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, game activity and payment references. It explains how we use, protect, retain and disclose those records, plus how you can request access, correction or deletion where local law permits.

We use payment references to connect a wallet event with the correct account, check a receipt and resolve a pending status. We do not need your wallet password for that process. The Privacy Policy explains the purpose and retention of each transaction record.

Yes. The Privacy Policy describes device and browser signals used to maintain a session, protect account access and identify unusual sign-in activity. You can ask us what category is linked to your account, and we may verify ownership through your registered phone or email.

Use the privacy contact path beside account help and state that you want a copy of your account data. Include your registered phone or email, but never include a password. We may perform an ownership check before sending records or confirming what we hold.

You can ask us to correct an outdated phone number or email through the Privacy Policy contact route. Because phone verification can affect account access, we may ask for an ownership check before changing it. We will explain the next account step after receiving your request.

Retention depends on the purpose of the record, account security needs, transaction reconciliation and legal requirements. The Privacy Policy explains the applicable period or criteria. You can ask about a specific DANA, QRIS, bank transfer or virtual account reference through the privacy route.

You may request deletion through the Privacy Policy contact path, where local law permits. Some records may need to remain for security, transaction reconciliation or a legal requirement. We will identify the retained category, explain why it remains and confirm what action we can take.