Reference

Privacy Policy for your win slots account

Our Privacy Policy explains what we collect when you open a win slots account, connect DANA or QRIS, and access the lobby from a phone or desktop.

Account recordsWallet activityDevice cookiesPolicy requests
win slots Privacy Policy for your win slots account
HELP WITH YOUR DATA

Reach us when policy questions arise

A clear contact route helps when you want to ask what we hold, correct an account detail, or question a wallet record. Start from the support contact shown in your win slots account area and include the email or phone detail attached to your account, plus the relevant receipt reference if DANA, OVO, GoPay, or QRIS is involved. We use those details to find the right record without asking you to send a password or full payment credential.

Team online

Account access

Ask us to confirm which account details support your login and phone verification. We can help locate a record when the email or phone path is unclear, while you should never send your password, PIN, or complete wallet credentials through a support message.

Wallet status

For a DANA, OVO, GoPay, or QRIS question, share the transaction reference and date shown on your receipt. We can trace the status connected to your account and explain what data was received without requesting access to your personal wallet.

Policy request

Use the account support contact to request access, correction, deletion, or an explanation of processing. Tell us which Privacy Policy question you have and include safe account identifiers so we can verify ownership before discussing private records.

HOW RECORDS STAY CONTROLLED

Keep account and device data clear

Our handling follows the account path you take: registration creates an account record, phone verification confirms access, and later wallet or lobby actions add activity records.

Account creation

When you open an account, we record the contact and verification details needed to establish access. A clear phone verification step helps us separate your request from an unknown person asking about the same email or phone number.

Session protection

Login time, device type, browser signals, and security events can be recorded to protect your session. These signals help us investigate unusual access without treating a device identifier as your full identity.

Cookie choices

Cookies can keep your session and selected account path working between pages. You can review or remove browser cookies in your phone or desktop settings, although some account functions may then ask you to sign in again.

Wallet records

A payment reference, amount status, and timestamp may connect to your account when you use DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. We do not ask for your wallet PIN or complete secret credential.

Retention path

We keep account, transaction, and support records for the period needed to provide the requested service, resolve disputes, protect access, or meet applicable legal duties. When a record is no longer needed, our handling follows the deletion process that applies to it.

Your request

You can ask what data we hold, request a correction, ask about deletion, or question a processing purpose. We first verify account ownership, then explain any limit that depends on local law and the next step available to you.

Privacy Policy answers for your account

These Privacy Policy answers focus on the actions you are most likely to take before opening an account or connecting a wallet. We explain the records tied to verification, device access, payment references, cookies, and support requests in direct terms. If a request concerns eligibility or access, the result depends on local law; contact us through the account support route when you need a record checked.

It covers account creation, phone verification, login and device events, cookies, wallet references, transaction status, game activity, support messages, retention, and requests to access or correct your records. It also explains how local-law requirements can affect access and a data request.

We use phone verification to confirm that the person opening or accessing an account controls the contact route provided. The result supports account security and helps us verify ownership before discussing private records or changing details linked with DANA, OVO, GoPay, or QRIS.

No. When you use DANA or QRIS, we may receive a payment reference, status, timestamp, and related account details, but we do not ask for your wallet PIN or complete secret credential. The same approach applies to OVO, GoPay, bank transfer, and virtual account records.

Yes. Send an access request through the support contact shown in your account area and include a safe identifier, such as your registered email or phone number. We verify ownership first, then explain the records available and any restriction that depends on local law.

Tell us which account, verification, wallet reference, or support detail is inaccurate. Include the relevant receipt date or transaction reference when applicable, but never send a password or PIN. After ownership checks, we can correct the record or explain why a legal or operational limit applies.

Cookies and device signals can preserve your signed-in session and help identify unusual access when you move through the mobile lobby. You can clear or restrict cookies in your phone browser settings. Doing so may sign you out or require another phone verification step.

You can ask about deletion through the account support contact. We assess each record because some account, transaction, security, or support data may need to remain for a stated service purpose, dispute handling, or a legal duty where local law permits.