Reference

windlive4d Privacy Policy for Indonesian Accounts

Our Privacy Policy explains what windlive4d collects when you open an account, use DANA or QRIS, and access the lobby from a phone or desktop.

Clear data purposesWallet records explainedCookie choicesRequest access or changes
windlive4d windlive4d Privacy Policy for Indonesian Accounts
CONTACT PATHS

Ask About Your Account Data

A direct privacy request helps us find the right account record without exposing details to the wrong person.

Access request Ask for the personal data connected with your account, including phone verification events, device sign-ins and wallet references. We will first confirm that the request comes from you.
Correction request If your phone detail or account record is inaccurate, send the specific field and supporting context through the account contact path. We can review the entry before making a change.
Wallet privacy help For a DANA, OVO, GoPay or QRIS privacy question, include the date and receipt reference rather than a PIN. This lets our team trace the record while limiting sensitive details.
DATA PRACTICES

Cookies, Security and Account Records

We keep this policy practical: each record has a purpose connected to account access, payment matching, security or support.

Account details

When you open an account, we collect the details needed for registration and phone verification. These records help us distinguish your account from another account and route privacy requests correctly.

Device signals

Sign-in time, browser type and device signals may be recorded when you move from a phone login to the lobby. We use them to identify unusual access and protect your account.

Cookie controls

Cookies can remember a session path and help security checks work across pages. You can manage cookies in your browser, although removing them may require another sign-in or phone check.

Payment references

We retain transaction references, status messages and receipt details from DANA, OVO, GoPay, QRIS and bank rails. We do not request wallet passwords, card PINs or banking PINs.

Retention requests

Records remain available only for the period needed for account security, payment matching, support handling or a legal requirement. Ask through the contact path for the retention period applying to your record.

Security contact

If you suspect someone accessed your account, contact us with the registered phone detail and approximate sign-in time. We may pause discussion of sensitive records until phone verification is complete.

Privacy Policy Questions From Indonesian Accounts

These Privacy Policy answers cover the questions we hear before account creation and during wallet use. They explain what you can request, how we check identity and which records may appear after a phone sign-in or payment status update. If your question is not listed, use the account contact path and describe the specific record you want us to locate.

It covers account registration, phone verification, device signals, cookies, lobby access records, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to create and identify your account, complete phone verification and protect privacy requests. It also helps us separate your account record from another account with similar details.

Yes. The Privacy Policy covers receipt references, status messages and matching details connected with DANA and QRIS. We do not need your wallet password, security code or banking PIN to check a record.

You can request a copy through the account contact path. Include your registered phone number and the record type you want checked. We may complete phone verification before releasing account-linked data.

Send the incorrect field, the correct replacement and context through the account contact path. We review the request against your account and may ask for phone verification before changing the record.

Mention cookies, browser details or a sign-in event in your privacy request. We can explain the device signal connected with that event, while your browser settings let you remove or limit cookies.

You can ask us to assess deletion through the account contact path. We review the request against security, payment matching and legal record needs, and access depends on local law before action is taken.