Reference

win100 Privacy Policy For Your Account

The win100 Privacy Policy explains how we use account details, wallet records and device data when you open an account or access titles such as Live Blackjack Gold…

Account dataWallet recordsCookie choicesContact requests
win100 win100 Privacy Policy For Your Account
PRIVACY HELP PATH

Where To Ask About Your Data

A direct support route helps you resolve a Privacy Policy question without sending account details through an unverified channel. Start with our on-site support chat and include the account phone number only when the agent requests it through the secure conversation. We can explain a data request, help locate a wallet record or clarify why an account step asks for verification. Please avoid posting passwords, wallet PINs or full payment credentials in a message. Your request can concern activity from Bandung, Medan or another Indonesian location.

Team online

Support chat

Use the support chat linked from your account area for a Privacy Policy question. We first confirm enough account context to avoid exposing data to the wrong person, then explain the relevant record, request path or access step.

Wallet record help

If a DANA, OVO, GoPay or QRIS reference appears unclear, share the transaction date and masked reference through support. We use that limited detail to locate the record while keeping your full wallet credentials out of the conversation.

Account request

For a copy, correction or removal request, tell us which account detail you mean and use the contact route shown on this page. We may ask for an account check before changing or releasing personal data.

HANDLING YOUR RECORDS

What We Do With Account Data

Clear handling matters when your account connects login activity with local wallet records. Our Privacy Policy describes the practical controls we use around access, cookies, security checks and retention.

Account details

We use your phone number, login details and verification information to create and protect your account. Before changing sensitive account data, we may compare the request with the account record so another person cannot redirect access.

Cookie controls

Cookies and similar session signals help keep a login active, remember a selected setting and detect repeated failed access. You can manage browser cookie settings, although restricting essential cookies may interrupt the account path or return you to login.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI may be matched with an account request. We use the reference to confirm status and reconcile the requested transaction, rather than asking for a wallet PIN.

Device security

We may record device type, browser details, session timing and connection signals when you sign in. These checks help us spot an unusual login or repeated failed attempt; they do not give us access to unrelated files on your phone.

Retention timing

We keep records for as long as needed for the purpose described in the Privacy Policy, account support, security checks or applicable local requirements. A deletion request may not remove records that must remain for a defined operational reason.

Change requests

You can contact us to ask for access, correction, deletion or an explanation of processing. Include the email or phone route connected with your account, and we may verify ownership before sharing, editing or removing a record.

Privacy Policy Answers For win100

These Privacy Policy answers address the searches we most often expect before account access. We keep the replies tied to actual records such as login events, wallet references, cookies and verification details. If your situation is different, use the support chat and describe the specific data or account step involved. Access and eligibility depends on local law, so the response may depend on your location and the request type.

The win100 Privacy Policy covers information you provide for an account, records created by login and verification, wallet references, cookies, device signals and support messages. It explains why we use each category, how we protect access, how retention works and how you can make a data request.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. We may use a masked reference, amount status and timing to reconcile the account request, while support should never need your wallet PIN or full secret credential.

Use the on-site support chat and state that you want an account data request under the Privacy Policy. Give the phone or email connected with your account, identify the record you want, and complete any ownership check we require before we release or explain personal data.

You can ask us to correct an inaccurate account detail through the support route. Tell us which field is wrong and provide the updated value through the secure conversation. We may verify the account first, and some payment or security records may need to remain unchanged for reconciliation.

It does. Cookies and session signals can keep your login active, remember settings and help detect unusual access on a mobile browser. Your browser controls can restrict them, but essential restrictions may send you back to login or affect account access until settings are restored.

We retain account, support, security and transaction-related records for the period needed for their stated purpose, account operation or applicable local requirements. The exact period can differ by record type. You can ask support which category applies and whether a deletion request can be completed.

The page can be read before account access, but service availability and eligibility depends on local law. Our Privacy Policy still explains the handling of a request, login data or wallet reference. If your location creates uncertainty, contact support before submitting personal details or opening an account.