Reference

surga 11 Privacy Policy for Your Account

Our Privacy Policy explains how we collect, use and protect the account details connected with your access to surga 11.

Account dataDevice sessionsWallet referencesPrivacy requests
surga 11 surga 11 Privacy Policy for Your Account
PRIVACY HELP

Where Privacy Questions Meet Account Help

A clear support path helps when a privacy request and an account issue arrive together. Sign in, open the account help route near the cashier area, and include the phone number on your account plus any relevant payment receipt. We use those details to locate the correct record without asking you to send a wallet password or full bank credentials.

Team online

Account access

If phone verification or a device session blocks your request, tell us the account step that stopped. We can check the relevant access record while avoiding requests for your wallet password.

Wallet status

For DANA, OVO, GoPay or QRIS questions, attach the payment receipt reference and status shown in your account. We use that reference to investigate the matching privacy record.

Data request

Ask us to access, correct or remove eligible account details through the account help route. Include a reachable contact and the specific record so we can confirm the request safely.

DATA CONTROLS

How We Protect Account And Wallet Records

Privacy work follows the account journey rather than a broad data collection habit. We separate phone verification, device access and payment references, limit internal access to operational needs, and use account checks…

Data handling

We collect account details, verification results, device signals and payment references for stated purposes such as access, transaction matching, security checks and support resolution.

Cookies

Cookies and session markers can remember an active sign-in path and help connect your browser with the right account. You can manage browser cookie settings, though some access steps may stop working.

Account security

Phone verification is checked before account access and account changes. Never send us a wallet password, full card secret or one-time code when asking about privacy.

Record retention

We retain records only for the operational, security or legal purpose that requires them. When that purpose ends, our handling process removes or separates the data where applicable.

Change requests

You can request correction of an inaccurate phone or account detail through support. We may ask for account verification before making a change to prevent another person taking control.

Contact route

For a copy, correction or deletion request, use the account help route and describe the exact data involved. We will explain any identity check or legal reason affecting the request.

Privacy Policy Questions About surga 11

These answers address the privacy questions we hear before account access, especially around phone verification, mobile sessions and Indonesian wallet references. Read the full policy above, then contact account help if your request involves a specific record or payment status.

The Privacy Policy covers account details, phone verification, device sessions, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create the account, confirm phone ownership before access and protect account changes. It also helps support locate the correct record when you send a privacy request.

No. A DANA, OVO, GoPay or QRIS reference helps us match payment status, but it does not give us permission to read unrelated wallet content or request your wallet password.

Use the account help route near the cashier area and ask for a data copy. Include your account phone number and the records you want covered, then complete any identity check we request.

Yes, where the change is eligible. Contact support with the inaccurate detail and the replacement value. We may verify your account first so another person cannot alter your phone or payment record.

We keep account, device and payment records only for the operational, security or legal purpose described in the Privacy Policy. Once that purpose ends, handling follows the removal or separation process.

Yes. It applies to mobile browser sessions, cookies, phone verification and device signals used when you access the account. Mobile access and eligibility depend on local law and available account checks.