Reference

bigobet Privacy Policy For Your Account

The bigobet Privacy Policy explains what account, device and wallet details we use, why we use them, and how you can request access or changes.

Account dataWallet recordsCookie choicesPolicy requests
bigobet bigobet Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Policy Help Through Account Support

A clear contact route matters when you want to ask about a record rather than solve a lobby issue.

Account help Send a Privacy Policy question through the account help route when you need to know which contact, verification or sign-in details are attached to your profile. We use the account identifier you provide to locate the relevant record without asking you to share your password.
Wallet records For a DANA, OVO, GoPay or QRIS question, provide the payment reference shown in your account history. We can explain how that reference is used for account matching and status checks, while the wallet provider remains responsible for data it handles directly.
Security concern If a sign-in or phone verification detail looks unfamiliar, contact account support before changing several fields at once. We may ask for account context to confirm the request, but we will not need your password or one-time code to begin a privacy enquiry.
DATA CONTROLS

How bigobet Protects Your Account Data

We handle privacy as part of the account steps you can see: phone verification before account access, wallet status beside the cashier path, and sign-in checks when a device or session changes.

Collected details

We may collect the details needed for an account, including contact information, phone verification status, login events and transaction references. When you browse Auto Roulette Live or Indonesia Football Reels 506, technical session data can help us connect a request to the correct account.

Cookie controls

Cookies and similar browser storage can keep your sign-in path working, remember selected settings and help us identify unusual activity. You can manage browser permissions on your phone or computer, though restricting essential storage may interrupt account access or remove saved preferences.

Account security

Phone verification is used before account access, while sign-in events and device details help us investigate unfamiliar activity. Keep your password private and avoid sending one-time codes in support messages. We use the information you provide to review the specific security concern.

Wallet matching

A payment reference helps connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account request with your account history. We use that reference for status checking and account support, without treating it as permission to access the separate wallet account.

Retention choices

We keep account and transaction records for the period needed to provide the requested service, investigate security events or meet applicable duties. When you ask about deletion or correction, we assess the request against those needs and explain any record that must remain.

Policy changes

If this Privacy Policy changes, we will place the updated wording on the policy page and identify the relevant date or subject where practical. Check the page before opening an account or changing wallet details so your request uses the current terms.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening a bigobet account in Indonesia. They explain the practical path for data access, corrections, wallet references, cookies, device records and account security. If your request concerns a specific record, use the account help route with the smallest amount of detail needed to identify it. Eligibility and access depend on local law.

It covers personal and technical details connected with your account, including contact data, phone verification, sign-in events, device information, cookies and transaction references. It also explains why we use those details for account access, security checks, support and wallet status enquiries.

Yes. Send a request through account help and identify your account without sharing a password or one-time code. We will review the request, explain the relevant records and apply any identity check needed to avoid giving account data to the wrong person.

Contact account support with the field you believe is wrong and the corrected detail. For a phone verification or wallet reference, include the account context that lets us locate the record. We will assess the change and explain if another check is required.

It covers the account-side details we receive, such as a DANA or QRIS payment reference, selected route and status information. DANA and QRIS handle their own records under their separate terms, so their privacy requests must also be directed to the relevant provider.

Device and cookie details help keep your sign-in path working, remember selected settings and identify unusual account activity. You can adjust browser permissions on mobile or desktop, but blocking essential storage may affect phone verification, sign-in continuity or saved choices.

We retain account, security and transaction records for as long as needed for the stated service purpose, investigation of account events or applicable legal duties. If you request deletion, we assess the request and explain when a record must remain for one of those reasons.

Use the account help route and describe the concern without sending your password, one-time code or full wallet credentials. Include the account identifier, device context or payment reference only when relevant. We will use those details to direct the request to the right privacy process.