Reference

surgawin Privacy Policy for Your Account

Our Privacy Policy explains how surgawin handles the account, device and wallet data connected with your access.

Account dataWallet referencesDevice choicesPolicy requests
surgawin surgawin Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Help Beside Your Account

A clear contact path matters when you want to ask about your Privacy Policy rights or a wallet reference. We keep policy questions separate from game requests, so your message can focus on account data, device records, cookies, retention or a correction request. Use the support contact shown after sign-in and include only the details needed to locate your account.

Team online

Account privacy request

Open the support contact from your signed-in account and state whether you need access, correction or deletion guidance. We may ask for account details to confirm that the request belongs to you.

Wallet reference check

If your question concerns DANA, OVO, GoPay or QRIS data, include the payment reference rather than a wallet password. This helps us trace status records without asking you to disclose private wallet credentials.

Device access concern

Tell us if a phone, browser or login event looks unfamiliar. We can use the account access record to help you review the event and take the account-security steps available through your profile.

DATA PRACTICE

How surgawin Handles Device And Account Data

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

Account data use

We use your account details to create access, confirm phone verification, protect sign-in and connect requests to the correct profile. We do not need your DANA, OVO or GoPay wallet password for these steps.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can appear in our records when you request a payment action. We use that reference to check status and reconcile the account entry.

Cookies and storage

Essential cookies or device storage can keep your session active and remember required settings. You can review cookie controls in your browser, although turning off essential storage may interrupt sign-in or account access.

Security signals

We may record device type, browser details, connection data and login time to identify unusual account activity. If a sign-in does not look familiar, contact us through the account support route promptly.

Retention choices

We keep account and payment records only for the period needed for access, security, reconciliation or a legal obligation. A deletion request can be assessed against those continuing needs under local law.

Requesting changes

To ask for access, correction or deletion, use the support contact displayed in your account and describe the requested change. We may verify account ownership before changing or releasing data.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to ask before opening access. We explain the practical path for data requests, device concerns and local wallet records, while access remains subject to local law. If your situation is not listed, use the support contact available in your account.

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

We use phone verification to confirm the account step before access and to connect support requests with the correct profile. The way this data is used depends on local law and the service action requested.

Yes. The policy includes the payment reference and status connected with DANA or QRIS activity. We use those records for account reconciliation and status checks, not to request your wallet password.

You can request access to the data connected with your account through the support contact shown after sign-in. We may verify ownership first, and the response path depends on local law.

Send a correction request through the account support route and identify the field that appears wrong. Include the smallest useful detail, such as an account reference, so we can check it securely.

You may ask about deletion through the support contact in your account. We assess the request against active access, security, payment reconciliation and legal retention needs where local law permits.

Contact us through the support route shown in your account and mention the unfamiliar phone, browser or login event. We can use the access record to help identify the relevant security step.