Reference

Open win11 Privacy Policy Clearly

Our Privacy Policy explains what account, device and wallet details we use when you open win11 on mobile or desktop.

Account dataWallet detailsPolicy requests
win11 Open win11 Privacy Policy Clearly
REQUEST HELP DIRECTLY

Open A Privacy Request From Account

A clear contact route helps you ask about your personal data without explaining your concern repeatedly.

Account support path Use the support area connected to your account when you want to ask what data we hold, correct a phone detail or question a login record. We use the account step to match the request with the right profile before discussing personal data.
Wallet status question For a payment-data question, include the rail name such as DANA, OVO, GoPay or QRIS and the transaction reference. We can check the recorded status without asking you to send a wallet PIN, password or full private credential.
Receipt and access help If your account access stalls on a mobile browser, describe the device path and attach only the relevant receipt detail. We use that context to separate a privacy request from a payment-status question and keep the response focused.
DATA HANDLING DETAILS

Explore The Controls Behind Your Policy

We apply the Privacy Policy through practical controls rather than broad promises. Phone verification helps us distinguish the account holder during an access request, while login and device records help us investigate…

Account records

We use your phone number, verification result and account activity to create and protect your profile. When you ask for a copy or correction, we first compare the request with the verified account details so private records are not disclosed to the wrong person.

Device signals

A mobile browser or desktop session may provide device and login signals used to detect access that does not match your usual pattern. These records help us investigate an account question; they are not a request for your device password or wallet PIN.

Cookies and sessions

Necessary cookies keep your signed-in session and account path working as you move between the lobby and support area. Browser settings can block optional cookies, while blocking required session storage may interrupt login or require you to verify access again.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we store the reference, amount status and related account link needed to reconcile a receipt. We do not ask for wallet passwords, card secrets or one-time security codes.

Retention timing

We keep personal records while they serve account security, payment reconciliation, support handling or a legal duty. Once the applicable purpose ends, we delete or anonymise the record through our retention process, subject to any requirement that still applies.

Changes and contact

You can request access, correction, clarification or deletion of eligible personal data through the account support path. Include your linked phone number and request details; we may ask for an account check before responding, and the outcome depends on local law.

Browse Answers About win11 Privacy Policy

These Privacy Policy answers address the searches we expect when you are deciding whether to open an account or checking an existing data record. We keep the route practical: use your verified account details, name the payment rail or device involved and avoid sending passwords or wallet security codes. For Indonesia access, eligibility depends on local law.

The win11 Privacy Policy covers account details, phone verification, login and device signals, cookies, support records and payment references. It explains why we use each category, how long we retain it for operational or legal needs, and how you can request access, correction or eligible removal.

We record the payment rail, transaction reference, account link and status needed to reconcile your activity or answer a receipt question. We do not need your wallet password or PIN. Send a privacy request through account support and include only the relevant reference.

Yes. Use the account support path with the phone number linked to your profile and describe the field that needs correction. We check the request against your verified account before changing a record, and some changes or limits depend on local law.

Yes, necessary cookies or session storage help keep your login and account path active on a mobile browser. You can manage optional browser permissions, but blocking required session data may interrupt access or ask you to complete phone verification again.

Send the request through the support area connected to your account. State that you want a copy of your personal data and provide your linked phone number. We may verify account ownership first, then explain which records can be supplied under the Privacy Policy and local law.

We retain payment references, login events and related account records while they support security, reconciliation, support handling or a legal duty. When the relevant purpose ends, we delete or anonymise them, except where an applicable legal requirement calls for longer retention.

You can ask us to remove eligible personal data through account support, explaining the records involved. We first verify the request and check whether security, payment reconciliation or a legal duty requires retention. The result depends on local law, and we will explain any limit.