Reference

batik9 Privacy Policy For Your Account

batik9 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesSecurity checks
Explore Our Lobby Read FAQ
batik9 batik9 Privacy Policy For Your Account
CONTACT OUR TEAM

Reach Support About Privacy Policy

A clear contact route helps you act on the Privacy Policy instead of guessing which team handles your request.

Account desk Use the account support channel for a copy request, correction request or question about…
Wallet status If your privacy question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account…
Security route For suspected account access by someone else, contact support through the account path promptly…
HOW WE HANDLE DATA

Browse batik9 Privacy Controls With Clarity

Privacy Policy choices should connect to actions you can take inside your account. We separate account identity, device activity, payment references and support messages so each request can…

Account records

We use your registered contact, phone verification result and account activity to provide sign-in and protect the account.

Device signals

A phone, tablet or desktop may send browser type, operating details, session time and security signals.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain references needed to match a cashier event…

Cookies

Cookies can keep a session open, remember a selected setting and show whether a page responds on your device.

Retention timing

We retain data for the period needed for account security, payment reconciliation, support handling or a legal requirement.

Change requests

Ask us to correct account details, explain a data use or consider deletion where local law permits.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the account, device and payment questions you may have before opening access. We keep the examples tied to the actual account path: phone verification, wallet references, cookies, support contact and local eligibility. If your situation is not covered, send a focused request through our support route and avoid including passwords or one-time codes.

The Privacy Policy covers data collected when you open an account, sign in, use phone verification, browse the lobby or contact support. It also addresses device signals, cookies, payment references from DANA, OVO, GoPay and QRIS, retention, security and requests to access or correct your records.

Phone verification helps us confirm that an account request or privacy request comes from you. We may use it before discussing account records, changing contact details or responding to a suspected access issue. Keep verification codes private and send support only the contact details needed to locate your account.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a cashier event, investigate a status question and maintain required records. We do not ask you to provide a wallet password.

Contact our account support route and state that you want an access request under the Privacy Policy. Include your registered contact and a short description of the records you need. We may confirm phone ownership first, then explain the available records and any limits that depend on local law.

You can ask us to correct inaccurate account details or consider deletion where local law permits. Send the request through support with your registered contact and the specific field or record. Some security, payment or legal records may need to remain for a defined operational reason.

Cookies can support a login session, remember settings and help us understand whether a page works on your device. Your browser provides controls for blocking or removing them. Necessary cookie changes may interrupt phone verification or account access, so check the effect before changing browser settings.

Use the account support channel for a Privacy Policy question, data request or suspected account access. Mention the registered contact, request type and relevant date, but never send a password or one-time code. If the matter involves a wallet status, add the transaction reference rather than private wallet credentials.

Related Pages

batik9 Indonesia World Cup Mix Parlay FAQ Live Roulette Turbo Account information