Reference

sulebet Privacy Policy for Your Account

Our Privacy Policy explains how sulebet handles the details you provide when you open an account, verify your phone, enter the lobby and use DANA, OVO, GoPay or…

Clear data purposesWallet record contextPhone verification detailsCookie choices
sulebet sulebet Privacy Policy for Your Account
CONTACT PATHS

Ask About Your Privacy Policy

A clear support route helps when you want to understand a record, correct an account detail or ask why a security check appeared. Start from the support channel shown after login and include the phone number connected to your account without sending a wallet password. If you are locked out, use the login help path and provide only the details needed to locate your account. Our team can also trace a payment reference from the cashier path.

Team online

Account questions

Use the signed-in support channel for access, phone verification or data requests. We may ask for an account detail to confirm that the request comes from you before discussing personal records.

Cashier records

For DANA, OVO, GoPay or QRIS status questions, open the cashier help path and share the transaction reference. We use that reference to investigate without requesting your wallet password.

Locked access

If your device cannot reach the account, use the login help route visible on the access screen. We first check account and security signals, then explain the next privacy-safe step.

DATA PRACTICES

How We Handle Account Privacy

Privacy is handled through ordinary account operations rather than hidden wording. We separate access checks from wallet credentials, use device signals to spot unusual login patterns, and limit…

Account details

We use your phone number and account settings to identify the account, complete phone verification and deliver account-related replies.

Device signals

When you sign in from a mobile browser or desktop, we may record device and session signals.

Cookies

Cookies and similar storage can keep a session active, remember selected settings and help us understand basic page access.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps connect a cashier request with its status.

Security checks

Phone verification and sign-in checks protect account access when device behaviour changes.

Retention requests

You can ask what personal data we hold, request a correction or ask about removal.

Privacy Policy Answers for sulebet

These answers address the searches we hear most often about the Privacy Policy, account records and local wallet activity. If your situation is different, use the account support channel or login help path and include only the minimum details needed to locate your account.

The sulebet Privacy Policy explains how we collect, use, protect and retain account, device, cookie and payment-reference data. It also describes how you can ask for access, correction or removal where local law permits.

We use your phone number to create and locate your account, complete phone verification and respond to account requests. We may compare it with limited account details before discussing personal data with you.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. These references help match a cashier request and status; we do not need your wallet password.

When you use a mobile browser or desktop, we may collect session, device and security signals linked to access. We use them to identify unusual sign-ins and protect the account, not to read unrelated device content.

Cookies can keep your session active, remember settings and support basic access measurement. You can clear or restrict them through your browser, but login, phone verification or other account steps may need to be repeated.

Yes. Contact us through the signed-in support channel, state whether you want access or correction, and identify the account with limited details. We verify the request first and explain any legal retention that applies.

We retain selected account, security and transaction references only as long as needed for account protection, dispute handling or legal duties. When a record is no longer needed, we remove or de-identify it under our process.