Reference

Open surga88 Privacy Policy for Your Account

Our surga88 Privacy Policy explains what account details we collect, why phone verification is needed, and how payment records are handled when you use DANA, OVO, GoPay or…

Account detailsPhone verificationWallet recordsCookie choices
surga88 Open surga88 Privacy Policy for Your Account
CONTACT OUR TEAM

Browse Privacy Help Beside Account Support

A clear contact path helps when you need a copy, correction or explanation of your data. We ask you to use the support route shown inside your account area and include the email or phone detail attached to the account, without sending a password or full wallet credential. This lets us confirm ownership before discussing private records.

Team online

Account access

If phone verification or sign-in blocks a privacy request, tell us the affected account detail and device path. We use that context to confirm ownership without asking for your password.

Wallet records

For DANA, OVO, GoPay or QRIS records, include the transaction date, rail name and status shown in your account. We can then trace the relevant entry without requesting unnecessary wallet credentials.

Privacy requests

Ask us to access, correct or remove eligible account data through the support route in your account area. We may request phone verification before sending records or changing a stored detail.

OUR DATA PRACTICE

Switch Through surga88 Privacy Controls

We handle privacy as an account operation, not as a hidden setting. Our process connects sign-in checks, wallet records, browser cookies and support requests so you can understand why a detail exists.

Account data

We collect details needed to open and maintain your account, such as contact data and phone verification status. We use them to match requests to the correct account and prevent mistaken changes.

Cookie choices

Cookies and similar browser markers can remember sign-in state, language preferences and page activity. You can adjust browser settings, although restricting them may interrupt the mobile path or account access.

Security checks

A sign-in from a new device or an unusual account action may trigger an additional check. We use phone verification and related access signals to reduce unauthorised changes to your records.

Retention periods

We keep account and payment records only as long as needed for the stated purpose, account support, dispute handling or legal duties. The period can differ between a wallet entry and a login event.

Payment records

A DANA, QRIS, bank transfer or virtual account reference helps us match a cashier status to your account. We do not need your full wallet password to investigate a receipt or pending entry.

Change requests

You can ask us to correct contact data or clarify how a record is used through account support. We verify the request first, then explain any legal or operational reason for keeping a detail.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the searches we hear most often before account creation. They cover account data, device access, wallet records, cookies and requests to change or receive a copy of your details. If your question is not listed, our account support route can direct it to the right team.

The surga88 Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment records linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps us confirm that the person requesting account access or a data change controls the recorded contact route. It also helps protect wallet status and account records from mistaken or unauthorised changes.

Yes. Send a request through the support route inside your account area, using the contact detail attached to the account. We confirm ownership first and then explain which records can be provided.

We use wallet and QRIS references to match a payment status, receipt or dispute with the correct account. We do not need your wallet password for that check, and access depends on local law.

Yes. The Privacy Policy covers cookies and similar markers used on the mobile browser path for sign-in state, language choices and account navigation. Browser controls can restrict them, but some access steps may stop working.

Retention depends on the purpose of each record, such as account support, payment disputes, security checks or legal duties. A wallet entry may therefore remain for a different period than a routine login event.

Contact us through the account support route and name the detail you want changed. We verify the request, make eligible corrections, and explain when a record must remain because of legal or account obligations.