Reference

suribet Privacy Policy For Your Account

The suribet Privacy Policy shows what we collect when you create an account, verify your phone, browse Live Blackjack Salon or use DANA and QRIS.

Account dataWallet recordsDevice choicesPolicy requests
suribet suribet Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Near Your Account

A clear support route helps you resolve a data question without repeating your account story.

Account access If you cannot open the privacy page after phone verification, use the logged-in account support route. Tell us whether the issue appears on mobile browser or desktop, and we will direct the request to the correct account check.
Wallet record For a DANA, OVO, GoPay or QRIS data question, send the transaction reference rather than a wallet password. We use the reference to locate status, amount and timing records while keeping your wallet credentials outside our support exchange.
Change request Ask us to correct, export or delete eligible account data through the same support route. Include the phone number attached to your account and a precise request so we can confirm identity before making a privacy change.
DATA PRACTICE

How suribet Handles Privacy Requests

We separate account operation from the wallet credentials held by DANA, OVO, GoPay or QRIS. Our records support phone verification, transaction matching, fraud checks and responses to your privacy requests.

Data collection

We collect details needed to open and maintain your account, such as your phone number, verification result, login events and selected wallet rail. Browsing activity around Live Blackjack Salon or Majapahit Empire Reels may also create session records used to keep account functions working.

Cookie choices

Cookies and similar browser storage can remember a session, preserve a language choice and help us detect repeated login failures. You can clear them through your browser settings, although removing them may require phone verification again before account access.

Account security

Phone verification is checked before account access, and unusual device or login patterns may trigger an additional check. We do not ask for your DANA, OVO, GoPay or QRIS wallet password, and you should never place that credential in a support message.

Payment records

A wallet or bank entry can include its rail, reference, amount, status and account link. For BCA, BRI, Mandiri or BNI transfers, these fields help match a receipt and investigate a cashier question without exposing unrelated account activity.

Retention periods

We keep account, security and transaction records for as long as needed for the stated purpose, dispute handling or legal duties. When a record is no longer required, our process removes it or separates it from direct account identifiers.

Your request

You can ask what account data we hold, request a correction, seek an eligible copy or ask about deletion through support. We verify the request against your account phone number before changing records, and some limits may apply where local law permits.

Privacy Policy Answers For suribet

These Privacy Policy answers focus on the account, wallet and device questions you may have before opening an account. We keep the process practical: use your verified phone number, identify the relevant payment rail and describe the requested change. If a legal restriction applies, access depends on local law.

It covers data linked to account creation, phone verification, login, mobile browser sessions, game browsing, cashier activity and support requests. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used for matching and security.

No. Our Privacy Policy describes transaction references, status, amount and account links rather than wallet passwords. When you use DANA, OVO, GoPay or QRIS, keep the wallet credential inside that provider’s own service and never send it through suribet support.

Use the support path available after login and submit a data access request with the phone number attached to your account. We may ask for phone verification or another account check before releasing data, and the response remains subject to local law.

Yes, you can ask us to correct eligible account details through support. State which field is wrong and provide the account phone number. For a payment record, include the DANA, OVO, GoPay, QRIS or bank reference so we can locate the correct entry.

Device and cookie data help keep a login session active, remember selected settings and identify unusual access. A mobile browser and desktop browser may create different session signals. Clearing cookies can end the session and prompt phone verification again.

We retain account, security and transaction data for the period needed to operate the account, resolve disputes or meet legal duties. After that need ends, we remove or anonymise the record under our retention process, subject to applicable local requirements.

You can submit a deletion request through the logged-in support route. We first confirm your identity and then assess which records can be removed. Some account, payment or security records may need to remain where local law permits or requires it.