Reference

Open surga55 Privacy Policy Before Account Access

Our surga55 Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA and QRIS.

Account dataWallet recordsDevice choicesYour privacy requests
surga55 Open surga55 Privacy Policy Before Account Access
REQUEST HELP

Reach Support About Privacy Requests

You can raise a privacy question through the support path attached to your account and include the email or phone number used for verification. We keep the route close to account and wallet help, so a request about a QRIS receipt, device sign-in, or account record reaches the right team without exposing extra details.

Team online

Account privacy path

Open the account support link and identify the record you want checked, such as a phone number, sign-in event, or profile detail. We use your verified account contact to match the request.

Wallet record query

For DANA, OVO, GoPay, QRIS, virtual account, or bank transfer records, include the transaction reference and date. We only ask for details needed to locate the relevant payment entry.

Access or correction

Tell us whether you want a copy, correction, or deletion assessment. We may ask for an account step or phone verification before changing personal data, helping prevent another person from taking action.

CONTROL YOUR DATA

Protect Your Data Across Devices

Privacy depends on practical controls, not a long statement alone. We separate account details from payment references where possible, check unusual device access, and keep requests tied to a verified contact.

Account data handling

We collect details such as your contact information, verification status, sign-in activity, and selected account settings to operate access and respond to requests. We do not need your DANA or GoPay wallet password.

Cookies and browser storage

Cookies and similar browser records can keep a session active, remember selected settings, and help us understand errors. You can manage browser permissions, although changing them may require another sign-in.

Device and account security

A new phone or browser may trigger an additional account check when sign-in behaviour changes. Phone verification helps us distinguish your request from an attempt made through an unfamiliar device.

Payment references

For QRIS, DANA, OVO, GoPay, bank transfer, or virtual account activity, we may retain reference numbers and status details needed to match a requested account action without storing wallet credentials.

Retention decisions

We retain records only for the period needed for account protection, transaction tracing, dispute handling, legal duties, or a pending privacy request. Deletion timing can depend on the record type and local law.

Who receives a request

Our support and privacy-handling team can assess your request. A payment provider may handle its own data when a rail confirms a transaction, so we explain which party controls the relevant record.

Find Privacy Policy Answers Before Joining

These Privacy Policy answers cover the account, device, and wallet questions you may have before opening an account. If your situation is not listed, use the account support path and include only the details needed to locate your record.

It covers account details, phone verification, sign-in and device records, cookies, payment references, retention, sharing, and the steps for requesting access, correction, or deletion where local law permits.

No. We may receive a payment reference or status for DANA, OVO, GoPay, QRIS, virtual account, or bank transfer activity, but wallet credentials remain with the relevant payment provider.

Device and browser details help us identify unusual sign-in behaviour and protect your account. A new phone can lead to an additional phone verification step before access continues.

Use the account support path, state that you want a copy of your personal data, and provide the verified email or phone linked to the account. We may confirm ownership first.

Yes. Send the incorrect field and the replacement detail through support. We check the request against your verified account contact before making a change, particularly when it affects wallet or sign-in records.

The period depends on the record and its purpose, including account protection, transaction tracing, dispute handling, or legal duties. Our team can explain the applicable retention reason for your request.

Our data practices are described for Indonesian account access, while access and eligibility depends on local law. If a local rule affects your request, we will explain the relevant restriction.