Reference

data sdy 2025 Privacy Policy for Indonesia

The data sdy 2025 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and access titles such as Live Baccarat Elite or…

Account data explainedWallet records clarifiedYour request options
data sdy 2025 data sdy 2025 Privacy Policy for Indonesia
ASK ABOUT DATA

Support Routes for Privacy Policy Requests

A clear request path helps you correct an account record without sending unnecessary details.

Account access request Ask us to identify the personal data connected with your account.
Wallet record question If a DANA, OVO, GoPay or QRIS receipt appears incorrectly, send the transaction reference…
Correction or deletion Tell us which field or record needs attention and why.
DATA HANDLING MAP

What Our Privacy Policy Covers Daily

We keep the Privacy Policy practical by linking each data category to an account action you can recognise.

Account and verification

When you create an account, we collect the details required for account access and may request phone verification before showing…

Device and login signals

Your mobile browser or desktop session can send device type, browser details, approximate connection data and login time.

Cookies and saved choices

Cookies may remember a session setting, language choice or consent preference.

Wallet and bank matching

For DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity, we handle references, amounts, timestamps and status results needed…

Security and retention

We retain account, verification and transaction records for as long as needed for the stated account purpose, security checks or…

Requests and contact

You can ask about access, correction, deletion or the reason for a data use through the support route displayed in…

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear before an Indonesian account is opened or a wallet is connected. They cover the data behind login, mobile access, game activity and payment matching without asking you to rely on assumptions. If your question is more specific, use the support path inside your account and identify the relevant record, such as a QRIS receipt or phone verification event.

It covers account details, phone verification, login and device signals, cookies, game activity, support messages and wallet or bank references. It also explains purposes, retention, request routes and access conditions. Eligibility depends on local law, so you should read the policy for your location before opening an account.

Yes. When you use DANA, OVO, GoPay or QRIS, we may handle a reference, status, timestamp and receipt detail needed to match the transaction with your account. We do not need your wallet password or banking password to investigate a payment record.

Phone verification helps us confirm that an account access request comes from the person connected with that account. The event and its result can be retained as an account-security record. If you cannot complete the step, contact support through the account path without sharing your password.

The policy describes practical signals such as device type, browser details, approximate connection data and login time. These help us identify unusual access and diagnose a mobile or desktop session. They are not a request for the private contents of your phone, messages or unrelated files.

You can request access to data connected with your account or ask us to correct a specific field. Use the support route shown after login, state the record involved and complete any identity check we request. We may limit a response where local law permits or requires it.

We keep records for the account purpose, security work or applicable legal requirements that make retention necessary. The period can differ between a login event, a phone verification result and a QRIS or bank reference. When the reason ends, we remove or separate the record where appropriate.

Sign in and use the support path displayed in your account, then identify your request as an access, correction, deletion or policy question. Include only the minimum account or transaction reference needed. Never send a password, wallet PIN or full banking credentials through a message.