Reference

bigobet Privacy Policy for Your Account

Our bigobet Privacy Policy explains what we collect when you open an account, sign in on mobile, use DANA or QRIS, and move between Blackjack, Rocket Crash or…

Account dataWallet recordsCookie choicesAccess requests
bigobet bigobet Privacy Policy for Your Account
CONTACT ROUTES

Get Policy Help Beside Account Access

A clear contact path helps when you need to understand a data entry, cookie choice or wallet reference. Sign in first when possible, then use the account support route so we can match your request to the correct record. If sign-in stalls, include the account detail you can safely share and the relevant DANA, OVO, GoPay or QRIS reference.

Team online

Account access

Use the support route shown with your account access area to ask what data we hold, why verification is pending, or how to correct a profile detail.

Wallet status

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference and date without sharing a password or private wallet code.

Policy request

Ask for a copy, correction or deletion assessment through the account contact path. We may request account verification before changing records connected with your identity.

CONTROL POINTS

Six Practical Controls Inside bigobet

Privacy choices work best when they are tied to a real account step. We separate sign-in protection from payment references, explain cookies before they are used where the site supports that choice…

Data collection

We use account details, verification results, device signals and support messages for stated account, security and service purposes rather than collecting unrelated profile material.

Cookie choices

Cookie settings help you understand which browser data supports sign-in, security or site measurement. Your selected preferences are treated as part of the policy record.

Account security

Sign-in checks, device activity and verification steps help us identify unusual access. Never send a password, wallet PIN or one-time code through a support request.

Retention period

We keep account, payment-reference and support records only as long as needed for their stated purpose, account protection, dispute handling or applicable legal duties.

Policy contact

Your account support route is the starting point for privacy questions. Include the email or phone detail attached to the account so we can locate the correct record.

Changing details

You can request a correction when your account detail is inaccurate. We check identity before applying changes that could affect access, wallet status or activity records.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before account access. They cover data collection, payment references, cookies, device activity, retention and request handling for Indonesian accounts, including access from Bandung and Medan where local law permits.

It covers account details, verification, device and sign-in activity, cookies, support messages, game-area activity and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account use.

We use the details you submit to create and protect your account, complete required verification, connect support requests to the right record and maintain accurate access history where local law permits.

Yes. It covers status, reference numbers, dates and related wallet or bank identifiers needed to match a DANA or QRIS transaction. We do not ask for your wallet password.

Sign in and use the account support route for a data access request. Tell us the account email or phone detail, and complete any identity check needed before we release connected records.

Yes. Send a correction request through the account contact path and identify the inaccurate field. We may verify you first, especially when the change affects wallet status or account access.

The policy explains cookies used for sign-in, security and site measurement where available. Check the cookie setting on your browser path, then adjust the choices offered there.

Retention depends on the purpose of the record, account protection, dispute handling and applicable legal duties. When those needs end, we assess the record for deletion or further restriction.