Reference

Read the shio 6 togel Privacy Policy

The shio 6 togel Privacy Policy explains which account, wallet and device details we collect, why we use them, and how you can ask for changes.

Account clarityWallet detailsDevice choicesPolicy requests
shio 6 togel Read the shio 6 togel Privacy Policy
REQUEST HELP SAFELY

Contact us about your privacy request

A clear support path helps you ask about personal data without sending sensitive wallet credentials. From your account, use the support route near account help and describe whether your request concerns login records, phone verification, cookies, device access or a payment reference. We may ask for details that identify your account before discussing it. This keeps a request connected to the right record while access remains where local law permits.

Team online

Account data request

Use the account help route to ask what personal details are connected with your account. We may confirm your phone verification step before discussing login history, contact details or records linked to your DANA, OVO, GoPay or QRIS activity.

Wallet reference check

If a payment reference looks unfamiliar, tell us whether it relates to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Share the reference and date, but never send a wallet password or full security code.

Access and cookie help

When a device remembers the wrong session or cookies affect account access, contact us through the same support path. We can point you to the relevant privacy setting and explain which login step may need to be repeated.

HOW DATA IS HANDLED

Check our account privacy practices

We keep the Privacy Policy practical by linking each data use to a visible account action.

Account records

When you create or access an account, we may store your contact details, phone verification result and login events. These records help us connect a privacy request to you and identify unusual access before account details are discussed.

Payment references

A DANA, OVO, GoPay or QRIS reference can show whether a cashier action reached the expected account. Bank transfer and virtual account records may also be retained for matching, reconciliation and account queries without storing your wallet password.

Device signals

Your browser, device type, session time and limited security signals may be recorded when you move from login to the lobby. This can help us identify a mismatched session on mobile or desktop before access continues.

Cookies and settings

Cookies can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can manage cookie controls in your browser, although changing them may require another login or affect saved preferences.

Retention requests

We keep personal records for the period needed for account operation, security checks, payment matching, disputes or legal duties. You may ask whether a record can be corrected or removed, subject to account checks and applicable law.

Who receives requests

Privacy questions are handled through our account support path rather than through a wallet provider. Include your account contact and the request type, then let us verify ownership before we explain, correct or restrict an eligible record.

Find answers about Privacy Policy

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover what we collect during login, how payment references are used, what happens on mobile devices and how to request a correction. If your situation is not listed, use the account support path and include only the details needed to identify your request.

The Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can ask about correction or removal where local law permits.

No. We use payment references and status details to match account activity involving DANA, OVO, GoPay or QRIS. Your wallet password and security code should remain with the wallet provider. If a reference looks wrong, contact us through account help.

Device type, browser details, session time and limited security signals can help us maintain the correct login session. This matters when you move from a mobile login to the lobby or return to Live Blackjack Table on another device.

Use the account support path and state whether you want a correction, access request or another privacy action. Include your account contact, not a wallet password. We verify ownership first, then assess the request under the Privacy Policy and local law.

We retain records for the period needed for account access, phone verification, security checks, payment matching, disputes or legal duties. The exact period can depend on the record and applicable law. Ask support which retention category relates to your request.

You can manage cookies through your browser settings. Some changes may sign you out, remove saved preferences or require another account check. The Privacy Policy explains cookie purposes, while support can help if a setting affects your login route.

Yes. Access, eligibility and some requests depend on local law. We apply the Privacy Policy to supported Indonesian routes, but a request may require identity checks or may be limited when retention, security or legal duties still apply.