Reference

Account rules for your access

Our Terms & Conditions explain how your account works across live casino tables, slots, and sportsbook markets, including the checks we may ask for before access starts.

Account rulesLocal lawDevice checksWallet name match

Explore lobby Read FAQ

What this policy covers in practice

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

These terms set the rules for account creation, use, and any request we need to verify before it is accepted. If you connect DANA, OVO, GoPay, or QRIS, the wallet name may need to match the name on the account record before we continue. When we

1
talk about access or eligibility, it always depends on local law and is available only where local law permits. If a clause affects a correction, a lock, or a dispute, we use the current page text and your registered contact to decide what happens next, and
2
you can ask us to check the exact paragraph again before you continue. We do not move a request forward until the account details, device sign-in, and wallet record line up with the page rules, which helps keep each case traceable. If you notice a mismatch,
3
contact us first so we can compare the account record, the device used, and the clause involved.

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

CONTACT PATHS

Where to send terms questions

For terms questions, the fastest path is live chat, followed by email or the help form if you need a longer record.

DATA HANDLING

How we handle account records

We keep the policy tied to the data we actually need: account name, contact detail, device type, and request history.

Data We Keep

We store only the details needed to manage your account and a terms request: name, contact address, device type, and relevant wallet reference. That lets us verify a clause, answer a dispute, and keep the record traceable.

Cookie Behavior

Cookies remember your session, language choice, and login state so you do not repeat the same checks on every page load. If you clear them, the site may ask for verification again the next time you sign in.

New Device Check

When a new phone, browser, or desktop tries to enter the account, we may ask for a one-time code before the session continues. That helps us keep access tied to the registered contact and device history.

Session Match

We expect the name on the account and the wallet record to match when a request depends on identity. If the details differ, we pause the action until you confirm the correct record from your registered contact.

Retention Window

Support threads, request logs, and case records stay only as long as needed for dispute handling, account history, and legal duties. After that period, we archive or remove them under our retention routine.

Change Requests

Send change requests from the registered email or live chat, name the exact field you want updated, and cite the clause that affects it. We will confirm the request before we edit the record.

Questions about account rules and access

If you want the short version before opening an account, these answers cover access, data use, wallet checks, device changes, and how to contact us. We keep each answer tied to the current page text, and the same local-law rule still applies when a question touches eligibility or access. Read the clause numbers here before you send a request, especially if you are using DANA, OVO, GoPay, or QRIS.

They cover account creation, access checks, device sign-ins, data use, wallet-name matching, and the steps we follow when a clause needs to be applied. The current page text is the one that matters for your next use.

Yes, when the account details do not match, a verification step fails, or local law requires a pause. We only use the current clause and your registered contact when we decide how to handle the session.

We keep the data needed to trace the case: your name, contact address, device type, relevant wallet reference, and the request history linked to the clause. That helps us answer you without asking for more than we need.

A name match helps us confirm that the request comes from the same account holder and not a copied profile. If DANA, OVO, GoPay, or QRIS details differ, we will ask you to correct the record first.

Send us the exact field, the correct value, and the clause that applies through live chat or email from your registered address. We confirm the request before we edit the record, so the change stays traceable.

We keep request records only for as long as needed to handle disputes, account history, and any legal duty tied to the clause. After that, the records are archived or removed under our retention routine.

Use live chat for the fastest handoff, or email if you want a written trail. Include the clause number, your registered name, and the wallet reference so we can locate the case quickly.

Account rules for your access

Where to send terms questions

How we handle account records

Data We Keep

Cookie Behavior

New Device Check

Session Match

Retention Window

Change Requests

Questions about account rules and access

01 What do sobatboss Terms & Conditions cover?

02 Can you pause my access under the terms?

03 What data do you keep for terms checks?

04 Why does the wallet name need to match?

05 How do I request a correction to my account details?

06 How long do you keep request records?

07 Who do I contact about a clause or dispute?

Related Pages