Reference

idolawin Privacy Policy Explained

idolawin Privacy Policy explains how we handle the details connected with your account, device, support requests and wallet activity.

Account clarityWallet recordsDevice choicesPolicy requests
idolawin idolawin Privacy Policy Explained
CONTACT YOUR WAY

Get Privacy Policy Help Directly

A clear contact route matters when your account record, wallet receipt or device setting needs attention.

Account request Use the account support path when you want to ask what personal details we hold or why Account Verification is needed. Include your registered contact detail so we can match the request safely before discussing account records.
Wallet record For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference and approximate time rather than a password or full wallet credential. We can check the account-side status while keeping sensitive payment details out of the message.
Privacy change If you want a correction, access request or deletion review, state the exact change in your support message. We may ask for an account check first, then confirm whether local rules require us to retain part of the record.
DATA HANDLING

What Our Privacy Process Covers

We keep the Privacy Policy practical by connecting each data use with an account task you can recognise.

Account details

We may handle the contact details you enter when opening an account and the verification material required for Account Verification. This lets us connect a request to the correct account instead of exposing details to someone using an unrelated email or phone number.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in account records when you ask us to check a payment status. We use the reference for matching and support work, not as a reason to request your wallet password.

Cookies

Cookies and similar device storage may remember a language choice, sign-in state or page setting. You can manage browser permissions on your phone or computer, though switching them off may require you to repeat an account step.

Account protection

Sign-in, device and verification signals can help us identify unusual access and protect your account. If a mobile browser changes or a login stalls, support may ask for limited details about the device path without asking for your password.

Retention choices

We retain records for the operational purpose that created them or for a legal requirement that applies to the account. When you ask for deletion, we check whether a payment, verification or dispute record must remain before confirming what can be removed.

Your request

You can ask for access, correction or a restriction on a particular use through support. Tell us which record concerns you, such as a QRIS receipt or device entry, and we will explain the identity check and the next response step.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or sending a support request. We keep each answer tied to an identifiable action, such as Account Verification, a mobile sign-in, a QRIS receipt check or a request to correct your details. Where a legal requirement affects access or retention, we explain that point through the support path.

The idolawin Privacy Policy covers account details, Account Verification records, sign-in activity, device settings, cookies, support messages and payment references. This includes records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks when you ask us to confirm an account-side status.

We use Account Verification details to connect the account with the person making the request and to protect account access. The check may be relevant when you open an account, ask to change personal data or request help with a wallet record. Access depends on local law.

Send a support request that names the account contact detail and describes the records you want to access, such as sign-in activity or a QRIS receipt reference. We check identity before sharing account data, then explain the response process and any retention rule that applies.

Yes, you can ask us to correct an inaccurate contact detail or account record through support. Describe the incorrect entry and the replacement clearly. We may ask for Account Verification before making the change, particularly when the request affects sign-in, wallet matching or account ownership.

The Privacy Policy allows cookies or similar storage to remember settings, maintain a sign-in step and help diagnose a mobile page. You can adjust permissions in your phone browser. If you block required storage, you may need to repeat login or account verification steps.

We keep each record for the operational reason it serves or for a legal requirement that applies to it. Payment references, Account Verification details and support messages may therefore have different retention periods. Ask support about a specific DANA, QRIS or account record for a tailored response.

Use our account support path and write Privacy Policy request in the message subject or opening line. Include your registered contact detail, the requested action and any safe reference number. Never include a password or full wallet credential; support will explain the identity check needed.