Reference

Privacy Policy for Your Account Path

kode syair hk Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move through the lobby from your…

Account clarityWallet recordsCookie choicesPhone verification
kode syair hk Privacy Policy for Your Account Path
CONTACT ROUTES

Where To Ask About Personal Data

A clear contact route helps when a privacy question sits beside a login or wallet record. Start from the support contact path linked in your account area and include the phone number on the account, the relevant date, and a short description of the request. For a DANA, OVO, GoPay or QRIS query, include the payment reference rather than sending a wallet password. We use those details to locate the correct record without asking you to disclose more than needed.

Team online

Account contact path

Use the support route connected to your account when you need a copy, correction or explanation of personal data. Adding your account phone number helps us match the request before we discuss records linked with your login.

Wallet record query

For a DANA, OVO, GoPay or QRIS privacy question, send the transaction reference and date through the support route. We can then separate our account record from the wallet provider's own record and reply with the relevant scope.

Access concern

If a phone verification step or account login exposes an unfamiliar device, contact us through the account help path. We may ask for account details to confirm ownership before changing access or discussing stored activity.

HANDLING DETAILS

Six Ways We Handle Your Data

Privacy work is part of the account path, not a separate promise hidden after payment. We separate identity details from practical records where the process allows, limit access to staff who need…

Account records

We collect details needed to open and maintain your account, including phone verification status and login events. If you browse Live Baccarat Gold or Esports Mobile Legends, related activity may be recorded to keep account history and access checks accurate.

Cookie controls

Cookies can remember a session, language setting and the page path that brought you back to the lobby. You can manage browser cookie controls on your device; blocking some cookies may require another login or limit saved preferences.

Login security

We use phone verification and device signals to help identify unusual account access. Never send a password or wallet PIN through support. If a new browser appears on your account, contact us before changing payment details.

Wallet matching

DANA, OVO, GoPay and QRIS references help us match a payment event with the correct account action. We do not need your wallet PIN for that check, and the wallet provider remains responsible for records held on its own service.

Retention period

We retain account, security and transaction records only for the period needed to operate the service, resolve disputes, meet legal duties or protect against misuse. When a record is no longer needed, we remove it or reduce its link to your account.

Change requests

You may ask us to access, correct, restrict or delete personal data where the request is available under local rules. Send the request through the account contact route, identify the record clearly, and we will confirm the next step.

Privacy Policy Answers for Your Login

These Privacy Policy answers focus on the questions that arise before you open an account or connect an Indonesian wallet. We explain the records involved, the device path, the contact process and the limits that apply when another provider, bank or local rule controls part of the request.

It covers account details, phone verification, login and device events, cookie settings, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains requests for access, correction, restriction and deletion where available.

We use your phone number to create the account path, complete phone verification and help confirm account ownership during a privacy request. It can also help us identify an unfamiliar login. We do not need your wallet PIN to match a payment reference.

It covers the account-side reference we receive when you use DANA or QRIS, such as a transaction identifier, amount status and time. DANA and QRIS providers keep their own records under their terms, so a provider-held request may need to go to them.

Yes. Send a correction request through the support route in your account area and identify the field or record that appears wrong. We may confirm your phone number or another account detail before making a change, so another person cannot alter your data.

Cookies can keep a browser session, remember a setting and help us understand whether a login continues on the same device. If you clear or block them on Android, iPhone or desktop, you may need phone verification again or lose saved preferences.

We keep each category only as long as needed for account operation, security checks, dispute handling or legal duties. The period can differ for login records, support messages and payment references. You can ask us which category applies to a specific request.

You can ask for deletion through the account contact route, and we will assess the request under applicable local rules. Some records may need to remain for security, dispute handling or legal duties. Where local law permits, we will remove or de-link data that no longer needs retention.