Reference

sins88 Privacy Policy For Your Account

Your account settings give you a direct path to understand, manage and question the data connected with your sins88 account.

Clear data purposesWallet record contextAccount request pathPhone and desktop access
sins88 sins88 Privacy Policy For Your Account
ACCOUNT HELP

Get Privacy Help Near Account Support

A clear contact path matters when your account data or wallet record needs attention. We ask you to start from the signed-in account help route, where the relevant account identifier and payment…

Data request Use the account help route to ask what personal data is linked to your profile, and include the email or phone detail used during account verification.
Wallet record For a DANA, OVO, GoPay or QRIS question, attach the payment reference and date so we can separate your request from another account.
Access concern If a phone session, password step or account sign-in raises a privacy concern, describe the device path and we will route it for account checking.
DATA PRACTICE

How sins88 Handles Your Data

We keep the Privacy Policy practical by tying each explanation to an account action you can recognise. The sections below cover collection, cookies, security, retention and requests to change your records.

What we collect

We may handle account identifiers, phone verification details, device signals and payment references. We use each category for account access, status checks, security or a purpose stated in the Privacy Policy.

Cookie controls

Cookies and similar browser storage can help remember an account session and protect the sign-in path. Your browser settings provide controls, while disabling them may affect account access.

Account security

We use phone verification and session checks to reduce mistaken access. Never share a password or verification code; contact account support if a device session does not look like yours.

Record retention

We retain account and transaction records only for the period needed for the stated service, security, legal or dispute purpose. The Privacy Policy explains why a category may remain stored.

Change a detail

You can ask us to correct an inaccurate account detail through the signed-in support route. Include the field, the desired correction and enough account context for us to verify ownership.

Request access

To ask for a copy or explanation of information linked to your account, send a Privacy Policy request from account help. We may verify ownership before releasing or changing records.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions you are most likely to have before sharing details with us. We keep the wording tied to real actions, including phone verification, mobile browser sessions and wallet references from DANA, OVO, GoPay and QRIS. If your situation is not covered, use the account support route and mention the relevant policy section.

The sins88 Privacy Policy covers account data, phone verification, cookies, device signals, payment references, security checks, retention and the steps for asking to access or correct your records.

We use phone verification to connect you with the correct account and reduce mistaken access. It can also help us investigate a sign-in concern or a payment reference linked to your account.

Yes. The Privacy Policy explains how DANA, OVO, GoPay and QRIS references may be used to match receipts, check transaction status and respond to an account payment question.

Open the signed-in account help route and ask for access to your records. Include your account identifier, and be ready for an ownership check before any data is released.

Yes. Send the requested correction through account help, naming the inaccurate field and the replacement detail. We assess the request against ownership checks and the requirements described in the Privacy Policy.

Cookies can retain a session and support the sign-in path on your phone. Your browser controls them, but blocking necessary storage may interrupt account access or require another sign-in.

Contact account support through the signed-in help route, describe the phone or desktop path and change your password if possible. We can then check the session against the account record.