Reference

situslotindo Privacy Policy for Your Account

Our Privacy Policy explains what account, device and wallet details we collect when you open an account, browse Live Baccarat or use DANA and QRIS.

Account dataWallet recordsCookie choicesSecure access
situslotindo situslotindo Privacy Policy for Your Account
REQUEST A DATA CHECK

Get Help With Privacy Requests

A clear support path helps when your account details need correction, a cookie choice is unclear or a wallet record does not match your receipt. Sign in, open the account help route near the cashier area and include the phone number linked to your account plus the relevant date. We use those details to locate the right record without asking you to send a password.

Team online

Account help route

Open support from your signed-in account and state whether you need access, correction or removal. We can match the request to your verified phone record without requesting your password.

Wallet record check

For DANA, OVO, GoPay, QRIS or bank transfer questions, attach the payment reference and date. We use that evidence to check status while limiting the wallet details shared in replies.

Cookie choice help

If a cookie setting does not behave as expected on your phone, tell us the browser and device path you used. We can explain which preference controls the stored session record.

CONTROL YOUR RECORDS

Privacy Choices That Stay Practical

We keep this policy practical by linking each data choice to an account action you can recognise. Your account area is the starting point for requests, while browser controls manage optional cookies.

Data we collect

We may collect your account name, phone verification result, login events, device details, cookie choices and transaction references. The purpose is to provide account access, protect sessions and respond to a specific request.

Cookie handling

Cookies can retain sign-in preferences, security signals and consent selections on your browser. You can adjust browser settings, though removing required cookies may interrupt the account path used to reach the lobby.

Account security

We use phone verification before account access and examine unusual device or login signals. Never send a password in support messages; we use account identifiers and request details to locate your record.

Retention choices

We retain records only while they support account security, payment reconciliation, dispute handling or a legal duty. A removal request may not erase records that must remain for one of those purposes.

Correction requests

If your phone number or account detail is incorrect, use the signed-in help route and identify the field needing change. We may ask for a verification step before updating information tied to access.

Who to contact

Send privacy questions through the account support path, including the request type and relevant date. For a wallet issue, add the receipt reference; for a cookie issue, add your browser and device.

Privacy Policy Answers For Your Account

These answers address the privacy searches we hear most often before account creation. They explain how the Privacy Policy relates to phone verification, wallet references, cookies, device access and requests made through the signed-in support route.

It covers account details, phone verification, login and device signals, cookie choices, wallet transaction references and support records. It also explains retention, security use and how you can request access or correction.

We use your phone number for the verification step before account access and to connect a privacy request with the correct account. We do not need your password in a support message.

The Privacy Policy allows transaction references, dates and status details for DANA, QRIS, OVO, GoPay, bank transfer or virtual account checks. Do not send wallet passwords or secret codes through support.

Sign in, open the account help route near the cashier area and request access to your records. Include the account phone number and relevant date so we can identify the correct data set.

Yes. Use the signed-in support path, name the field that is wrong and complete any verification we request. We can correct account details when the request matches the verified account record.

Required cookies can support sign-in, security checks and consent storage, while optional cookies remember selected preferences. Clearing them may require you to repeat the account step on that device.

You can ask through the account support route. We assess the request against security, payment reconciliation, dispute handling and legal retention needs, then explain which records can be removed or kept.