Reference

Legal terms for your account

We keep the legal side of your account in one place: what we collect, how we verify changes, and how we answer access questions where local law permits.

DANAOVOGoPayQRIS

Explore Lobby Read FAQ

Access rules, data, and records

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

We write our legal terms so you can see the path before you send anything to support. We may collect the details you enter during account creation, the device and browser signals used for security, and the chat records that help us resolve account changes or

1
disputes. Transaction labels from DANA, OVO, GoPay, and QRIS stay in the record because they help us match a request to the right history and check for mistakes. When access depends on region or method, the answer depends on local law or where local law permits.
2
If you ask for a correction, a copy of stored data, or a check of an account decision, we first confirm the request from the email or phone on file and then route it to the right team. This process is the same from Makassar, Denpasar,
3
or anywhere else we support.

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

REQUEST ROUTES

Where to send legal requests

Fast contact paths matter when a policy question slows your account. We keep live chat open 24/7, and email works when you want a written trail for a correction or data request. If you are in Makassar, chat is usually the quickest route; the form is better when you need us to trace a stored record. Every channel starts with identity checks before we change anything.

Team online

Live Chat

Open live chat when you need a quick answer about access, corrections, or stored records. We keep it open 24/7, and the chat log stays attached to your case so nothing gets lost.

Email

Email works well when you want a written trail. Send the request from the address on file, add the account phone if needed, and we will reply after we verify who is asking.

Request Form

Use the request form when you want a case number for a correction, data copy, or closure check. It is easy on mobile and desktop, and the form keeps your request in one thread.

COOKIE CONTROL

How we handle cookies and data

We treat legal requests as account work, not copy-paste replies. That means we check the sign-in method, device history, and message thread before changing records, and we keep…

Cookies

We use session cookies to keep sign-in state, language choice, and security checks working.

Data Handling

We keep the account details you enter, the chat trail, and device signals only as long as we need them…

Security Checks

When a device looks unfamiliar, we may ask for a fresh sign-in or a code sent to your email or…

Retention

Stored files are checked on a schedule, and we remove items that no longer need to stay in our records…

Change Requests

If you need a correction, a copy of stored data, or a closure request, send it through support.

Access Rules

Access depends on local law and on the account checks we can complete.

Common legal questions you ask

These are the questions we hear most when you want a clear path for account records, corrections, and access. We answer through live chat, email, or the request form, and we keep the language plain so you can see what we store, why we store it, and how to ask for a change. If a rule depends on your region or payment path, the answer is the same: it depends on local law.

We keep the details you enter, the device and browser signals that help with security, the chat trail, and transaction labels such as DANA, OVO, GoPay, or QRIS. We store only what we need for support and record checks.

Yes. Send the request from the email or phone on file, and we will verify you before changing anything. If the change touches stored records, support will explain what can be updated and what must stay.

Cookies keep your sign-in state, language choice, and security checks working while you move between pages. You can clear them in Chrome, Safari, or Firefox, then sign in again from the login page.

Access can pause when device checks fail, a request looks inconsistent, or local rules require a stop. Where local law permits, we resume after verification; if not, we close the path at the login stage.

We keep records only for the period needed for account support, dispute handling, and the retention rules that apply to us. When those reasons end, the data is removed or made anonymous on schedule.

Use live chat for the quickest reply, email for a written trail, or the request form when you want a case number. All three routes are checked 24/7, and each starts with identity checks.

Those labels help us match the request to the right account history and spot errors faster. If a transaction needs a correction, the wallet name or QRIS reference gives support a cleaner starting point.

Legal terms for your account

Where to send legal requests

Live Chat

Email

Request Form

How we handle cookies and data

Cookies

Data Handling

Security Checks

Retention

Change Requests

Access Rules

Common legal questions you ask

01 What records do you keep on my account?

02 Can I ask for a correction to my data?

03 How do cookies affect my session?

04 When can my access be stopped?

05 How long do you keep stored records?

06 How do I reach you about a legal request?

07 Why do you ask about DANA, OVO, GoPay, or QRIS?

Related Pages