Reference

Open batikslot login Privacy Policy

batikslot login Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet status.

Account dataCookie choicesWallet referencesPolicy requests
batikslot login Open batikslot login Privacy Policy
PRIVACY HELP PATH

Ask us about a policy request

A clear request helps us locate the right account record without exposing details unnecessarily. Use the account help path when you need to ask about a Privacy Policy matter, such as an access request, a correction to your phone detail or the status of a wallet reference. Include the email or phone detail linked to your account, but never include your password or a full payment credential. We may ask for an account step, such as completing phone verification, before discussing private data.

Team online

Access request

Ask us which account details we hold and why they are used. We will use the contact detail attached to your account to locate the request, then may ask you to complete phone verification before sharing private account data.

Correction request

If your phone, email or account detail is wrong, tell us what needs changing through the account help path. We compare the request with existing account records and wallet status references before applying a correction.

Payment reference

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, send the relevant receipt reference rather than a password. This lets us trace the account event while limiting the private data included in your message.

DATA CONTROL POINTS

Protect your privacy across each account step

We apply the Privacy Policy to the practical moments you see: opening an account, signing in, checking a wallet status and returning to the lobby on a phone or desktop browser.

Account security

We use phone verification before account access and keep login and security-event records to identify unusual activity. Do not share your password in a request. If a sign-in issue appears on mobile, use the account path rather than sending private credentials.

Cookie controls

Cookies can help remember a session and support account navigation between the login page and lobby. Your browser can restrict or clear them, although some account steps may then need to be repeated. We explain cookie purposes within the Privacy Policy.

Device behaviour

The policy covers data created when you access the account from a phone, tablet or desktop browser. Device and session details can help us diagnose a sign-in loop or security event, while the same account path remains available when you change devices.

Wallet records

A DANA, OVO, GoPay or QRIS status can create a reference linked to an account action. Bank transfer and virtual account references may also be retained for reconciliation and support. We do not need your wallet password to check a payment status.

Retention choices

We keep personal data only while it supports account security, payment tracing, service records or a legal need. When a record no longer serves one of those purposes, our retention process can remove or de-identify it, subject to applicable requirements.

Policy contact

You can ask what we hold, request a correction or raise a concern about cookie or account handling through the support path. Where local law permits, we respond using the contact detail connected with your account and explain the next verification step.

Find answers about Privacy Policy

These Privacy Policy answers address the account and access questions we expect from Indonesian customers before they open an account. They explain what happens around phone verification, cookies, device records and local wallet references without turning the policy into a general platform description. If your situation is not covered, use the support path with the smallest useful amount of account detail.

The batikslot login Privacy Policy covers account details, phone verification, login and security records, cookies, device sessions, support requests and payment references. It also explains retention, correction requests and how we handle questions about DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use phone verification to confirm that the person requesting account access matches the account contact detail. It can also help us protect private data during an access or correction request. We will not ask you to place your password in a support message.

Yes. The Privacy Policy covers account-linked references created when you check or use DANA, OVO, GoPay or QRIS status. These references help us match an account action with a receipt or pending status. They are not the same as your wallet password or full payment credential.

Use the account help path and identify the email or phone detail attached to your account. Ask for an access copy of the data held about you. We may require phone verification before responding, and where local law permits, we will explain the response process and any applicable restriction.

You can request a correction to an account detail such as your phone number or email. Send the requested change through the support path, without sharing a password. We compare the request with account records and may verify your phone before changing the stored detail.

We retain account, security and payment-reference data only while it supports account protection, payment tracing, support handling or a legal need. The period can differ by record type. When retention is no longer needed, we remove or de-identify the record subject to applicable requirements.

Yes. The Privacy Policy applies when you access the account from a phone, tablet or desktop browser in Bandung, Medan or another supported Indonesia location. Eligibility and access depends on local law. Device session data may be used to protect the account and diagnose sign-in issues.