Reference

live sdy pools Privacy Policy for Your Account

The live sdy pools Privacy Policy explains what account, device and wallet details we collect, why we use them, and how you can request changes.

Account dataWallet detailsCookie choicesAccess requests
Explore Our Lobby Read FAQ
live sdy pools live sdy pools Privacy Policy for Your Account
CONTACT ROUTES

Switch to Support When Data Questions Stall

A clear contact path helps you resolve a Privacy Policy question without repeating your account story. Start from the account help route and include the phone number linked to your profile, the subject of your request and any relevant wallet reference. We use those details to locate the right record while limiting unnecessary disclosure. If your question concerns Semarang access, a QRIS receipt or a login device, say so plainly. Our support team can explain the next step for access, correction or deletion requests.

Team online

Account help

Use the account help path for questions about your Privacy Policy rights, phone verification, login records or a request to correct details. Include your registered phone number so we can identify the correct account before discussing personal data.

Wallet status

For a DANA, OVO, GoPay or QRIS data question, share the payment reference rather than a wallet password or security code. We can check the linked status and explain which account record supports the transaction enquiry.

Security concern

If a login from an unfamiliar device appears in your account, contact support through the account route and describe the device behaviour. We may ask for phone verification before changing access details or discussing the stored record.

DATA PRACTICES

Browse How We Handle Account Records

We handle personal data as an operating task, not as a broad profile about you. Account records connect your phone verification, sign-in events and chosen wallet route so we can protect access…

Data we collect

We may collect your name or account identifier, phone number, verification result, sign-in timestamps, device signals and payment references. If you use QRIS, DANA, OVO or GoPay, we use the related status detail to connect an account action with the correct record.

Cookie controls

Cookies and similar device storage help keep your session active and remember security settings. You can manage browser permissions or clear stored data, but doing so may require a fresh login and phone verification before account access resumes.

Account security

We use phone verification, login event checks and device signals to reduce unauthorised access. Never send a password or one-time security code through support. If a device path looks unfamiliar, ask us to check the account record before making changes.

Payment references

A wallet or bank reference can remain attached to an account action after the balance status is resolved. For BCA, BRI, Mandiri or BNI transfers, we retain the reference needed to match a receipt, answer a dispute or meet an applicable record duty.

Retention periods

We keep personal data only while it supports account security, payment reconciliation, support handling or a legal requirement that applies where local law permits. When a retention reason ends, we delete, aggregate or restrict the record according to its purpose.

Change requests

You can ask us to access, correct or delete eligible personal data through the account help route. Tell us which field or record is concerned, such as a phone number or QRIS reference, and we may verify account ownership first.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers cover the account and payment questions we expect you to ask before opening access. They explain what happens with device signals, wallet references, cookies and personal data requests without moving away from the policy subject. If your situation is not listed, use the account support route with the smallest amount of detail needed to identify your record.

The Privacy Policy covers data collected through account creation, phone verification, sign-in activity, device use, cookies, support contacts and payment references. It explains why we use each category, how long it may remain connected to your account and how you can request access or correction.

We use your phone number to support account identification and verification before access or sensitive account changes. It can also help us match a support request to the right record. We do not need your wallet password or one-time security code for a normal policy enquiry.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS. We use those details to match an account action or investigate a receipt question, while the wallet credentials themselves should remain with you and your payment provider.

Use the account help route and ask for a personal data access request. Include your registered phone number and identify the record you want, such as login activity or a QRIS reference. We may verify account ownership before releasing information linked to your profile.

You can request a correction when an account detail is inaccurate or out of date. State the field clearly, such as your phone number or account identifier, and provide the replacement detail through support. We may check ownership before applying the change to protect your account.

Retention depends on the reason for holding a record, including account security, payment reconciliation, support handling or a legal duty. When that reason ends, we delete, aggregate or restrict the data where appropriate. A payment reference may remain longer than a short-lived session record.

You can ask us to delete eligible personal data through the account help route. We first assess whether the record is still needed for security, payment reconciliation or a legal requirement. If deletion cannot apply to part of the record, we explain the reason and restrict its use where suitable.

Related Pages

live sdy pools Indonesia Omaha Turbo Round Account information Access guide Live Baccarat Elite