Reference

surga11 Privacy Policy for Your Account Data

Sic Bo, Sugar Rush and QRIS account access each create a different data point, so our Privacy Policy explains what we collect and why.

Account recordsWallet activityDevice choicesYour privacy requests

Explore Our Lobby Read FAQ

How Wallet and Account Data Is Used

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

Our Privacy Policy covers data you provide when creating an account, completing phone verification and contacting us about account access. It also covers records created when you select DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, such as the payment route, reference, amount and

1
status needed to match a transaction. Device type, browser details, session times and security events help us recognise unusual sign-in activity and keep the account path working. We use this data to provide requested account services, answer support questions, process wallet status checks and meet obligations
2
that depend on local law. If you are in Indonesia, some features or account actions may be available only where local law permits. This policy applies to the surga11 website and its account pages, and it explains how to ask about a record, request a correction
3
or raise a privacy concern.

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

PRIVACY HELP PATH

Get Help With a Privacy Request

A clear support path matters when a phone number, wallet reference or device record needs attention.

Account privacy request Ask us to access, correct or explain personal data through the account help path. Include your registered contact detail so we can match the request before discussing account records.

Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, send the payment reference and status shown in your account. Never include your password or one-time verification code.

Device access concern If a login appears from an unfamiliar phone or browser, contact us through account support and describe the device path. We can check security events and explain the next account step.

HANDLING DETAILS

What Your Privacy Policy Covers

We keep this Privacy Policy practical by connecting each data type to an account action you can recognise.

Data collection

We collect account details you submit, phone verification results, payment references, support messages and technical session data. We do not need your wallet password or one-time code to investigate a status question.

Cookies and sessions

Cookies and similar session tools help keep you signed in, remember selected settings and connect a request to the correct account page. You can manage browser cookie controls, though some account functions may then behave differently.

Account security

Phone verification, sign-in records and device signals help us identify unusual account access. If you change phones, check the account path first and contact support before sharing any wallet reference.

Retention periods

We retain account, payment and support records only as long as needed for the stated service, dispute checks, security work or legal duties. Retention can vary by record type and local requirements.

Data changes

You can ask us to correct inaccurate account details or clarify how a record was used. Send the request through account support with your registered contact detail and the specific field or event.

Privacy contact

Privacy questions belong in the same account help path, where we can verify the request and respond about your records. For a QRIS or bank transfer matter, add its reference without sending login credentials.

Privacy Policy Answers for surga11

These Privacy Policy answers address the questions we expect before you open an account or connect a local wallet. They cover the data collected during phone verification, the device path used for sign-in, payment references and the practical route for asking us to change or explain a record.

It covers account details, phone verification, device and session data, support messages, cookies and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for the account verification step, sign-in support and account record matching. If access or eligibility is discussed, it depends on local law and where local law permits.

Yes. The Privacy Policy covers the payment route, reference, status and related account record for QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity.

We may record device type, browser details, session times, approximate technical signals and security events. These details help connect your login to the correct account and identify unusual access.

Use the account help path and provide your registered email or phone detail, then state whether you want access, correction or an explanation. We may verify ownership before responding.

Retention depends on the record and the reason it was created. Account, payment and support data may remain for service delivery, dispute checks, security needs or legal duties.

Yes. Send the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference and its displayed status. We will not ask you to include a password or one-time verification code.

surga11 Privacy Policy for Your Account Data

Get Help With a Privacy Request

What Your Privacy Policy Covers

Data collection

Cookies and sessions

Account security

Retention periods

Data changes

Privacy contact

Privacy Policy Answers for surga11

01 What does the surga11 Privacy Policy cover?

02 Why does surga11 need my phone number?

03 Does the Privacy Policy cover QRIS and wallet records?

04 What device data does surga11 collect?

05 How do I request a copy or correction of my data?

06 How long does surga11 keep Privacy Policy records?

07 Can I ask about a payment record without sharing my password?

Related Pages