Reference

surga5000 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, sign in on mobile, or select DANA, OVO, GoPay or QRIS.

Account dataCookie choicesWallet securityAccess requests

Explore Games Read FAQ

Explore What Our Privacy Policy Covers

surga5000 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect account details you submit, contact data used for phone verification, device and browser signals, sign-in records, and payment status connected with your chosen rail. For example, a DANA, OVO, GoPay or QRIS reference may be kept so we can match a cashier event to

1
your account without storing a wallet password. Our Privacy Policy also explains cookies, security checks, retention and requests to correct or remove eligible data. If you reach us from Jakarta or another Indonesian location, the same policy applies to that account flow. Access and eligibility depend
2
on local law, and you can ask our support team to clarify a section before opening an account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST HELP DIRECTLY

Open A Support Request About Privacy

A clear contact path matters when your account record, cookie choice or wallet reference needs attention.

Live chat Use the live-chat path shown on our site for questions about account data, cookie settings or a DANA, OVO, GoPay or QRIS reference.

Account contact Send your request from the contact route linked to your account so we can compare the phone verification record and discuss privacy changes with the right person.

Payment trace For a wallet or bank transfer query, provide the transaction reference only. We use it to locate status data without asking for your wallet password or security code.

SEE OUR DATA PRACTICE

Browse How We Handle Your Data

Our Privacy Policy is tied to practical account events rather than vague statements. We separate sign-in, device, cookie and payment-status records so a request can be checked against the right account step.

Account collection

We receive the details you enter for account creation and phone verification, then use them to connect sign-in activity with the account record you asked us to maintain.

Device signals

Browser type, device details and sign-in timing can help us identify unusual access. We use these signals for account protection, not as a substitute for your password.

Cookie controls

Cookies can keep a session working and help us understand which policy page was opened. You can adjust browser cookie settings, although some account steps may then need repeating.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may support reconciliation. We do not ask you to provide a wallet password in a support request.

Retention checks

We retain records only for the operational, security or legal purpose explained in our Privacy Policy. Ask support which category applies when you request deletion or correction.

Change requests

To request access, correction or removal of eligible data, contact us from your account route and describe the record. We may verify account ownership before making a change.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the account and payment questions you are most likely to have before using surga5000. If your situation is unusual, contact us through live chat with the smallest useful set of account details, and we will point you to the relevant policy step.

It covers account details, phone verification, device signals, cookies, sign-in records, payment references, retention and requests to access or correct eligible data connected with your account.

We use phone verification to connect the person requesting account access with the correct account record and to reduce mistaken changes. We do not need your one-time code in support messages.

Yes. The policy covers payment-status and reference data linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps, while wallet passwords remain with your payment provider.

Use the account contact route or live chat, describe the record you want checked, and include your verified sign-in phone number. We may confirm account ownership before responding.

Cookies can maintain a browser session and record that you opened a policy page. If you block them, login or the move from login to the lobby may require extra steps.

Retention depends on the record type and its operational, security or legal purpose. Our Privacy Policy explains the relevant period, and support can clarify which category applies to your request.

Yes. Contact us through the support path displayed on the site and mention your account concern. Access and eligibility depend on local law, including for Indonesian accounts and devices.

surga5000 Privacy Policy For Your Account

Open A Support Request About Privacy

Browse How We Handle Your Data

Account collection

Device signals

Cookie controls

Wallet references

Retention checks

Change requests

Check Privacy Policy Answers Before Opening

01 What does the surga5000 Privacy Policy cover?

02 Why does surga5000 need my phone verification details?

03 Does the Privacy Policy cover DANA and QRIS activity?

04 How can I request a copy or correction of my data?

05 How does surga5000 use cookies on mobile?

06 How long does surga5000 keep account records?

07 Can I ask questions about Privacy Policy access in Indonesia?

Related Pages