Reference

sumaterabet Privacy Policy Explained

Our Privacy Policy explains how we handle the account details behind Lightning Roulette, Egypt Book of Mystery and local wallet access.

Account clarityWallet recordsDevice choicesCookie controls
sumaterabet sumaterabet Privacy Policy Explained
CONTACT PATHS

Get Privacy Help Near Wallet Status

A clear support path helps you ask what we hold, why we use it or how to correct an account detail. Contact us through the support route shown after account access, and include your registered phone number plus the relevant payment reference when a DANA, OVO, GoPay or QRIS record is involved. We use those details to locate the request without asking you to send a password.

Team online

Account access

If you cannot reach your account, tell us the device path you used and the phone verification stage reached. We can check the access record while keeping your password private.

Wallet receipt

For a wallet question, send the payment rail and receipt reference, such as QRIS or DANA. We compare the record with your account status before explaining what data was used.

Privacy request

Ask us to correct, export or remove eligible personal data through the same support route. We may verify account ownership first, where local law permits, to protect your records.

SIX DATA CONTROLS

Six Privacy Steps Inside sumaterabet

We apply this Privacy Policy to practical account events rather than treating it as a page you read once.

Collected fields

We use account contact details, verification results and payment references for access and transaction checks. We do not ask for a password in support messages, and we avoid collecting unrelated details.

Cookie choice

Cookies and similar device storage can keep a session active or remember your selected settings. You can review browser controls before returning to the lobby, though some account functions may then need another check.

Account security

Phone verification is part of the account access path. We use device and session signals to spot unusual access, while you should keep verification codes private and sign out on shared devices.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a wallet event to the correct account. It does not give support staff your wallet password.

Data retention

We keep records only for as long as needed for the stated account, payment, security or legal purpose. Retention can vary by record type and depends on local law.

Change requests

You may ask what personal data we hold, request a correction or ask about deletion through support. We confirm ownership first and explain any legal reason a record must remain.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the searches we hear before an Indonesian account is opened. They cover the data connected to your phone verification, mobile device, wallet reference and support request. If your question concerns a right or restriction not listed here, send us the request through the account support route and we will assess it under applicable local law.

It covers account details, phone verification, payment references, device signals, cookies, support requests and retention. It explains how we use those records for access, security, payment matching and legal duties.

Phone verification helps confirm that the account access request belongs to you and supports account security. We may record the verification result, but you should never send the code or password to support.

Yes. The policy covers references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use them to match a payment event and investigate receipt or wallet status questions.

We may receive browser, session and device security signals from the path you use to reach your account. These signals help protect access and diagnose a stalled session, not create unrelated personal records.

You can contact support to ask what eligible personal data we hold, request a correction or ask about a copy. We may verify account ownership first, and the outcome depends on local law.

We retain each record for the account, payment, security or legal purpose that requires it, then remove or anonymise it when appropriate. The exact period varies by record and depends on local law.

Start with browser cookie controls for local storage choices, then contact support for an account-linked request. We explain which data can be deleted and which records may remain where local law permits.