Reference

indoslot Privacy Policy for Your Account

Our Privacy Policy explains how indoslot handles the details connected with your account, mobile browser, wallet status and lobby activity.

Account dataWallet recordsCookie choicesPrivacy requests
indoslot indoslot Privacy Policy for Your Account
ACCOUNT HELP PATH

Contact Routes for Privacy Policy Questions

A clear support route helps you ask about privacy without explaining the same issue repeatedly. Start from your signed-in account and include the phone number linked to it, the affected device and the relevant payment reference if your question concerns DANA or QRIS. We use those details to locate the correct record, while you should leave out any wallet password or private login code.

Team online

Account request

Send a privacy question from the account connected to your phone verification. We can then compare the request with the correct account record before discussing access, correction or removal.

Payment reference

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the receipt reference and date. That lets us trace status data without asking for your wallet password.

Mobile access

If a privacy page or cookie choice behaves differently on your phone, tell us the browser and device path used. We can separate a display issue from an account-data request.

DATA HANDLING PRACTICE

How We Handle Cookies and Account Records

Privacy work is part of the account path, not a separate promise hidden from the cashier area.

Account security

Phone verification helps connect an account request to the correct person. Sign-in events and device markers may be checked when access looks unusual, helping us protect your account record.

Cookie controls

Cookies can remember a session, language choice or privacy setting on your browser. You can clear them through browser controls, although doing so may require another account sign-in.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a cashier event with the right account. We use the reference and status, not your wallet password.

Device records

We may store browser, operating-system and IP details linked to a session. These records help diagnose account access and distinguish a mobile sign-in from an unfamiliar attempt.

Retention choices

We retain account, payment and support records for operational or legal needs, then remove or anonymise them when that purpose ends where local law permits.

Change requests

Ask us to correct account data, explain its use or discuss removal through your signed-in account route. Include the specific field or record so we can act precisely.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet status. We keep the route practical: identify your account, name the record involved and use the available support path. Access and eligibility depend on local law, so the policy should be read together with the rules that apply to your location.

It covers account details, phone verification, session and device records, cookies, lobby activity, payment references and privacy requests connected with your use of indoslot where local law permits.

No. We may keep a DANA or QRIS transaction reference, amount, receipt and status for reconciliation, but you should never send us a wallet password, PIN or private login code.

Phone verification helps us connect an access request with the correct account and reduce mistaken disclosures. It may also support checks when a sign-in comes from an unfamiliar device.

Yes. Send the request from your signed-in account and identify the field that needs correction, such as your phone number or profile detail. We may ask for account matching.

Cookies may remember your session and privacy choice on a mobile browser or desktop browser. Clearing them can remove that choice and may require you to sign in again.

We keep payment references, receipts and status records while they support reconciliation, account support or a legal requirement. When the purpose ends, removal or anonymisation follows where local law permits.

Use the signed-in account route and describe the data question clearly. For a wallet matter, add the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference without sharing private credentials.