Reference

Privacy Policy for Your zippobet Account

Our Privacy Policy explains how zippobet handles the details connected with your account, including phone verification, wallet records and device access.

Account dataWallet recordsCookie choicesSecurity requests
zippobet Privacy Policy for Your zippobet Account
HELP WITH YOUR DATA

Privacy Questions Follow Your Account Path

A privacy question should not leave you searching through unrelated pages. We direct account-data requests through the same contact route used when login or wallet status stalls, while the cashier path helps us locate a payment reference. Include your account contact detail and a short description so we can check the correct record. If you use a mobile browser, keep the relevant transaction screen available when contacting us.

Team online

Account contact

Use the support contact shown in your account area to ask about stored details, phone verification records or a correction. We may ask you to confirm account ownership before discussing personal data, so your request reaches the correct account.

Wallet record check

For a DANA, OVO, GoPay or QRIS question, send the payment reference and the date shown in your cashier history. We use those details to separate a wallet-status query from a wider Privacy Policy request.

Access concern

If a sign-in or device event looks unfamiliar, contact us through the account support route and describe what you noticed. We can review the related access record and explain the security step needed before further account discussion.

YOUR RECORDS

What We Do With Account Data

We treat the Privacy Policy as an operating rule for account handling, not as a page kept apart from the lobby.

Collection

We collect details you submit during account creation, phone verification and support contact, plus technical records such as login time, browser type and device signals. These details help us connect your request with the correct account without asking for unrelated material.

Cookie controls

Cookies can preserve session choices and help us identify unusual sign-in behaviour. You can manage browser cookie settings on your device, although switching them off may require another login or limit parts of the account-data request path.

Account security

Phone verification and access records help us check that a privacy request comes from the account holder. We may pause a request when details do not match, then ask for an account step that confirms control without revealing private records.

Payment references

We record transaction references rather than treating your DANA, OVO, GoPay or QRIS wallet as our own account. A reference can help us trace a cashier question, while the wallet provider remains responsible for its separate data practices.

Retention

We keep account, security and payment-related records for the operational or legal period set out in the Privacy Policy. When a record is no longer needed for those purposes, we remove it or change it so it no longer identifies you.

Your request

You can ask what personal data we hold, request a correction or raise a concern through the account support contact. Please include enough account detail for us to locate the record, and expect an ownership check before disclosure.

Privacy Policy Answers for Indonesia

These questions address the points we hear most often before an account is opened: what zippobet collects, how wallet records are treated, how cookies affect access and how you can ask for a change. The Privacy Policy remains the controlling text if a detail changes, so check the current page before sending sensitive account material or completing phone verification.

The zippobet Privacy Policy covers account details, phone verification, login and device records, support messages, cookies and payment references. It explains why we use each category, how we protect access, how long records may remain and how you can ask about or correct your personal data.

It explains the account-side records linked to DANA, OVO, GoPay and QRIS, such as a payment reference or wallet-status message. Each wallet provider has separate privacy terms for data it processes, so check that provider's own terms for its handling of your wallet details.

Contact us through the support route shown in your account area and ask for a personal-data access request. Include your account contact detail and the records you want checked. We may complete phone or ownership verification before sharing data connected with your account.

Yes. Send a correction request through the account support contact and identify the field that needs changing, such as a contact detail. We compare the request with the account record and may ask for a verification step before applying or explaining the requested change.

On a mobile browser, cookies and device signals can keep a session choice or help identify unusual access. Your browser settings control many cookie choices. Removing them may sign you out or require another phone-verification step when you return to the account.

We keep personal data only while it supports account operation, security checks, payment tracing or a legal need described in the Privacy Policy. After that period, we remove or anonymise the record where practical. The exact period can vary by record type and local law.

Yes. Use the account support contact and describe the unfamiliar login, device or date shown in your access record. Do not send a wallet password or unrelated private material. We can review the event and explain the account-security step needed for the request.