Reference

Privacy Policy for Your Account Path

Our copot togel Privacy Policy explains what we collect when you create an account, sign in on mobile or desktop, browse Live Baccarat Salon, and use wallet choices…

Clear data purposesPhone verification recordsDANA and QRIS contextCookie choices
copot togel Privacy Policy for Your Account Path
CONTACT ROUTES

Three Ways To Raise A Privacy Question

You can ask us to clarify, correct or remove eligible account data through the support entry connected to your login and cashier path.

Account help path Use the support entry beside account access when you need a copy of your…
Cashier record query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, refer to…
Device access concern If a familiar phone, browser or login event appears unusual, contact us through the…
DATA PRACTICES

Six Practical Privacy Checks We Apply

Privacy controls matter most when they match what you actually do: sign in, verify a phone, switch between a lobby and a wallet, or return from a mobile…

Account details

We use contact and account fields to create your account, support phone verification and respond to requests about your records.

Device signals

A mobile browser or desktop session can produce device, browser, language and login-event signals.

Cookies

Cookies can remember session settings, help the account path load correctly and show whether a page has already been opened.

Payment references

A wallet or bank record may include a method name, reference, amount status and time needed to match the request.

Account security

Phone verification, sign-in events and support checks help us avoid discussing private records with the wrong person.

Retention requests

We keep records only for the period needed for the stated account, security, payment-status or legal purpose.

Privacy Policy Answers For Your Account

These common Privacy Policy questions focus on the records you create through account access, wallet status and mobile browsing. If your situation is not covered, use the support entry connected to your account and include only the details needed to identify the request.

It covers data connected with account creation, phone verification, sign-in events, device and browser signals, cookies, lobby activity, support requests and payment references. The policy also explains retention, security checks and how you can ask about, correct or change eligible records.

Phone verification helps connect an account request to the correct contact and supports account-security checks. We may use its status when you sign in or ask support about private details. Do not send a verification code or password in a support message.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. These records can help us check a status or locate an account query, while access to any service depends on local law.

A session may provide browser type, device signals, language settings, cookie status and login timing. We use this context to maintain the account path, investigate unusual access and answer a device concern. We do not need unrelated personal content from your phone.

Use the support entry attached to your account and identify the field that needs correction, such as a contact detail. We may ask for an account check before changing private data. Do not include your password, full payment credentials or a verification code.

You can ask whether deletion is available for a particular record. We assess the request against its purpose and any legal, security or payment-status duty that may require retention. Send the request through account support with the relevant record type and contact detail.

Start through the support entry beside login or the cashier path, depending on the record involved. Account questions should include your verified contact; wallet questions should include a payment reference. We use those details to route the Privacy Policy request without exposing unrelated records.