Reference

Privacy Policy for Your Account Data

Our Privacy Policy explains what we collect when you open a data sdy loto account, move from login to the lobby, or check DANA and QRIS status.

Account clarityWallet contextDevice controlsPolicy access
data sdy loto Privacy Policy for Your Account Data
HELP WITH PRIVACY

Get A Clear Answer About Your Data

A direct support route helps you ask about the Privacy Policy without sending sensitive details through an open message.

Policy questions Use the account contact route to ask what data we hold, why a record appears, or how the Privacy Policy applies to your account. Keep your message focused and never include a password, wallet PIN or full payment credential.
Access requests If you want a copy of account or device records, identify the phone number connected to your account and complete the requested verification step. We use that check to avoid releasing personal data to the wrong person.
Wallet concerns For a payment-status question, provide the date, method and reference shown beside DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We can then connect the privacy request with the correct account record.
DATA HANDLING DETAILS

What Our Privacy Process Covers

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

Account records

We use account details such as your phone number and verification result to create the correct account record, confirm that you are signing in to it, and respond to requests made through the account contact path.

Wallet references

DANA, OVO, GoPay and QRIS may produce a method, status or reference record. We use that limited payment context to match an action with your account and investigate a status question without requesting your wallet PIN.

Cookies and sessions

Cookies and session markers can remember sign-in state, protect account pages and keep your selected path working. Clearing browser data may sign you out, so you may need to repeat phone verification before account access.

Device signals

Browser type, device details and security events help us notice unusual access and keep pages usable on a phone. They also help us distinguish a normal move from mobile login to a desktop session.

Retention choices

We retain records for the period needed for account security, payment matching, support handling and legal duties that apply where local law permits. When a record is no longer needed, our process removes or separates it.

Changes and contact

You can ask us to correct an inaccurate phone number, account detail or contact record through the signed-in support path. We may verify your identity first, then explain what can be changed and when the update takes effect.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the points you are most likely to check before opening an account. We cover the data connected with login, mobile browsing and local wallet records, along with the steps for asking about access or correction. Where a request depends on a legal requirement, the applicable rule is where local law permits.

It covers account details, phone verification, login and session records, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security and how to request access or correction.

We use your phone number to create and identify your account, complete the clear verification step before account access, and help support match a request to the right record. Keep the number current so a correction or access request can be checked properly.

Yes. The Privacy Policy covers the payment method, status and reference details connected with a DANA or QRIS action, as well as similar records for OVO and GoPay. We use this context to match activity to your account, not to collect your wallet PIN.

When you use a mobile browser, we may receive browser type, device details, session markers and security events. These records help keep login and the lobby working, identify unusual access and connect a support question to the correct session without needing content from your personal files.

Sign in, open the account contact path and ask for an account-data access request. Include the phone number linked to the account and complete any identity check we request. We will explain the available records and any limits that apply where local law permits.

Yes. Send a correction request through the signed-in support route and describe the inaccurate field, such as a phone number or contact detail. We may verify you first, then update the record when permitted and tell you how the change is handled.

You can ask through the account contact path and mention the browser or device involved. Clearing cookies may end your session and require phone verification again. Our support team can explain the relevant session record and the available browser-side steps.