Reference

sdy pools Privacy Policy For You

Your account details, wallet records and lobby activity are handled under the sdy pools Privacy Policy, so you can see what we collect and why.

Clear data purposesWallet record controlsPhone verification contextIndonesia access terms
sdy pools sdy pools Privacy Policy For You
HELP WITH YOUR DATA

Where To Ask About Privacy Policy

A clear support route matters when your account details or wallet record needs attention.

Account privacy request Use the support path inside your account when you want to ask about personal…
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, describe the date and…
Policy access path When you cannot reach the policy page or need help understanding a data response…
DATA HANDLING DETAILS

What Our Privacy Process Covers

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

Account details

We may handle the name, contact detail and phone number you submit during account opening.

Cookies and sessions

Cookies can keep your session state and remember choices that help the Privacy Policy page or account area load as…

Device security

A device signal may be associated with an account access event to help us investigate an unfamiliar login.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in account records when you check a deposit…

Retention choices

We retain account, security and payment records for as long as the stated purpose or a valid operational need requires.

Change requests

To request access, correction or another change, contact us through the account support route and identify the record concerned.

Privacy Policy Questions About sdy pools

These Privacy Policy answers focus on the account, device and wallet questions you may search before opening an account. We keep the wording tied to real steps, including phone verification, DANA and QRIS records, browser cookies and the support route. If your situation is different, contact us from the account area with only the details needed to identify the request.

The sdy pools Privacy Policy covers account details, phone verification, device and session signals, cookies, lobby activity and payment references. It also explains retention, account security, your access or correction requests, and how to contact us when a record connected with DANA or QRIS needs checking.

Phone verification connects an account access step with the contact detail you supplied. We use it as part of account security and may keep the related status in the account record. If your number changes or the status looks wrong, use the support route to request a check.

Yes. The Privacy Policy covers references and status details created when your account uses DANA or QRIS, along with OVO, GoPay, bank transfer or a virtual account. We use those references to reconcile account activity, and you should never send a wallet PIN for a policy request.

Use the support link inside your account and ask for access to a particular category, such as contact details, device records or payment references. Include a safe account identifier and explain the request. Where local law permits, we will confirm the process and any relevant limits.

Cookies can retain session state and selected browser choices, which may reduce repeated steps when you return to the account area. Clearing cookies can sign you out or remove those choices. The Privacy Policy explains their purpose, and support can help if access changes afterward.

You can ask us to correct an inaccurate account detail through the account support path. Name the field, such as a phone number or contact detail, and provide a safe way to identify the account. We may confirm ownership before applying the change or explaining why it cannot be made.

Yes, the response to an access, correction or deletion request depends on local law. Where local law permits, we will assess the request against the relevant record purpose and retention need. We will explain the outcome through the support path without asking for unnecessary wallet credentials.