Reference

win idn Privacy Policy For Your Account Data

Your account, wallet and device data receive clear handling rules in the win idn Privacy Policy.

Account dataWallet recordsCookie choicesContact steps
win idn win idn Privacy Policy For Your Account Data
CONTACT PATHS

Get Clear Help With Privacy Requests

Privacy questions should reach the team through a traceable account path, so we can match your request to the correct records without exposing them to another person. Start by signing in, opening the support route shown in your account, and naming the request you need. For a wallet question, include the DANA, OVO, GoPay or QRIS receipt reference, but never send a wallet password or full login credential. Our team can explain the next step for access, correction or removal requests.

Team online

Account support route

Sign in and use the contact path displayed in your account. Tell us whether you want a copy of personal data, a correction, a privacy explanation or a request to close the account.

Payment record check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the transaction reference and date. We use those details to locate the correct entry without asking for your wallet password.

Access concern

If a phone verification or login event looks unfamiliar, use the account support path immediately. We may ask for account details needed to confirm identity before discussing private records.

DATA PRACTICE

Know What Happens To Your Personal Records

We keep this policy practical by connecting each data use to an account action you can recognise. Phone verification supports account access, payment references help reconcile wallet status, and device signals help…

Collection at account opening

We collect the details you enter for an account, including contact data and phone verification status. Required fields help us identify your account before we discuss private records through support.

Wallet and cashier records

A DANA, OVO, GoPay or QRIS reference lets us match a payment event to your account. Bank transfer and virtual account records may carry the same reconciliation details for status checks.

Cookies on your device

Cookies may keep a session active, remember a selected setting or show us that a page has loaded correctly. You can manage browser cookie controls, though some account functions may then need another sign-in.

Account security signals

We may record browser type, device details, sign-in time and security events. These signals help us identify unusual access without treating a device signal alone as proof of identity.

Retention and removal

We retain personal records only while they serve the stated account, payment, security or legal purpose. When you ask about removal, we explain what can be deleted and what must remain for a defined duty.

Policy changes

If this Privacy Policy changes, we will place the revised wording on this page and show the effective date. Check the page before using a newly added account or wallet function.

Privacy Policy Answers For win idn Accounts

These Privacy Policy answers cover the questions we expect you to ask before creating an account or sending a wallet payment. They explain the records tied to phone verification, mobile access and local payment references, plus the steps for requesting access or correction. If your question is not listed, use the support path inside your account and provide only the details needed to locate your record.

The win idn Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references, security events, retention and privacy requests. It explains how we use these records when you access the service from Indonesia where local law permits.

We may collect the contact details you enter, login credentials in protected form, phone verification status and account activity needed to provide access. Device and browser signals may also be recorded to identify unusual sign-in behaviour and protect your account.

Yes. The policy covers payment references, status, amount and account identifiers connected with DANA, OVO, GoPay and QRIS. We may also handle matching details for bank transfer and virtual account payments, but we do not need your wallet password.

Device and browser details help us understand sign-in patterns, detect unusual access and keep a mobile session working correctly. These signals can include device type, browser details and access time; they are considered alongside account checks rather than used alone.

Sign in, open the support contact path shown in your account and state whether you want access to your records or a correction. Include the relevant phone number or payment reference only when needed, and avoid sending passwords or wallet credentials.

We keep records while they are needed for the stated account, payment, security or legal purpose. If you ask about deletion, we will explain which records can be removed and which must remain for a defined legal or reconciliation duty.

Yes. Ask through the account support route if you need details about cookies connected with your session or settings. You can also adjust cookie controls in your mobile browser, although changing them may require another sign-in or affect page functions.