Reference

surya11 Privacy Policy Explained Clearly

The surya11 Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and enter rooms such as Speed Baccarat Room.

Account dataWallet recordsCookie choicesAccess requests
surya11 surya11 Privacy Policy Explained Clearly
CONTACT ROUTES

Get Privacy Policy Help Directly

A clear contact path helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Account access question If you cannot reach your account, send the registered phone number and the device path you used, such as Android Chrome or mobile Safari. We use those details to locate the access event without asking for your password, then explain which Privacy Policy record is relevant.
Wallet record question For DANA, OVO, GoPay or QRIS activity, include the displayed amount, date and reference while hiding sensitive wallet details. We can check whether the record is linked to your account and explain what data the Privacy Policy allows us to retain.
Data request route Ask for access, correction or removal by using the same support path connected to your account. We may request a clear account step, such as phone verification, before releasing personal data so another person cannot receive your records.
HANDLING DETAILS

How surya11 Handles Privacy Requests

Privacy work follows the same account path you use to reach the lobby: identify the account, check the relevant event and apply the request to the correct record.

Account details

We may collect your name, phone number, email address and verification result when you create or access an account. These details help us identify the correct account during support, including when you ask about a record linked to Speed Baccarat Room or another lobby area.

Payment references

DANA, OVO, GoPay and QRIS can provide a transaction reference and status for matching. Bank transfer or virtual account activity may show BCA, BRI, Mandiri or BNI context. We use these references for reconciliation and support, not as a request for your wallet PIN.

Cookies and devices

Cookies can remember a session, language choice and consent setting on your browser. Device and browser details can help us investigate a failed login or an unexpected session. You can clear browser cookies, although this may require another account access step.

Account security

Phone verification before account access helps connect a request to the right account. We may review sign-in time, browser type and security events when access looks unusual. Never share your password, one-time code or wallet PIN with anyone contacting you.

Retention periods

We retain account, support and transaction records for the period needed for security, reconciliation, dispute handling or a legal requirement that applies to your region. When a record is no longer needed, we remove it or separate it from direct account identifiers where feasible.

Correction requests

If your phone number, email address or another account detail is wrong, contact us with the requested correction and a way to verify ownership. We assess the request against security and legal needs, then tell you whether the record can be changed or why it must remain.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain the records connected with login, wallets, cookies and support, while recognising that access depends on local law. If your question concerns a particular transaction or device, include its date and reference so we can respond to the correct account history.

The Privacy Policy covers account details such as your phone number or email, verification events, device and browser signals, cookie choices, support messages and payment references. For DANA, OVO, GoPay or QRIS, we use status and reference data to match activity, not your wallet PIN.

We use payment data to connect a transaction reference with your account, check whether a wallet or bank transfer reached the expected status and answer reconciliation questions. A virtual account record may include BCA, BRI, Mandiri or BNI context without requiring your banking password.

Where local law permits, you can ask which personal data we hold and why it is used. Send the request through the account support route with your registered phone number or email. We may complete phone verification before sharing records connected to your account.

Yes, you can request a correction to an account detail such as your phone number or email address. Explain what is wrong and what should replace it. We check ownership and any security or legal requirement before changing the record, then confirm the outcome.

We keep account, support and transaction records only for the operational, security, dispute or legal period that applies. The exact period can differ by record and region. When continued storage is not needed, we remove the record or reduce its link to direct identifiers.

Yes. Cookies may keep your session active, remember a language choice or store your consent setting on the browser you use. You can clear them through your browser settings. After clearing cookies, you may need to repeat phone verification before account access.

Your access or eligibility depends on local law. Where local law permits, we handle requests for access, correction or removal through the account support route. Tell us your region and the record involved so we can apply the relevant Privacy Policy process.