Reference

sule123 Privacy Policy For Your Account

Your sule123 Privacy Policy explains how we handle account details, device signals and wallet records when you open Sic Bo, Fish Hunter or other lobby areas.

Account dataDevice choicesWallet recordsAccess requests
Explore Our Lobby Read FAQ
sule123 sule123 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Help With Privacy Requests

A clear contact path matters when a wallet receipt, phone detail or device record needs attention.

Account contact Use the support contact inside your account for a Privacy Policy question about your phone verification, login record or stored profile detail. Include the relevant date and payment reference when a DANA, OVO, GoPay or QRIS record is part of your request.
Receipt check For a bank transfer or virtual account receipt, send the reference shown by your bank and avoid sharing passwords or wallet PINs. We compare the reference with the account record, then explain what data was used to match the payment status.
Access assistance If a lost phone or failed verification blocks your request, tell us which account step stopped working. We may ask for limited details to confirm ownership, and account access remains subject to local law and the checks described in this policy.
CONTROL YOUR RECORDS

What We Do With Your Sule123 Data

We keep the Privacy Policy practical by linking each data use to an account action: access, verification, payment matching, fraud prevention or support.

Data handling

We use profile details, phone verification results and account activity to provide access and protect the account. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to match status, not to request your private wallet passcode.

Cookie choices

Cookies and similar browser signals can keep a signed-in session connected to the correct account and remember basic page settings. You can manage cookies through your browser controls, although changing them may affect the way account access and session checks work.

Account security

Phone verification and sign-in checks help us distinguish your account from an unfamiliar device. If you move from mobile to desktop, we may record session details so a suspicious change can be investigated without asking you to disclose a wallet PIN.

Retention periods

We retain each record only while it supports the stated purpose, an unresolved payment or account question, safety checks, or a legal duty. When the reason ends, we remove, anonymise or restrict the record according to the process described in this Privacy Policy.

Your requests

You can ask whether we hold your account data, request a correction, seek deletion where applicable, or ask for a usable copy. Send the request through the account support route and identify the phone or payment reference involved so we can find the correct record.

Policy contact

Our support contact handles questions about this Privacy Policy, including cookie use, device signals and wallet references. We may need to confirm account ownership before sharing or changing data, and the response path follows local law and the limits explained here.

Privacy Policy Answers For Sule123

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the records created during phone verification, mobile access, wallet payments and support contact, so you can decide what to share. If your question involves a particular DANA, OVO, GoPay, QRIS or bank reference, include that reference through the account contact route where local law permits.

The sule123 Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references, support messages and retention. It explains why each category is used, how you can request access or correction, and when a record may be removed or restricted.

Yes. The Privacy Policy applies when you use DANA or QRIS and also covers OVO, GoPay, bank transfer and virtual account records. We retain the reference and status needed to match the payment with your account, but we do not need your wallet PIN.

Device and session details help us recognise an unusual sign-in, connect your mobile browser with the correct account and investigate access problems. The Privacy Policy treats these signals as purpose-based records, not as a reason to collect unrelated personal details.

Use the signed-in account support contact and ask for a copy of the data linked to your account. Include your verified phone number and any relevant payment reference. We may confirm ownership first, and the response depends on local law and applicable limits.

You can request a correction when your account name, phone detail or another stored record is inaccurate. Send the request through the account contact route and explain the change clearly. We may ask for a verification step before changing data connected to account access.

Retention varies by the purpose of the record, such as matching a QRIS receipt, resolving a bank transfer question, protecting an account or meeting a legal duty. When the reason ends, we remove, anonymise or restrict the record where applicable.

Yes. Ask through the account support contact which cookie or session issue you want explained. You can also adjust cookies in your mobile browser settings. Some changes may affect sign-in continuity, device checks or the account path described in this Privacy Policy.

Related Pages

sule123 Indonesia winbola855 Account information FAQ pamen138