Reference

surga200 Privacy Policy for Your Wallet Path

Our Privacy Policy explains how surga200 handles the details behind your account, including phone verification, device access and payment references for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie controlsPolicy requests
surga200 surga200 Privacy Policy for Your Wallet Path
HELP WITH DATA

Privacy Policy Support Beside Your Account

A clear contact path matters when an account detail or wallet reference looks wrong. From your account area, use the support link beside the cashier path and include the phone number or…

Account privacy request Ask us to check the account details connected with your phone verification. Include the account identifier shown in your profile so we can distinguish your request from another DANA, OVO, GoPay or QRIS record.
Wallet reference check If a payment status does not match your receipt, send the reference through the support link beside the cashier. We use the reference to investigate the record and avoid collecting unnecessary wallet credentials.
Policy clarification For questions about cookies, device records, retention or a change request, contact us through the account support route. We will explain which data is involved and what action is available under local law.
OUR DATA PRACTICE

Inside surga200 Privacy Handling

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

Account details

We use your account identifier and verified phone detail to open the correct account path, confirm requested changes and send account-related responses. We do not ask you to place a wallet PIN in a support message.

Device and login records

A mobile or desktop sign-in may create records such as device type, browser details, time and network signals. These help us investigate access concerns and protect your account without treating a device signal as your identity by itself.

Payment references

For DANA, OVO, GoPay and QRIS, we keep the reference and status needed to match a cashier request. Bank transfer and virtual account checks may also show BCA, BRI, Mandiri or BNI as the relevant bank rail.

Cookies on your browser

Cookies can keep your session, language setting and privacy choices available while you move from login to the lobby. Browser controls let you remove or restrict them, although some account functions may then need to be repeated.

Retention and removal

We keep information only while it serves an account, security, dispute or legal purpose. When a record no longer has a valid purpose, we remove it or separate it from direct account details where a legal duty does not require continued storage.

Requests and corrections

You can ask us to correct account data, explain a payment reference, provide details about our use of information or request removal where permitted. Send the request through account support and include enough detail for us to verify ownership.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the questions we expect before you open an account or continue using the mobile path. They focus on the records created by phone verification, cookies, device access and local wallet references. If your question concerns a circumstance not listed here, use the support route beside the account cashier and we will identify the relevant part of the policy.

We collect the account details needed to create your profile, including your phone verification record and sign-in information. We may also record device and network signals, support messages and payment references when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Your phone number supports the account access step and helps us confirm that a requested change belongs to you. It can also help support locate the correct account. We do not ask you to share a DANA, OVO or GoPay PIN with us.

Our Privacy Policy does not require us to collect your wallet PIN. For QRIS and other wallet requests, we use the transaction reference, amount and status needed to match the cashier record. Keep your PIN and authentication codes private and do not send them to support.

Cookies can remember your session, language setting and selected privacy preferences while you move between login and account pages. You can restrict or delete them in your browser settings. If you do, some sign-in steps or saved choices may need to be completed again.

Yes. Send a correction request through the account support link and identify the information that appears wrong. We may ask for an account detail or phone verification step before changing it. We will assess the request under this Privacy Policy and where local law permits.

We retain each record while it is needed for account operation, security checks, payment reconciliation, disputes or legal duties. The period can differ by record type. When the purpose ends and no legal duty remains, we remove the data or separate it from your account.

Use the support link in your account, positioned beside the cashier path, and state whether your question concerns account data, cookies, device access or a wallet reference. Include only the details needed to locate the matter; never include a wallet PIN or login code.