Reference

Slot List Indo Privacy Policy: Your Data Path

Slot List Indo Privacy Policy explains how we handle the account details, device signals and wallet records connected with your access to Dragon Tiger, Aviator and other lobby…

Account clarityWallet recordsCookie choicesPhone checks
Slot List Indo Slot List Indo Privacy Policy: Your Data Path
CONTACT ROUTES

Get Privacy Help Beside Account Access

A clear contact route matters when your account details or wallet record do not look right. We ask you to include the account identifier, the affected step and the payment reference if your question concerns DANA, OVO, GoPay or QRIS. For safety, we may ask you to confirm ownership before discussing personal data. Access remains where local law permits.

Team online

Account privacy request

Use our account support channel to ask what personal details are connected with your sign-in. Include your registered phone number and the exact correction or access request you want us to assess.

Wallet record query

When a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt reference and date through support. We use those details to locate the relevant record without requesting your wallet password.

Device access concern

Tell us if a phone or browser no longer belongs to you. We can review the account access trail, explain the next verification step and help protect the account before discussing stored personal details.

DATA PRACTICE

Your Cookies, Devices And Records

We handle this policy area through practical account controls rather than vague promises. A phone verification step helps us distinguish an account owner from an unknown sign-in, while cookie settings affect saved…

Account details

We may hold your registered phone number, account identifiers and verification status so we can complete sign-in checks and answer account questions. We use these details for the stated account purpose rather than unrelated messages.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can include a reference, amount status and time. We use this transaction trail to match your request and investigate a missing or disputed entry.

Cookie controls

Cookies can remember a session choice and help identify unusual sign-in behaviour. You can manage browser cookie settings on your phone or desktop, although changing them may require another account verification step.

Device signals

Your browser type, device path and access time may be recorded when you move from account sign-in to the lobby. These signals help us investigate unfamiliar access without reading private content on your device.

Retention approach

We retain account, payment and support records for as long as needed for the service, security checks or lawful duties. When a record is no longer needed, our handling process is designed to remove it.

Change requests

Ask us to access, correct or question the handling of your personal data through the account support channel. We may verify your identity first, then explain what action is available for that record.

Privacy Policy Questions About DANA Records

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover account access, cookies, device records and local wallet references, with a practical route back to our support channel when your question needs a personal response.

It covers account details, phone verification, cookies, device signals, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm account ownership before access and before discussing personal details. It also gives support a clearer way to investigate an unfamiliar sign-in or an account change request.

Yes. The Privacy Policy covers references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records used to match a payment question.

Contact our account support channel with your registered phone number and a clear request for access. We may verify ownership first, then explain which account, device and transaction records can be provided.

Yes. Send the incorrect field, the desired correction and your account identifier through support. We may ask for a phone verification step before changing personal details connected with your account.

Cookies may remember a session choice and help us examine unusual access. You can adjust cookie settings in your mobile browser, but doing so may clear a session and require sign-in again.

Access and eligibility depend on local law. Where local law permits, you can ask support about an account access issue from Semarang, Makassar or another Indonesian location.