Reference

Open the surg11 Privacy Policy

surg11 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your account area.

Account recordsWallet checksDevice accessCookie choices
surg11 Open the surg11 Privacy Policy
CONTACT OPTIONS

Choose a clear privacy contact route

A direct request helps us locate the correct account record without exposing details in a public message.

Account data request Ask us to identify the personal data connected to your account, explain its purpose…
Wallet record question For a DANA, OVO, GoPay or QRIS record, send the payment reference, date and…
Correction or deletion Tell us which account detail needs correction or which request you want assessed for…
DATA PRACTICES

Explore the controls behind this policy

Privacy choices work best when they match the way your account is actually used. We separate account identity, device signals, lobby activity and payment references so a support…

Account details

We collect details you submit for account creation and phone verification, then connect them to the account needed for access.

Device signals

Your browser or mobile device can provide technical signals such as session data, device type and security events.

Payment references

A DANA, OVO, GoPay or QRIS payment can produce a reference, amount status and timing record.

Cookies and sessions

Cookies and similar session tools help us keep you signed in, remember essential settings and protect pages that require account…

Security checks

Phone verification, session controls and payment matching help us check that an account request comes from the account holder.

Retention requests

We keep records only for the operational, security or legal purposes that apply to the account and its transactions.

Find answers about your Privacy Policy

These Privacy Policy answers address the account questions we expect before registration, especially around phone verification, Indonesian wallets and device access. We keep the response tied to surg11 records rather than describing unrelated platform functions. For a record-specific answer, use your account phone number and the payment reference or device detail that helps us locate the correct event.

The Privacy Policy covers account details, phone verification, device and session signals, lobby activity linked to your account, cookies, payment references and support requests. It also explains why we use those records, how security checks work and how you can request access, correction or removal.

We use your phone number to create and identify the correct account and to complete phone verification before account access. It also helps support match a Privacy Policy request to your account. We may ask for an additional account step before discussing personal details.

Yes. The Privacy Policy includes payment references and status details connected with DANA, OVO, GoPay and QRIS. These records help us match a receipt or pending status to your account. A bank transfer or virtual account can create similar reference data for support checks.

We use device type, browser session details and security signals to keep account pages working and identify unusual access. This can help explain a failed login or interrupted wallet check. The Privacy Policy treats these signals as operational and security records tied to the relevant session.

You can ask what personal data categories are connected to your account and why we use them. Send the request through the account support path with your phone number and a clear subject. We verify account control before discussing or providing personal records.

Tell us which account detail is incorrect and provide the accurate replacement detail through support. We check the account and any linked payment record before confirming a correction. A DANA, QRIS or bank transfer reference may need to remain unchanged for an open status check.

You can request deletion or ask whether a category can be removed. We assess active account needs, security records, payment reconciliation and any legal retention requirement before replying. Access depends on local law, so the result can differ between an unused detail and an open transaction record.