Reference

Privacy Policy for Your sista99 Account

sista99 Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby, or check wallet status through DANA, OVO, GoPay and QRIS.

Account recordsWallet activityDevice choicesCookie controls
Explore Our Lobby Read FAQ
sista99 Privacy Policy for Your sista99 Account
REQUEST HELP SAFELY

Support Routes For Privacy Questions

A clear support route helps you raise a privacy question without sending sensitive wallet details into the wrong place. Start from your signed-in account support path and describe the request, such as a copy of account data, a correction, or a question about a QRIS status record. We may ask for an account step or phone verification before discussing personal records.

Team online

Account support path

Use the support route attached to your signed-in account for a Privacy Policy request. Include the email or phone reference connected to your account, but do not send a password, PIN or full wallet credentials.

Cashier record check

If your request concerns DANA, OVO, GoPay or QRIS data, mention the payment rail and transaction reference shown in your cashier history. We use those fields to locate the correct record without asking you to repeat private wallet access details.

Identity confirmation

For deletion, correction or access requests, we may confirm the phone verification step already linked to your account. This protects your records from an unauthorised request while keeping the privacy conversation tied to the right account.

DATA HANDLING DETAILS

Inside sista99 Privacy Controls

We handle privacy as an account process, not as a broad promise. Your sign-in, device session, wallet status and support history each serve a defined security or service purpose, while cookies help…

Account data

We may hold your registration details, phone verification result, sign-in history and account settings. These records help us connect a request to your account and detect an unusual access pattern without treating every device visit as a new profile.

Wallet references

Payment records show the rail selected, such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account, plus status and reconciliation references. We use these fields to trace cashier activity and respond to a specific account question.

Cookies and sessions

Cookies and session data can remember sign-in choices, language settings and page preferences. You can adjust cookie behaviour through your browser controls, although switching them off may require you to repeat an account step.

Device security

We may record device type, browser details, approximate session signals and login time to protect account access. This supports checks when a new phone or browser appears, while it does not give us access to your device files.

Retention choices

We retain records only while they support account security, payment reconciliation, dispute handling or a legal duty. When a purpose ends, data may be deleted, separated from your account or kept in a restricted form where a record must remain.

Change requests

You can ask us to view, correct or remove eligible personal data through the account support path. State the request clearly, and we will confirm identity where needed before changing a phone, profile field or connected account record.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep the wording practical so you know which account step to use and what records may be needed.

The Privacy Policy covers account registration, phone verification, sign-in sessions, device signals, cookies, support requests and payment references. It explains why we use those records, how long they may remain, and how you can ask for access, correction or removal where local law permits.

We do not need your wallet password, PIN or full wallet login credentials to match a cashier record. For DANA, OVO, GoPay or QRIS activity, our records focus on the selected rail, account reference, transaction status and reconciliation details.

Phone verification connects an account request to the person who controls the registered contact path. We may use that step before discussing private records or changing account details, especially when a request concerns wallet status, sign-in history or deletion.

Yes, you can send an access request through the signed-in account support path. Tell us which records you mean, such as profile details, device sessions or payment references. We may verify your identity before releasing data linked to your account.

Use the account support path and identify the field that needs correction, such as a phone number or profile detail. We may ask you to complete the relevant account step before changing it, so an unauthorised person cannot redirect your account.

Retention depends on the purpose of each record. Payment references may remain for reconciliation, disputes or legal duties, while device and session data may be restricted or removed when no longer needed for account security. The applicable period can depend on local law.

You can request deletion through the signed-in support route, and we will assess which records are eligible. Some account, payment or security records may need to remain for legal duties, dispute handling or fraud prevention, even after other data is removed.

Related Pages

sista99 Indonesia Access guide Live Blackjack Grand FAQ Account information