Reference

sule88 Privacy Policy for Your Account

Our Privacy Policy explains what account, device and wallet details we use when you open sule88, sign in, or request account help.

Account dataWallet recordsDevice signalsPolicy requests

Browse Our Lobby Read FAQ

What the Policy Covers at Checkout

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

Our Privacy Policy applies when you create an account, confirm your phone, sign in from a mobile browser, browse titles such as Queen of Bounty or Rocket Crash, and use the cashier area. We may handle your account identifier, phone verification result, device details, sign-in events,

1
chosen language, support messages, and transaction references. Payment references can show whether a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account request was submitted and matched to your account; we do not need your wallet password to check that status. We use these records to
2
provide account access, identify unusual sign-in activity, answer requests, and reconcile payment events. The policy applies to services offered where local law permits, and some data handling can change when a legal request requires it. We do not describe unrelated services here: this page is the
3
Privacy Policy for your sule88 account and its connected payment steps.

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

REQUEST SUPPORT

Need Help With a Data Request?

A clear support path helps when your Privacy Policy question concerns login history, phone verification, or wallet status.

Account questions Ask us to check account details, phone verification, or a sign-in record through the support contact displayed after login. We may request details that confirm you control the account.

Wallet records For DANA, OVO, GoPay, or QRIS questions, send the payment reference and date through the cashier support path. We compare the reference with the account record before responding.

Privacy changes To request a correction or ask how your data is retained, use the same account support route and state the exact record involved. We will explain the next verification step.

HANDLING DETAILS

How We Handle Account Data

We keep this Privacy Policy practical by tying each data use to an account action. Phone verification supports account control, device signals help us examine unusual access, and payment references help match…

Phone verification

Before account access is completed, we may use the phone verification result to connect the account to you. We retain the result as an account-security record rather than requesting your wallet password.

Mobile device signals

When you move from login to the lobby on a phone, we can record device and browser signals linked to that session. These details help us examine unfamiliar access and account requests.

Cookie choices

Cookies can keep a session preference or help us understand whether a page loads correctly. You can manage browser cookie settings, although changing them may affect the sign-in path.

Payment matching

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account events, we use transaction references and status records to match activity to your account without storing wallet passwords.

Retention requests

You can ask how long a particular account, device, support, or payment record is kept. Tell us the record type and date so we can locate the applicable retention detail.

Correction path

If your phone number, account detail, or support record appears incorrect, contact us through the signed-in support route. We may verify account control before changing personal data.

Privacy Policy Questions for sule88

These Privacy Policy answers focus on the records you are most likely to ask about before opening an account or using the cashier. They cover account creation, device access, local wallets, cookies, corrections, and requests for stored data. If your situation is not listed, use the support contact displayed in your account and include enough detail for us to locate the relevant event.

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

We use the verification result to support account control and examine access requests. It can help us distinguish your account activity from an unfamiliar sign-in before discussing personal or wallet records.

No. For DANA, OVO, GoPay, and QRIS status checks, we use payment references and transaction results. We do not need your wallet password to match a payment event with your account.

A mobile or desktop session can provide browser, device, session, and sign-in signals. We use them to support account access, identify unusual activity, and investigate a request tied to your account.

Use the support contact shown in your signed-in account, name the record you believe is incorrect, and include its date. We may verify account control before changing the stored detail.

Yes. Ask through the account support route and identify whether your question concerns account, device, support, or payment data. We will explain the applicable retention detail for that record.

Yes. The policy applies to account data and related requests where local law permits. Certain access or handling steps may differ when a legal requirement applies to your location.

sule88 Privacy Policy for Your Account

Need Help With a Data Request?

How We Handle Account Data

Phone verification

Mobile device signals

Cookie choices

Payment matching

Retention requests

Correction path

Privacy Policy Questions for sule88

01 What does the sule88 Privacy Policy cover?

02 Why does sule88 need phone verification data?

03 Does the Privacy Policy store my wallet password?

04 What device data can sule88 collect?

05 How do I request a correction under this Privacy Policy?

06 Can I ask how long my data is retained?

07 Does local law affect this Privacy Policy?

Related Pages