Reference

idnslot Privacy Policy for Your Account

Our idnslot Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet referencesCookie choicesAccess requests
idnslot idnslot Privacy Policy for Your Account
CONTACT PATHS

Reach Us About Your Privacy Policy

A direct support request gives you a practical route when a privacy question involves login, phone verification or a wallet reference.

Account message Send a privacy request from your signed-in account and include the email or phone…
Wallet query If your question concerns DANA, OVO, GoPay or QRIS, mention the transaction date and…
Jakarta access If you are contacting us from Jakarta, use the same account contact route shown…
DATA HANDLING

Explore How We Handle Your Data

Clear handling rules help you understand what happens after each account action. We separate account identity, device activity and payment references where practical, limit access to operational needs, and use security checks…

Account records

When you open an account, we collect the details needed for account access and phone verification. We use them to identify your account, respond to requests and keep sign-in activity connected to the correct profile.

Device signals

Your browser or mobile device can provide session, language, operating system and security signals. These help us recognise unusual access around games such as Aviator or Bingo without asking for your private wallet PIN.

Cookies

Cookies can keep a session active, remember a selected setting and support security checks. You can manage browser cookie controls, but switching them off may require another login before you reach the lobby.

Account security

We may compare login patterns, phone verification and account changes before discussing private records. Never share your password or one-time code; our support route should not require either item from you.

Retention period

We keep records only as long as needed for account operation, security review, payment reconciliation, dispute handling or legal duties. A closure request does not always remove records that must remain for those reasons.

Change request

To correct or ask about your stored data, contact us through the account message path and name the field or record concerned. We may verify your identity before making a change or sharing details.

Browse Common Privacy Policy Questions

These answers address the searches we hear most often before an account is opened. Each response stays focused on the idnslot Privacy Policy, including account access, payment references, cookies, device records and requests to change or remove data.

It covers account details, phone verification, device and login records, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to connect account access to the correct person, help detect unusual sign-ins and answer account requests safely. We do not need your wallet PIN for this process.

Yes. The policy explains cookies used for sessions, settings and security checks. You can change browser controls, although removing cookies may sign you out before you return to your account.

We may retain a payment reference, date, amount status and account link so we can reconcile a transaction or answer a support request. We do not ask for your DANA or QRIS PIN.

You can send a request through the signed-in account message path, naming the record or field involved. We may verify your identity first, then explain whether the change or copy can be provided.

Retention depends on the purpose and applicable duties. We may keep records for account security, payment reconciliation, disputes or legal requirements after closure, while removing data no longer needed.

Use the support route shown inside your account and describe whether your request concerns login, cookies, device activity or wallet references. Access to idnslot depends on local law.