Reference

batik77 Privacy Policy For Your Account

Your account details, device activity and wallet records receive a clear explanation in the batik77 Privacy Policy.

Account recordsWallet referencesDevice controlsPolicy requests
batik77 batik77 Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Near Your Account

A privacy question should not leave you searching through the lobby. We keep the contact path close to account access so you can ask about a phone record, wallet reference, cookie choice…

Account request Ask us to explain the personal data connected with your account, including phone verification or sign-in records. Include your registered contact detail so we can locate the correct account safely.
Wallet question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, provide the transaction reference and date. We use those details to narrow the request without asking for your wallet password.
Access concern If a device signal, cookie choice or login record looks unfamiliar, contact account support through the available channel. We may ask for a verification step before discussing private account details.
DATA PRACTICES

Understand How We Handle Your Data

The policy explains why each data category is used and how it connects with an account action.

Account creation

When you open an account, we use the details you submit to create access and send account-related messages. Phone verification helps confirm that the requested access belongs to the person completing the account step.

Wallet matching

A DANA, OVO, GoPay or QRIS reference helps us reconcile an account action. Bank transfer and virtual account records serve the same purpose, while sensitive wallet credentials remain with the payment rail.

Security signals

Login time, browser type, device path and failed access attempts can support account protection. If you switch from mobile to desktop before opening Crash Games, those signals may help identify an unusual sign-in.

Cookie choices

Cookies can keep a session active, remember selected settings and help us understand basic page use. Your browser controls can remove or restrict cookies, although some account functions may then need another sign-in.

Retention period

We retain records for the period needed to provide account access, resolve a payment question, protect against misuse or meet a legal requirement. The policy explains the purpose before a retention request is assessed.

Change requests

You can ask us to correct outdated contact details, explain a stored record or address a permitted deletion request. Send the request from your registered contact route so we can verify ownership first.

Check Privacy Policy Answers Before Access

These Privacy Policy answers cover the account questions we expect before registration or a wallet action. They explain what to prepare, how identity checks work and where local rules affect access. If your situation involves a particular device, payment reference or account correction, contact us with the smallest useful detail and we can direct the request.

It covers account details, phone verification, device and login signals, cookies, payment references, support requests, retention and permitted data changes. It also explains when access depends on local law.

We use your phone number for account creation and a verification step before access. It helps connect the request to the correct account and supports account recovery or security questions.

Yes. It explains that DANA, OVO, GoPay and QRIS may provide transaction references or status details used to match an account action. Wallet passwords are not needed for that matching.

Device type, browser signals, login time and failed access attempts can help identify unusual account activity. These records support account security and are handled according to the retention purposes stated in the Privacy Policy.

You can request a correction to outdated contact or account details through the available support route. Send the request from your registered contact path, because we verify account ownership before making a change.

You may ask about deletion, but some account, payment or legal records may need to remain for a stated purpose. We assess the request under the Privacy Policy and applicable local requirements.

Use the available account support channel and include your registered email or phone, plus a short description of the record involved. Never send a wallet password, full card credential or account login secret.