Reference

Open zebra007 Privacy Policy Before Access

Our zebra007 Privacy Policy shows how we handle your account data while you browse Live Baccarat, Fishing God and other lobby titles.

Clear data purposesWallet-linked privacyMobile access contextPhone verificationIndonesia account terms
zebra007 Open zebra007 Privacy Policy Before Access
CONTACT PATHS

Switch To The Right Privacy Contact

A clear contact path helps you ask about Privacy Policy matters without mixing them with a game or wallet question.

Account data request Use the signed-in account route when you want to ask what account data we…
Wallet record question If your Privacy Policy question concerns DANA, OVO, GoPay, QRIS, bank transfer or a…
Access correction path When a name, phone detail or account record needs correction, tell us which field…
DATA HANDLING

Browse zebra007 Privacy Controls Clearly

Privacy Policy choices are easier to understand when each data touchpoint has a defined reason.

Account data use

We use details such as your account contact, phone verification result and sign-in records to provide access and protect the…

Cookie choices

Cookies and similar device signals can help keep a signed-in session working, remember a selected path and identify repeated access…

Sign-in protection

Phone verification before account access helps us distinguish an account holder from an unverified request.

Wallet matching

A DANA, OVO, GoPay or QRIS reference can be used to match a payment status to the correct account record.

Record retention

We retain account, security and transaction-related records only for the period needed for the stated service, account protection, dispute handling…

Change requests

You can ask us to correct account data, explain its use or address a permitted deletion request through the account…

Check Your zebra007 Privacy Policy Answers

These Privacy Policy answers address the account questions you are most likely to have before opening access or linking a local wallet. They cover data collection, mobile sessions, payment references, cookies, correction requests and account verification. If your situation is not listed, use the relevant contact path above and describe the record or action you want us to assess.

The zebra007 Privacy Policy covers data connected with account creation, phone verification, sign-in activity, device sessions, support requests and payment references. It explains why we use those records, how cookies support access, how retention works and how you can ask about correction or another permitted request.

We may collect the account contact details you submit, phone verification status, sign-in and device signals, support messages and records needed to match wallet activity. The Privacy Policy explains the purpose for each category. We do not ask you to place a password or one-time code inside a privacy request.

Yes. The Privacy Policy covers payment references and status signals connected with DANA, OVO, GoPay and QRIS when those records are linked to your account. Bank transfer and virtual account references may also be used for matching. We use the reference to reconcile activity, not to request secret wallet credentials.

When you sign in on a phone, we may process device and session signals that help keep access working and identify unusual activity. The Privacy Policy explains this use. Browser cookie settings can affect continuity, and the same account check applies if you ask us to discuss or change a mobile-related record.

You can send a correction request or ask about deletion where that request is permitted under the applicable Privacy Policy and local law. Identify the account contact and the record involved. We may verify account control first, then assess the request against service, security, dispute and legal retention needs.

Use the signed-in account contact route and state whether your request concerns account data, cookies, device access, phone verification or a wallet reference. Add the relevant payment reference if needed, but never include your password or one-time code. We use your account detail to direct the request correctly.

Yes. Account access and the handling of a particular request depend on local law and may differ where local law permits. Our Privacy Policy is written for the account and data paths described here, including Indonesia wallet references, but applicable rules can affect eligibility, retention and how a request is handled.