Reference

Open bigobet Privacy Policy Before Access

bigobet Privacy Policy explains how we collect, use and protect the details connected to your account, device and wallet activity.

Account dataCookie choicesWallet recordsAccess requests

Browse The Lobby Read FAQ

Browse How Privacy Works With Payments

bigobet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details you provide during account creation, including contact data used for phone verification before account access. We also record operational events such as login time, device type, security checks and payment status so we can match a DANA, OVO, GoPay or

1
QRIS transaction to the correct account. Bank transfer and virtual account references may be retained for reconciliation and receipt checks. We use this material to provide account access, investigate errors and protect the cashier path. Access and eligibility depends on local law, and the policy applies
2
where local law permits. We do not ask you to send payment credentials through an unapproved contact route.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST SUPPORT

Contact bigobet About Privacy Questions

A clear contact path helps you act on your Privacy Policy rights without guessing which team to reach. Tell us whether your request concerns account access, a wallet receipt, cookies, stored device details or a correction to your personal data. Include the account contact details you used, but never send a password, wallet PIN or full payment credential. We may ask for an account step or verification detail before discussing records, because the request must reach the person connected to the account.

Team online

Account access

If your phone verification or login record looks wrong, contact us through the account help route. We will check the relevant access event, confirm what can be changed under the Privacy Policy, and explain any verification step needed before we discuss account data.

Wallet status

For a DANA, OVO, GoPay or QRIS receipt question, use the payment support path beside the cashier area. Share the transaction reference and date rather than private wallet credentials, so we can locate the record while limiting the data included in your request.

Data requests

To ask for a copy, correction or deletion review, identify the account contact and describe the exact record concerned. We will confirm your identity, assess the request under the Privacy Policy and reply with the next step or the reason a record must remain.

DATA PRACTICES

Explore How We Handle Your Records

The way we handle data is tied to practical account events rather than broad collection for its own sake.

Account details

We use the contact details you submit to create and protect your account, send account-related replies and complete phone verification before access. Please keep those details current; an old number can make a correction or access request take longer to confirm.

Payment matching

A payment reference lets us connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event with the right account. We use that match to check receipt status and investigate a mismatch, not to request your private wallet PIN.

Device security

Login time, browser or device type and security events can help us spot account access that does not fit your normal path. If you switch from mobile to desktop, those records help us investigate the change without asking you to share your password.

Cookie controls

Cookies can remember settings and help the account page load consistently across your device path. You can manage browser cookie controls, although removing some cookies may require you to repeat login or preference steps when you return.

Retention period

We retain account, security and payment records only for the period needed for access, reconciliation, dispute handling and applicable legal duties. When a record is no longer needed for those purposes, our handling follows the deletion or anonymisation process available to us.

Change requests

You can ask us to correct inaccurate account data, provide a copy where available or review a deletion request. We first confirm the request belongs to you, then explain the action, timing and any reason a record must be kept.

Get Answers About Privacy Policy

These Privacy Policy answers focus on the account and payment questions you are most likely to have before opening access. They explain what we collect, why phone verification matters, how cookies affect your device path and where to send a request about a DANA, OVO, GoPay or QRIS record. If your situation is unusual, contact us with the smallest useful set of account details. We will use the policy and applicable local requirements to decide what we can provide or change.

The bigobet Privacy Policy covers account details, phone verification, login and device events, cookies, payment references and support requests. It explains how we use those records for account access, security, wallet status checks, dispute handling and legal duties where local law permits.

We collect the details needed for your account path, including contact data used for phone verification. We may also record device type, login events and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity to check account and receipt status.

Phone verification helps us confirm that the person requesting account access or a data change is connected to the account contact. It also supports security checks when a login pattern changes. Keep your number current, and never share a password or wallet PIN.

We use transaction references and status details to match DANA or QRIS activity with your account and investigate a receipt mismatch. We do not need your wallet PIN for that check. Send only the reference, date and account contact requested through the support path.

Yes. Contact us with the account contact details and describe the record you want copied or corrected. We will verify the request, search the relevant account and explain what the Privacy Policy allows us to provide, amend or retain under applicable requirements.

We keep records for the period needed to provide account access, protect the account, reconcile payments, resolve disputes and meet applicable legal duties. Retention can differ by record type. When a record is no longer needed, we follow the deletion or anonymisation process available.

Use the privacy contact route and state whether your question concerns cookies, a mobile device, desktop access or a login event. Browser controls can remove some cookies, but you may need to repeat account steps. We will confirm what device data relates to your request.

Open bigobet Privacy Policy Before Access

Contact bigobet About Privacy Questions

Account access

Wallet status

Data requests

Explore How We Handle Your Records

Account details

Payment matching

Device security

Cookie controls

Retention period

Change requests

Get Answers About Privacy Policy

01 What does the bigobet Privacy Policy cover?

02 What personal data does bigobet collect for an account?

03 Why does bigobet need phone verification?

04 How does the Privacy Policy handle DANA and QRIS records?

05 Can I request a copy or correction of my data?

06 How long does bigobet keep account and payment data?

07 Where can I ask about cookies or device data?

Related Pages