Reference

surga play Privacy Policy For Your Account

Our Privacy Policy explains how surga play collects, uses and protects the details connected to your account, wallet status and device access.

Account dataWallet checksDevice accessPolicy requests
surga play surga play Privacy Policy For Your Account
CONTACT ROUTES

Ask About Privacy Policy Changes

A clear contact path helps you resolve a privacy question without repeating account details across unrelated channels.

Account privacy request Send a request through the support chat linked to your account when you want to ask what account details we hold or why a phone verification record is connected to your profile.
Wallet data question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include the visible status and date in your message. We use those details to locate the relevant account record without asking for your wallet password.
Correction pathway Tell our support team which account field needs correction, such as your phone number or contact detail. We may confirm ownership first, then record the requested change and explain any limits under local law.
DATA PRACTICES

What We Do With Your Details

Privacy depends on practical handling, not a hidden statement. We separate account details from ordinary browsing signals where our systems allow, restrict sensitive actions behind account checks and use payment references to…

Account collection

We collect details you enter during account opening, including contact information needed for phone verification. We also receive account activity such as login events and selected account settings so we can keep the correct profile connected to your session.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount status and time record in the account area. We use these fields to match a payment event; we do not ask you to disclose a wallet password to support.

Cookie controls

Cookies and similar storage can remember a session, preserve language choices and help detect unusual login behaviour. You can adjust browser controls, although removing necessary storage may require another login or interrupt a privacy preference.

Device security

When you move between a mobile browser and desktop, we may record device and session signals used for account protection. A new device can prompt an additional account check before private wallet or profile details are shown.

Retention period

We retain account, support and transaction records only for the period needed for the stated purpose, account security or applicable requirements. When a record is no longer needed, our handling follows deletion, restriction or anonymisation procedures where available.

Your requests

You can ask for access, correction or clarification through the account support route. We may request identity confirmation, explain any legal restriction and tell you what action we took regarding the specific data request.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you may have before opening an account or connecting a local wallet. We keep the wording practical: what we collect, how we use it, what happens on a new device and how you can ask for a change. If your situation needs a legal assessment, access depends on local law.

The Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect it, when records may be retained and how you can request access or correction.

Phone verification helps connect the correct person to an account and supports account security when a private request is made. We may use the verification result to protect profile and wallet details, while any access remains where local law permits.

Yes. The Privacy Policy covers payment references and status details that reach the account after a DANA or QRIS event. The relevant provider keeps its own records under its separate rules, while we use received references to reconcile your account activity.

We may collect session, browser and device signals linked to login security, such as a new device event or session timing. These signals help us decide when an additional account check is needed before showing private profile or wallet details.

Use the support chat connected to your account and describe the data request clearly. You can ask about access, correction or a specific payment reference. We may confirm account ownership first, then explain the result and any limit under local law.

We keep records for the time needed to provide the stated account function, protect security, answer a support request or meet applicable requirements. The period can differ by record type, and we follow deletion, restriction or anonymisation steps when retention is no longer needed.

Yes. The Privacy Policy explains how cookies or similar storage support sessions, language choices and unusual-login checks. You can change browser settings, but removing necessary storage may sign you out or prevent a saved privacy preference from working.