Reference

Privacy Policy For Your surya72 Account

Our Privacy Policy explains how surya72 handles the details you provide when opening an account, signing in from a mobile browser, or checking DANA and QRIS status.

Account clarityWallet recordsDevice accessPolicy requests
Browse Our Lobby Read FAQ
surya72 Privacy Policy For Your surya72 Account
HELP WITH YOUR DATA

Privacy Questions Reach Our Support

A clear support route helps you ask what data we hold, why a wallet reference appears on your account, or how to correct a phone number.

Account data request Ask our support team which account details are linked to your phone verification or…
Wallet record question For DANA, OVO, GoPay or QRIS questions, mention the payment rail and receipt reference…
Correction or removal If a contact detail is wrong or you want to request removal of eligible…
DATA HANDLING DETAILS

What We Keep And Why

The practical parts of our Privacy Policy are designed around account events you can recognise: phone verification, mobile sign-in, wallet status checks and support replies.

Account creation

When you open a surya72 account, we collect the contact and verification details needed to create your account path. Phone verification helps us distinguish the account holder from an unverified request. You can ask support to clarify which fields are attached to your account.

Mobile browser access

A mobile browser may send device, browser and session details when you sign in and move from the account page toward the lobby. We use these signals to recognise unusual access and protect your session. They do not replace the account details required for verification.

Cookies and sessions

Cookies can remember a session preference, support account continuity and help us identify technical errors. Your browser settings can control or remove cookies, although changing them may affect sign-in steps. Our Privacy Policy explains which cookie purposes apply when you access the site.

Wallet and payment logs

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can remain in payment records so we can match status checks and receipts to the right account. We do not need your wallet PIN for this process. Retention follows the purpose and applicable legal requirements.

Security controls

We use phone verification, session checks and account activity logs to investigate sign-in problems or an unexpected account change. If you contact us about a security event, give the time, device path and affected account step. Never include your password, PIN or one-time code.

Changes to your data

You can ask us to correct inaccurate contact details or request access to eligible personal records through support. We verify the requester before making a change. Where local law permits, you may also request deletion, subject to records we must retain for security, payment matching or legal duties.

Privacy Policy Questions About surya72

These Privacy Policy answers address the account, device and payment questions you may have before opening an account or returning to surya72. They explain what we collect, how we use it, how long records may remain and which support path to use. Access or eligibility depends on local law, so check the policy wording that applies to your location.

The surya72 Privacy Policy covers account creation, phone verification, sign-in sessions, device details, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how retention works and how you can request access, correction or removal of eligible personal data.

Yes. Our Privacy Policy includes records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We may keep a reference, status and matching details so support can investigate a receipt or stalled wallet status without needing your wallet PIN.

When you sign in through a mobile browser or desktop browser, we may receive browser, device, session and security-event details. The Privacy Policy explains how these details help identify unusual access, maintain a session and diagnose account problems. They are handled alongside, not instead of, phone verification.

Use the support path connected to your account and ask for a personal data access request. Include your account identifier and enough detail to locate the request, such as the phone verification step. We verify your identity first, then explain which records can be provided under applicable law.

You can ask support to correct inaccurate account details, including a contact field linked to phone verification. Our Privacy Policy requires an identity check before changes are made. If a payment reference is involved, mention DANA, OVO, GoPay or QRIS and the receipt status so the correct record is reviewed.

Retention depends on why the data was collected and whether a record is needed for account security, payment matching, support history or legal duties. The Privacy Policy does not promise one period for every category. You can ask support which retention rule applies to a specific account record.

Read the current Privacy Policy on this page and use the account support route for questions about a change. Tell us which section or data category concerns you, such as cookies, mobile sessions or QRIS records. Access and any available request rights depend on local law.

Related Pages

surya72 Indonesia Account information Liga 1 Handicap Odds About Us Gamelan Riches Megaways