Reference

sins88 Privacy Policy For Your Account

The sins88 Privacy Policy explains what we collect when you open an account, use phone verification, browse Live Roulette or check wallet status, and how you can ask…

Account dataWallet recordsCookie choicesPrivacy requests
sins88 sins88 Privacy Policy For Your Account
REQUEST HELP DIRECTLY

Privacy Help Beside Your Account Path

A privacy question should not require you to search through the lobby. Use the support route shown in your account area and include the email or phone detail connected to your profile, plus a short description of the request. We use those details to locate the right record without asking you to send a wallet password or full payment credential. If a DANA receipt, QRIS status or login event is part of the question, keep its reference ready. Customers in Surabaya and across Indonesia follow the same privacy contact path, where local law permits.

Team online

Account privacy request

Send your request through the account support path with the contact detail used during phone verification. We may ask for a matching account step before changing or releasing personal data, helping us avoid sending records to the wrong person.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and approximate time shown in your account. We use that context to check the wallet event while avoiding requests for your wallet password or private security code.

Login and cookie concern

If a device remembers a session or a cookie choice seems unexpected, contact support from the account route shown on the site. Tell us your browser or device path so we can separate a cookie issue from an account access event.

OUR DATA CONTROLS

What We Do With Your Personal Details

We handle privacy as an account operation, not as a separate promise hidden from the cashier path.

Data we collect

We may receive your name or contact detail, phone verification result, login events, device information, support messages and payment references. For DANA, OVO, GoPay and QRIS, the record is used to identify status and reconciliation rather than to request your private wallet password.

Cookie handling

Cookies and similar browser storage can keep a session active, remember a language or region choice, and help us detect unusual access. You can manage browser storage through your device settings, although clearing it may require you to complete account verification again.

Account security

Phone verification, login timestamps and device signals help us check whether an account request comes from the expected person. Never send a password or wallet security code in support messages. If access looks unfamiliar, use the account contact path promptly.

Retention timing

We keep personal details while they support account access, transaction matching, security checks or an unresolved dispute. When a purpose ends, we remove, anonymise or restrict the record where practical, subject to any legal or payment record that must remain available.

Request a correction

You can ask us to correct a wrong contact detail or clarify how a record is used. Include the account identifier and the requested change. We may verify your identity through the phone or email already connected to the account before acting.

Who receives requests

Privacy questions go to the support contact displayed within the sins88 account path. We route the request to the team handling account records, cookies or payment references. If your question concerns a QRIS or bank transfer record, include only the reference needed to locate it.

Privacy Policy Questions About sins88

These answers address the privacy questions we expect you to ask before opening an account or contacting support. They cover account records, wallet references, cookies, device access and requests for correction or deletion. The full Privacy Policy remains the place to check the current wording for your region, because access depends on local law and is available where local law permits.

The sins88 Privacy Policy covers account details, phone verification, login and device events, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and how to request a correction.

We use the phone verification result to help confirm account access and reduce the chance that a privacy request reaches the wrong person. It can also help us investigate an unfamiliar login. We do not ask you to place your wallet password in a support message.

Yes. The Privacy Policy covers the transaction references and status details created when you use DANA, OVO, GoPay or QRIS through the account path. These details help us match a payment event to the correct account without requiring your private wallet password.

Use the privacy contact route shown in your account support area and identify the email or phone detail linked to your profile. State whether you want access, correction or clarification. We may complete an account verification step before releasing or changing personal data.

Cookies can keep your session available, remember selected settings and help us identify unusual access. Browser storage may differ between a Mobile App path and a desktop browser. You can clear or manage cookies in device settings, but this may trigger phone verification again.

We retain records while they are needed for account access, security checks, payment reconciliation, support handling or a dispute. Some records may remain longer when a legal or payment requirement applies. When the purpose ends, we remove, anonymise or restrict the data where practical.

You can send a deletion request through the account support path, and we will assess it under the Privacy Policy and local requirements. We may need to retain limited records for security, payment reconciliation or legal reasons. Access and request outcomes depend on local law.