Reference

Privacy Policy for surga12 Accounts

surga12 Privacy Policy explains how we use the details you provide when opening an account, checking wallet status or entering the lobby.

Account dataWallet recordsDevice accessPrivacy requests
Explore Our Lobby Read FAQ
surga12 Privacy Policy for surga12 Accounts
PRIVACY SUPPORT

Where to Send a Privacy Request

A clear support path helps you act on this Privacy Policy without guessing which team to contact.

Account access If your phone verification or login record looks incorrect, contact account support from the…
Wallet records For a privacy question involving DANA, OVO, GoPay or QRIS, share the payment reference…
Data changes When you request a correction or access copy, tell us which account detail concerns…
DATA HANDLING

What We Do With Account Details

We handle account information for specific operational reasons rather than keeping it without purpose.

Collected details

We may receive your account contact details, phone verification state, login timestamps, device and browser signals, support messages and payment…

Cookie choices

Cookies can support session continuity and remember limited settings when you move from login to the lobby.

Account protection

We use phone verification and access signals to reduce mistaken account changes.

Payment matching

A DANA, OVO, GoPay or QRIS reference can help us match a wallet event to your account.

Retention period

We keep account, support and transaction records only while they serve account operation, dispute handling, security checks or legal duties.

Your request path

You can ask for access, correction or clarification through account support.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the account questions we expect you to ask before opening access. They explain why we request phone verification, what payment references mean, how cookies affect a mobile session and where to raise a data concern. If your situation involves eligibility, access depends on local law and our support team can explain the available account path where local law permits.

The surga12 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how long records may be kept and how you can request access or correction through the account support route.

Phone verification helps us connect an account request to the person who controls the verified contact route. It can support login checks and changes to profile details. We may ask you to confirm ownership before discussing records or changing information linked to your account.

We use transaction references and status details to match DANA, OVO, GoPay or QRIS activity with an account. We do not need your wallet password for that process. Never send a wallet password or one-time code in a support message.

Send an account support request using the contact route connected with your profile. State that you want an access copy and identify the account detail involved. We may verify ownership before responding, so the data is not disclosed to another person.

Yes. Tell account support which detail is inaccurate, such as a contact entry or verification status, and provide the verified account route. We will check the request and explain the correction process. Payment references may need to remain unchanged for reconciliation purposes.

Cookies can keep a session active and remember limited page settings while you move between login and the lobby. Browser controls let you restrict them. If you block required cookies, you may need to sign in again or lose some account-session functions.

Yes. Access and eligibility depend on local law. Where local law permits, we handle account data requests through the support path described in this Privacy Policy. We may limit or adjust a response when a legal duty requires particular records to be retained.

Related Pages

surga12 Indonesia Gamelan Riches Reels Account information Live Baccarat Grand FAQ