Reference

Privacy Policy for sdy loto accounts

Our Privacy Policy explains how sdy loto handles the details you provide when opening an account, confirming your phone, using DANA or QRIS, and contacting support.

Clear data purposesWallet record handlingCookie choicesAccount access steps
sdy loto Privacy Policy for sdy loto accounts
POLICY HELP PATH

Get help with a privacy request

A clear request path helps when you cannot tell which account detail needs attention. Contact us through the support route available after sign-in and state that your message concerns the Privacy Policy.

Account privacy request Use the signed-in support path to ask for access, correction, deletion, or a copy of personal data. We check the account step first so a request is connected to the right sdy loto record.
Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference, share the date and transaction status without sending your PIN. We use those details to locate the relevant record safely.
Login and device concern If a new phone, browser, or sign-in alert looks unfamiliar, tell us through the account support route. We may verify your phone before discussing device data or changing account contact details.
DATA PRACTICE

What the policy says about your details

Our handling of personal data follows the practical account events you can recognise: registration, phone confirmation, wallet activity, device access, and a direct support request.

Collection at account opening

We collect the details needed for your account path, including contact information and phone-verification status. When you move from login to a lobby page, related sign-in and device details can help us protect that access.

Payment references only

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity can create transaction references. The Privacy Policy explains their purpose for matching account records, checking status, and responding to a payment question.

Cookies on your device

Cookies may remember a session, language choice, or account-flow setting on your browser. You can manage browser cookie controls, although restricting necessary cookies may affect sign-in and the way privacy choices are saved.

Account security checks

Phone verification and sign-in checks help us avoid discussing personal data with the wrong person. Never share your password, PIN, or one-time code in a support message, even when asking about privacy.

Retention and deletion

We retain records for the period described in the Privacy Policy, based on account, support, security, or transaction needs. You can ask whether a record can be removed; some records may need to remain for legal or operational reasons.

Changing your details

Ask through the signed-in support route if your phone, contact detail, or account information needs correction. We may confirm ownership before making a change, and we will explain the next step if a request needs more detail.

Privacy Policy questions for your account

These Privacy Policy answers address the account questions Indonesian customers usually ask before sharing contact details or connecting a wallet. They cover data collection, cookies, payment references, phone verification, retention, and the direct path for requesting changes. If your situation is not listed, use the privacy request route after sign-in and describe the exact record you want us to check.

It covers data linked to your account, phone verification, sign-in device, support messages, cookies, and transaction references. It also explains why we use those details, when disclosure may be needed, how retention works, and how you can request access or correction.

Phone verification helps connect an account request to the correct account holder before we discuss personal data or change contact details. It also supports sign-in protection. We will not ask you to place a password, PIN, or one-time code in a support message.

Yes. The Privacy Policy covers references connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity. We use those references to match account records, check a stated status, and answer a request without asking for your wallet PIN.

Sign in and use the support route for a privacy request. State whether you want access, a copy, correction, or deletion, then provide the account phone number and relevant date. We may verify ownership before sharing or changing personal data.

On a mobile browser, cookies can retain a session, language choice, or saved privacy setting. Your browser controls can restrict them, but necessary cookies may be required for sign-in and account access. The Privacy Policy explains these purposes in more detail.

Retention depends on the type of record and its account, security, support, transaction, or legal purpose. The Privacy Policy describes the applicable periods and explains why some records may remain after a deletion request where continued storage is required.

Yes. You can read the Privacy Policy before completing registration and contact us through the available support path if a point is unclear. For account-specific requests, we may need the account step and phone verification before discussing personal data.