Reference

surga22 Privacy Policy For Indonesia Accounts

Our Privacy Policy explains how surga22 handles the account, wallet and device data connected with your access to Lightning Roulette, Aviator and other lobby areas.

Account clarityWallet data scopeDevice session controlsPolicy request path

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

surga22 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the data needed to create and maintain your account, including the contact details you submit, phone verification results, sign-in records and device signals used to identify unusual sessions. When you use DANA, OVO, GoPay or QRIS, we record the transaction reference, amount, status and

1
related account identifier so we can match the wallet event without asking for an unrelated wallet password. Bank transfer and virtual account records may include the selected rail and reference number. We use this data to provide account access, investigate payment mismatches, maintain security and answer
2
policy requests. We may share limited details with payment processors, technical service providers or authorities when required by law or where local law permits. Your eligibility and access depends on local law. This page describes our current handling approach; contact us through the routes below when
3
you need clarification or a correction.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

DATA HELP ROUTES

Where To Ask About Your Data

A clear support route matters when a Privacy Policy question affects your account or wallet status. Start from the signed-in support area and include your account identifier, the relevant date and a short description of the request. We use those details to locate the correct record without asking you to send a full password, wallet PIN or unnecessary document.

Team online

Account support path

Use the account support route for a copy request, correction, deletion question or concern about phone verification. Include the email or phone number attached to your surga22 account so we can find the right record.

Wallet status path

For DANA, OVO, GoPay or QRIS data questions, share the transaction reference and status shown beside the cashier record. We can check the matching event without requesting your wallet password or private wallet security code.

Security concern route

If a sign-in appears unfamiliar on your mobile or desktop device, contact support through the account area and mention the session time. We can review the account event and advise the next verification step.

SIX DATA PRACTICES

How Device And Account Data Stay Managed

We keep this policy practical by separating account identity, wallet references, device activity and support requests.

Account creation

When you open an account, we use the submitted contact details and phone verification result to connect your sign-in with the correct account record. We do not need your wallet password to complete this account step.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet event to your account. For bank transfer or virtual account activity, we use the rail and reference details shown in the transaction record.

Cookie controls

Cookies can preserve a session choice and help identify repeated access from the same browser. Clear them in your browser settings when needed; returning to the account may prompt a fresh sign-in check.

Device signals

We may use browser, operating-system and session signals to identify unusual access around your account. These signals support security checks and are not a request for the private contents of your device.

Retention handling

We keep account, payment and support records for the period needed for their stated purpose, legal duties or an unresolved dispute. When a record is no longer needed, our handling follows the applicable retention process.

Change requests

Ask us to correct, access or remove eligible account data through support. We may confirm your identity with the phone verification step before making a change, so one account is not altered by another person.

Privacy Policy Questions For Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. They explain what you can ask us to do, which records help us respond and why a verification step may be needed. For a case-specific request, use the account support route with the smallest useful set of details.

It covers account details, phone verification, sign-in and device signals, cookies, wallet references, payment records, support requests, retention and eligible requests to access, correct or remove data.

Yes. The policy covers DANA, OVO, GoPay and QRIS references, status and account matching details. We use those records to investigate payment questions without asking for your private wallet password.

Phone verification helps connect the person requesting account access with the correct account record. We may repeat that check before changing data, handling a deletion request or discussing a sensitive sign-in event.

You can ask through the signed-in support area. Include your account identifier and request scope; we may verify your identity first, then assess which account, payment and support records can be provided.

Send a correction request through support with the affected field and the accurate replacement. We may ask for a phone verification step before changing account details or records connected with wallet activity.

Contact us through the account support route and state which data you want removed. We assess the request against account security, legal duties, payment records and any unresolved dispute.

Our handling and your eligibility depend on local law. Where local law permits, we respond to eligible data requests and explain any limit that applies to a particular account or payment record.

surga22 Privacy Policy For Indonesia Accounts

Where To Ask About Your Data

Account support path

Wallet status path

Security concern route

How Device And Account Data Stay Managed

Account creation

Payment matching

Cookie controls

Device signals

Retention handling

Change requests

Privacy Policy Questions For Your Account

01 What does the surga22 Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS data?

03 Why does surga22 need phone verification?

04 Can I request a copy of my account data?

05 How can I correct inaccurate Privacy Policy data?

06 How do I request removal of my surga22 data?

07 Does access to this policy depend on local law?

Related Pages