Reference

Privacy Policy For Your siko wd Account

Our Privacy Policy explains what we collect when you open a siko wd account, sign in on mobile or desktop, browse Blackjack and Fish Hunter, or select DANA…

Account dataWallet recordsCookie choicesRequest access
siko wd Privacy Policy For Your siko wd Account
CONTACT ROUTES

Get Privacy Policy Help Directly

A clear contact route matters when your Privacy Policy question concerns a phone number, device record or wallet receipt. We ask you to use the support path connected to your siko wd account so we can match the request safely without exposing account data in an open message. Include the email or phone detail tied to your account, the subject of your request and any relevant receipt reference. We may ask for a verification step before discussing personal records.

Team online

Account support path

Open the account support route after signing in and choose a privacy request. We use the account session and phone verification status to reduce mistaken disclosures, especially when your question concerns a DANA, OVO, GoPay or QRIS record.

Payment record query

For a wallet or bank transfer question, include the payment rail, date and reference shown on your receipt. Our support team can locate the relevant account record without asking you to send a full wallet password or private sign-in code.

Access or correction request

Ask us to see, correct or clarify eligible personal data through the same support route. Tell us whether the request concerns your profile, device history, cookies or account activity, and we will use reasonable checks before replying.

DATA PRACTICES

How We Apply This Policy

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

Account and phone data

When you open an account, we collect the contact details and phone verification result needed to identify that account. If you ask for a correction, we compare the request with the existing account record before changing the stored detail.

Device and sign-in signals

Your mobile browser or desktop session can generate device, browser and connection signals. We use them to recognise a returning sign-in, investigate unusual access and protect account data; they are not treated as a replacement for your phone verification.

Cookies and preferences

Cookies can remember a session choice, language setting or policy preference on the device you use. You can adjust cookie controls in your browser, although restricting essential cookies may require another sign-in before account pages open.

Wallet and receipt records

Selecting DANA, OVO, GoPay, QRIS, bank transfer or a virtual account can create a payment reference linked to your account. We use that reference to check status and receipts, while wallet credentials remain outside our requested support details.

Retention and deletion

We retain records for the period needed for account operation, security checks, legal duties or an unresolved payment query. You can ask whether a record remains stored; deletion may be limited where keeping it is required for one of those purposes.

Policy change requests

If a detail is inaccurate or your circumstances change, contact us through the account support path and describe the requested update. We record the request, verify the account holder and reply about the action available under local requirements.

Privacy Policy Answers Before Account Access

These Privacy Policy answers focus on the questions you may have before opening an account or checking an existing record. We explain the practical path for data access, correction, cookies, payment references and account closure without turning the policy into a general lobby description. If your question is not listed, use the support path connected to your account and mention the exact data category involved.

The siko wd Privacy Policy covers account creation, phone verification, sign-in activity, device and browser signals, cookies, support messages, lobby selections such as Blackjack or football pages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Sign in through the account path, open support and ask for a data access request. State the phone or email connected to your account and identify the records you want, such as device history, cookie preferences or a QRIS receipt. We verify ownership before disclosure.

Yes. The Privacy Policy explains that mobile and desktop sessions may produce browser, device and connection signals. We use these signals for session recognition and account security, not as a substitute for phone verification. Browser controls can limit non-essential cookie storage on your device.

A DANA or QRIS selection can create a reference linked to your account, including status and receipt details needed for support. We use that reference to check a payment query. Do not send a wallet password or private sign-in code when asking us to locate a record.

You can request a correction through the signed-in support route. Describe the incorrect field, such as a phone detail or account contact, and provide the updated value. We compare the request with your verified account before applying an eligible change or explaining why a record must remain.

We keep personal records for the time needed to operate the account, investigate security activity, meet applicable legal duties or resolve a payment dispute. The exact period depends on the record type. You can ask support whether a particular account or receipt record is still retained.

You may request account closure or deletion of eligible data through support. We first verify the request and check whether a record is still needed for legal, security or payment-dispute reasons. Access depends on local law, so our reply will identify any required retention.