Reference

Open sejatibet Privacy Policy

Your sejatibet Privacy Policy explains what we collect, why we use it and how you can ask for changes before opening an account.

Clear data purposesWallet details explainedRequest changes directlyMobile session controls
Explore Our Lobby Read FAQ
sejatibet Open sejatibet Privacy Policy
POLICY SUPPORT

Check policy help from your account

A clear support path matters when a privacy question meets a login or wallet status issue. From your account, use the support route and include the phone number linked to your account, the relevant date and the payment reference if your question concerns DANA or QRIS. We use those details to locate the right record without asking you to send unrelated account data.

Team online

Account privacy request

Ask about the Privacy Policy through the support route shown after login. Include your verified phone number and request type so we can check identity before discussing account data.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, provide the payment reference and date rather than a wallet password or full security code. We use the reference to trace the relevant record.

Policy change request

If you want to correct, access or remove eligible data, state the exact account field involved. We may request phone verification before confirming what can be changed under local law.

DATA PRACTICES

Protect account data across mobile sessions

Our privacy process follows the account journey rather than treating every record alike. We separate sign-in details, payment references, device signals and browsing events, then limit each use to its stated purpose.

Data handling

We handle phone verification details for account access, payment references for reconciliation and session signals for security checks. A visit to Fishing God or Super Bingo may create a service event tied to your account.

Cookies and sessions

Cookies can keep your signed-in path available and help us recognise a returning device. You can review browser controls on mobile or desktop, although restricting cookies may interrupt account access.

Account security

We may compare a new device, sign-in pattern or phone verification result with earlier account activity. This helps us investigate unusual access without requesting your wallet password through support.

Retention period

We keep account, payment and support records for the period needed for the stated service, security review or legal duty. When that period ends, records are deleted or separated from direct account details.

Who to contact

Use the support route attached to your signed-in account for privacy questions. Mention whether your request concerns device data, cookies, phone verification or a DANA, OVO, GoPay or QRIS reference.

Requesting changes

You can ask us to correct eligible account data or explain its use. We verify the request against your account before making a change, and we state when local law requires continued retention.

Browse Privacy Policy answers for Indonesia

These Privacy Policy answers address the searches we hear most often about account records, mobile sessions and Indonesian wallet references. Read them before opening an account, then use the signed-in support route if your question concerns a specific record or request.

It covers account details, phone verification, device and session records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to create and protect your account access, confirm that a privacy request comes from the account holder and investigate unusual sign-ins across mobile and desktop sessions.

We may record service events such as opening Speed Blackjack, Rocket Crash or Football Betting. These records help us maintain account accuracy, answer support questions and investigate access concerns.

We use payment references, dates and status details to match account activity with DANA or QRIS requests. We do not ask you to send a wallet password or full security code.

Use the support route available after login and identify the account field you want corrected. We may confirm your phone number first, then explain the available action under local law.

Yes. Send a signed-in privacy request naming the record type, such as cookies, device signals, payment references or support messages. We will explain the relevant retention purpose and period.

The policy is available for your account questions, while account access and eligibility depend on local law. If a legal duty affects a request, we explain the reason and next step.

Related Pages

sejatibet Indonesia Speed Blackjack Access guide FAQ Account information