Reference

sdy lotto paito Privacy Policy

Our Privacy Policy explains how sdy lotto paito handles your account data when you open the lobby, verify your phone, or use DANA, OVO, GoPay and QRIS.

Account data clarityWallet record handlingCookie choicesPhone verificationPolicy contact path
sdy lotto paito sdy lotto paito Privacy Policy
POLICY HELP ROUTES

Where To Ask About Privacy Policy

A clear contact route matters when you want to know what we hold or why a record appears beside your account.

Account contact route Use the support contact shown after login for a Privacy Policy question about your…
Cashier record help If your question concerns DANA, QRIS, OVO, GoPay, bank transfer or virtual account records…
Access request check For a copy, correction or deletion request, contact us through the policy route attached…
HANDLING AND CONTROL

Privacy Controls From Login To Lobby

We apply the Privacy Policy across the steps you actually take: opening an account, moving from mobile login to the lobby, checking wallet status and contacting support.

Account data

We may hold your account name, contact detail, phone verification result and sign-in history to keep access tied to the correct profile. We do not need unrelated files from your device. If a field is inaccurate, ask us to check the account record and explain the correction needed.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in transaction records. We use these references to reconcile an account request and answer a status query, rather than treating them as a reason to collect unrelated wallet content or contacts.

Cookies

Cookies can keep a login session active, remember a selected setting and help us understand whether a page is working on your browser. You can remove or restrict cookies through browser controls, although changing them may require another login or reset a saved preference.

Mobile sessions

When you use a mobile browser to move from login to the lobby, we may record device and session signals such as browser type, time and security events. These signals help us review an unusual access attempt without reading personal content stored elsewhere on your phone.

Retention checks

We keep records for as long as needed for account operation, payment reconciliation, security checks or a support request, then assess whether continued storage has a clear purpose. A request about retention can name a login event, QRIS reference or specific account field for faster handling.

Your requests

You may ask what account data we hold, request a correction, ask about a processing purpose or seek deletion where applicable. We confirm the requester through the account route, explain any lawful reason to retain a record and respond according to local requirements.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the points you may check before opening an account or contacting us. We keep each response tied to an actual account step, device path or wallet record, including phone verification, QRIS activity and mobile browser sessions. If your question needs a record-level answer, use the policy contact route shown after login and provide only the details requested for verification.

It covers account data, phone verification, sign-in and device signals, cookies, wallet references, support records, retention and requests about access or correction. It applies to the data handling connected with your account and the lobby, where local law permits.

We may collect the account details needed to create your profile, confirm your phone before access and maintain sign-in security. Browser and session signals can also be recorded. We do not need unrelated files, contacts or personal content stored on your device.

DANA and QRIS references help us match a wallet request with the correct account and investigate a status question. The same approach can apply to OVO, GoPay, bank transfer and virtual account records. We use the reference for reconciliation, not unrelated wallet content.

Yes. Use the policy contact route shown after login and identify the field that appears wrong, such as a phone detail or account name. We may complete a phone verification check before changing the record, then explain what was updated or why further confirmation is needed.

Cookies can support session continuity, remember a browser preference and help identify whether a page responds correctly. You can restrict or remove them in your browser settings. After doing so, you may need to log in again or select your preference again.

Retention depends on the purpose of the record, such as account access, payment reconciliation, security review or a support request. We assess whether continued storage remains necessary. Ask through the policy route about a named record, such as a QRIS reference or sign-in event.

Contact us through the account policy route and state whether you want access, correction, purpose details or deletion where applicable. We verify that the request comes from you, may ask for the relevant account step, and handle the request according to local law.