Reference

Privacy Policy for surya 88 Accounts

surya 88 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account recordsWallet statusCookie choicesPhone verification
surya 88 Privacy Policy for surya 88 Accounts
CONTACT YOUR WAY

Privacy Policy Help From Your Account

A clear contact path matters when you need to ask what data we hold or why an account record appears in a certain state. Our support route starts from the account and cashier area, so we can match your request with the correct phone verification and payment reference without asking you to repeat private credentials. You can ask about collection, use, retention, correction or deletion where local law permits. Include only the details needed to locate the issue, and we will explain the next step through the available account contact channel.

Team online

Account contact

Open the support path from your signed-in account when your Privacy Policy question concerns phone verification, profile details or account access. We use the account context to locate the right record, while you should keep your password, wallet PIN and one-time codes private.

Wallet status

For a DANA, OVO, GoPay or QRIS data question, include the payment reference and approximate time shown in your cashier history. We can then separate a wallet status query from an account query without requesting your full wallet credentials or asking for unnecessary personal details.

Policy request

If you want to ask for correction, a copy of relevant account data or removal where local law permits, describe the request plainly through the available support channel. We may verify account ownership before responding so private records are not disclosed to another person.

SIX DATA CHECKS

Six Privacy Policy Commitments We Follow

We keep this policy practical by linking each data use to an account action you can recognise. Phone verification supports account ownership checks; device signals help us identify unusual sign-in behaviour; cookies…

Data collection

We collect the details you provide during account creation, such as your contact details and verification response, plus records created when you sign in or contact support. We do not need your wallet PIN to match a DANA, OVO, GoPay or QRIS reference.

Purpose matching

Each record has an operational reason. Phone data supports account access, device signals help detect unusual sign-in patterns, and payment references help reconcile a cashier event. We use these details for the purpose described in this Privacy Policy or a related legal duty.

Cookie controls

Cookies can retain sign-in or display preferences and help us understand which page path delivered a request. Your browser settings can restrict cookies, although some account functions may then require another sign-in or may not display the same way.

Account security

We use phone verification and account activity signals to reduce the chance of an unauthorised person entering your record. Never share a password, one-time code or wallet PIN. If access looks unusual, contact us from the account support path as soon as possible.

Retention choices

We keep account, support and transaction records for as long as needed for the stated purpose, dispute handling or applicable legal requirements. When a retention period ends, we remove or separate the record where practical, subject to any duty that still applies.

Change requests

You may ask us to correct inaccurate account details, explain a data use or consider deletion where local law permits. Send the request through the available support route, identify the registered account and state the exact change; we may verify ownership before acting.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened or while a wallet record is being checked. We keep the wording tied to the actual surya 88 account path: phone verification, device activity, cookies, payment references, support requests and local legal requirements. If your situation is unusual, contact us through the account support route with only the minimum details needed to identify your record.

The surya 88 Privacy Policy covers account details, phone verification, device and connection signals, cookies, support messages and payment references. It explains why we use each category, how we protect access, how long records may remain and how you can request correction or other action where local law permits.

Phone verification helps us connect account access with the person who opened the record and helps us investigate unusual sign-in activity. We use the verification result for account security and support handling; you should not send us one-time codes, passwords or wallet PINs in a message.

Yes. The Privacy Policy covers the transaction references and wallet status needed to match a cashier event involving DANA, OVO, GoPay or QRIS. We use those references to investigate a pending or mismatched record, not to request your private wallet PIN or full wallet credentials.

We may receive device and connection signals created when you sign in or use the account, such as browser or device context and activity timing. These signals help identify unusual access and display the account path correctly. They are handled under the purposes described in the Privacy Policy.

Use the available support path from your account area and state whether you want correction, a copy of relevant records, an explanation of use or deletion where local law permits. Include your registered phone number and the request details, but leave out passwords, one-time codes and wallet PINs.

We retain personal data for the period needed for the purpose collected, account support, dispute handling or applicable legal requirements. The exact period can differ by record type, such as phone verification, support messages or payment references. You can ask support how retention applies to your record.

Start with the account contact route shown near the cashier and support area, then describe the Privacy Policy issue in clear English. For a wallet query, add the transaction reference and approximate time. We may verify account ownership before discussing private records or making a requested change.