Reference

situs thailand Privacy Policy For Your Account

Our Privacy Policy explains how we handle the account, device and wallet details you provide when you access Live Blackjack Prestige, Wild Bandito Slots or La Liga Over…

Account clarityWallet data controlsDevice privacyPolicy access
situs thailand situs thailand Privacy Policy For Your Account
CONTACT ROUTES

Get Help With A Privacy Request

A clear contact path helps when you want to ask about a record connected with your account. Use the support route shown inside your account area and include the phone number or transaction reference that helps us locate the request, without sending a wallet password. We can explain a collection purpose, check an access request or correct an eligible detail. If your concern started with a QRIS receipt, a DANA status or a login event, mention that context so our team can direct the request to the right record.

Team online

Account message

Send a privacy question from the signed-in account route so we can connect your request with the correct phone verification record. We may ask you to confirm account details before discussing personal data, which helps prevent disclosure to the wrong person.

Cashier context

For a DANA, OVO, GoPay or QRIS query, include the payment reference and approximate date shown in your account history. We use that detail to separate a wallet-status question from a broader request to access, correct or remove personal data.

Access request

Ask us to explain the data linked with your account or to amend an inaccurate detail through the available support path. We may verify your phone before responding, and some action can depend on local law or a record we must retain.

HANDLING DETAILS

What Happens To Your Account Data

We treat this policy as an operating process rather than a small-print page. Login records help us spot unusual access, cookie data helps us remember necessary session settings…

Collected details

We may handle your phone number, verification result, login timestamps, device type, browser signals, account actions, support messages and payment…

Cookie choices

Cookies and similar storage can keep a signed-in session working, remember essential settings and help us understand an interrupted account…

Account security

Phone verification is an account step before access, and login events may be checked for unusual device or location patterns.

Retention periods

We retain each category only as long as its purpose, an unresolved request or a legal requirement calls for.

Data corrections

If your phone detail or another account record is inaccurate, contact us through the account support route with the specific…

Policy questions

You can ask why a detail was collected, how it relates to your account or which retention reason applies.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account actions you are most likely to question before opening an account or while checking a wallet record. We explain the role of phone verification, cookies, device data, payment references, correction requests and access rules in plain language. Where a request involves legal eligibility or a retention duty, the outcome depends on local law. If your situation is not covered below, use the support route attached to your account.

It covers personal data connected with your account, including phone verification, login events, device details, support messages and payment references. It also explains cookies, retention, security checks and requests to access or correct records linked with DANA, OVO, GoPay, QRIS or bank transfer activity.

We use your phone number for the account path and phone verification before access. It helps connect your login with the correct account and supports security checks when a device or access event appears unusual. We do not ask you to place a wallet password in a support message.

Yes. When you use DANA or QRIS, we may handle a transaction reference, status or timing needed to match the account action. The same approach can apply to OVO, GoPay, bank transfer and virtual account records. Wallet credentials are not needed for that matching process.

Use the support path available from your signed-in account and clearly ask for an account-data access request. Include the phone detail connected with the account, but do not send wallet credentials. We may verify your identity first, and the response depends on local law and required retention.

You can request a correction for an inaccurate phone detail or another eligible account record through support. Tell us which field is wrong and what should replace it. We may ask for phone verification, while payment or security records may need to remain unchanged when retention is required.

Necessary cookies or device storage can keep your account session active and preserve essential settings while you move from login to the lobby. Browser controls may let you remove or block some storage. Blocking necessary cookies can interrupt access, so check the account path if login stops working.

Account access and eligibility depend on local law. We handle data for the account path available to you, including access from a phone or desktop in Jakarta, but location signals may be checked for security. A support request can explain a regional access issue without exposing unrelated payment data.