Reference

How batik168 Handles Your Personal Information

This page explains exactly what data batik168 collects when you open an account, make a deposit via DANA, OVO, or GoPay, or contact our support team — and what we do with it.

Account data handled securelyDANA, OVO, GoPay payment data protectedNo data sold to third partiesYour rights, clearly statedContact us to request changes
batik168 How batik168 Handles Your Personal Information
HOW WE PROTECT IT

Data Handling, Cookies and Account Security

We apply SSL encryption across all pages on batik168, which means data travelling between your device and our servers — including login credentials and payment confirmations — is protected in transit. Players in Yogyakarta and Batam access the same encrypted connection as every other account holder. Here is how the four key areas of data handling actually work on our platform.

Cookies and Tracking

We use session cookies to keep you logged in and analytics cookies to understand how the lobby is used. You can adjust cookie preferences in your browser settings at any time.

Data Retention

Account data is kept for as long as your account is active and for a period after closure as required by applicable regulations. Transaction records tied to DANA, OVO, or GoPay are retained for financial audit purposes.

Account Security

Each login triggers an OTP sent to your registered phone number. If we detect a login from an unrecognised device or IP, we flag it before granting full account access.

Your Rights Over Your Data

You can request a copy of your data, ask us to correct inaccurate details, or request account closure through our support team. We process those requests in line with applicable local law.

PRIVACY CONTACT PATHS

How to Reach Us About Your Data

If you want to access the personal data we hold on your account, request a correction, or ask us to delete specific records, reach out through any of the channels below. We aim to respond to data-related requests within a reasonable timeframe. For account-linked queries — such as confirming which wallet records are attached to your profile — our live chat team can pull that up while you wait.

Live Chat Open the chat widget from any page on batik168. Available during active support hours. Suitable for account data questions and wallet record queries.
Email Support Send your data request to our support address listed in your account dashboard. Include your registered phone number so we can verify your identity.
Account Dashboard Log in, head to your profile settings, and use the data request form directly. This is the quickest path for straightforward corrections to your registered details.

Questions About Your Privacy on batik168

These are the questions we get most often about how personal data is managed. If your question is not covered here, reach out via live chat or the email address in your account dashboard.

We collect your name, email, phone number, and date of birth at registration. Payment activity through DANA, OVO, or GoPay generates transaction references we also keep on file.

We share data only with payment processors — such as those handling DANA, OVO, GoPay transfers — and only to complete your transaction. We do not sell data to advertisers.

Log in and use the data request form in your account dashboard, or send a request via the support email listed there. Include your registered phone number to confirm your identity.

Yes. Submit a deletion request through live chat or email support. Some records — particularly financial transaction data — may be retained as required by applicable regulations.

Every login uses an OTP sent to your registered phone. Unrecognised device logins are flagged before access is granted. All data in transit is protected with SSL encryption.

Account data is held for a period after closure in line with applicable local regulations. Transaction records linked to your DANA, OVO, or GoPay wallet are kept for financial audit purposes.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.