Reference

instaslot Privacy Policy for Your Account

Our Privacy Policy explains how instaslot collects, uses and protects details connected with your account, device and wallet activity.

Clear data purposesWallet activity contextAccount request pathMobile and desktop scope
Browse Our Lobby Read FAQ
instaslot instaslot Privacy Policy for Your Account
REQUEST HELP

Reach Us About Privacy Policy

A clear contact path matters when you want to ask about your Privacy Policy rights or correct an account detail. Start from the support route shown in your account area and include the email or phone detail linked to your profile, without sending a wallet password. We can then locate the relevant record, explain the next step and keep your request tied to the correct account.

Team online

Data access request

Ask us what account, phone verification, device and wallet-reference data we hold by using the support path inside your signed-in account. We may ask for account details to confirm the request belongs to you.

Correction request

If your phone detail or account entry is outdated, tell us which field needs correction and why. We compare the request with your account record before changing personal data connected with DANA, OVO, GoPay or QRIS activity.

Privacy clarification

For a question about cookies, retention or a bank transfer reference, use the same account support route and describe the exact screen or transaction step. Keep passwords and wallet security codes out of your message.

DATA PRACTICE

How We Handle Your Policy Requests

We apply the Privacy Policy to the account journey rather than treating every record as the same. Login protection, wallet references, cookies and support requests each have a defined purpose.

Account details

We use the details you provide during account opening and phone verification to create your profile, protect sign-in and connect an approved request with the right account. Please keep those details accurate when you contact us.

Device signals

A mobile browser or desktop session can create technical records such as device type, browser details and sign-in time. We use these signals to recognise unusual access and investigate account-security questions.

Cookies

Cookies and similar browser storage can remember session choices and help the account path load correctly. Your browser controls may restrict them, although some sign-in or policy-request functions may then behave differently.

Wallet records

A DANA, OVO, GoPay or QRIS reference can be retained to reconcile an account action, while bank transfer and virtual account details help us trace the matching request without needing your wallet password.

Retention period

We keep personal data only for the period needed for the stated purpose, account security, dispute handling or a legal record. When that need ends, deletion or de-identification follows our internal handling process.

Request verification

When you request access, correction or deletion, we may check your account email or phone detail before responding. This protects your records from a request made by someone else.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the searches you may make before opening an account or asking for a change. They cover the records created by phone verification, mobile sign-in, cookies and local wallet activity. If your question is not listed, use the support route in your account area and describe the specific data or account step involved.

It covers account details, phone verification, sign-in and device records, cookies, support requests, and references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to create and protect your account, connect requests with the correct account and investigate unusual sign-ins. We do not ask you to send a wallet password through support.

Yes. Use the account support route and ask for a data access request. Include the account phone or email detail so we can check ownership before explaining which records can be provided.

Send a correction request through account support, identify the inaccurate field and provide the updated detail. We compare the request with your profile before changing information connected with your account.

Yes. It covers technical records from a mobile browser and desktop session, including device type, browser details and sign-in time, where those records support security, session function or a request.

We may retain transaction references to match an account action and resolve a status question. These references help reconciliation without requiring your wallet password, and the same approach applies to bank transfer records.

Use the support route shown inside your account and describe the data or policy point you need clarified. Account access depends on local law, and we will explain any applicable request condition.

Related Pages

instaslot Indonesia About Us Access guide VIP Baccarat FAQ