Reference

winlive4 Privacy Policy Explained

winlive4 Privacy Policy sets out how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet recordsDevice choicesPolicy access
winlive4 winlive4 Privacy Policy Explained
POLICY HELP PATH

Get Help With Your Privacy Questions

A clear contact route helps when your account record or wallet status needs attention. We keep privacy questions separate from general lobby requests, while still linking the route close to the cashier path. Include your account detail, the relevant date and a receipt reference where available, and we can identify the request without asking you to send a full wallet password.

Team online

Account access

If phone verification blocks account access, contact us through the support route shown beside your account area. We use the details you provide to locate the relevant record and explain the next privacy step.

Wallet status

For a DANA, OVO, GoPay or QRIS status question, send the transaction reference and account identifier, not your wallet password. We can compare the record while limiting the data shared in the request.

Data request

To ask for a copy, correction or removal where applicable, state the request clearly through our privacy contact path. We may ask for account verification before changing information connected with your identity.

HANDLING IN PRACTICE

What We Do With Your Account Data

We apply this policy to the records created when you open an account, complete phone verification, browse from a mobile device or check a wallet status.

Account opening

We collect the details needed to create and maintain your account, including contact data used for phone verification. The Privacy Policy describes the purpose before those details are used for account access.

Phone verification

A phone check helps connect an account request to the person making it. We use verification results for access and account protection, while your Privacy Policy rights still apply to those records.

Device signals

When you open the lobby on a phone, tablet or desktop, technical signals can help us keep sessions working and identify unusual access. We explain the categories rather than hiding them behind general wording.

Cookie choices

Cookies can remember a session and support page settings, including the route from login to the lobby. Your browser controls let you clear or restrict them, although some account functions may then need another login.

Retention periods

We keep account, verification and payment references for the period needed for the stated service, dispute handling or legal duty. When a record is no longer needed, our process removes or separates it.

Change requests

You can ask us to correct inaccurate account data, explain its use or consider a deletion request through the privacy contact route. We check identity first so one person cannot alter another account.

Privacy Policy Questions About winlive4

These answers cover the questions we expect you to ask before opening an account or checking a wallet record. For a case-specific response, use the privacy contact path and include only the details needed to locate your account.

It covers account details, phone verification, device signals, cookies, payment references and support requests. It also explains why we use each category, how long records may remain and how you can contact us.

Our policy concerns transaction references and status needed to match an account action. Do not send a DANA or QRIS password in a support request; we do not need it to investigate a receipt.

OVO and GoPay status can show whether an account action is pending, matched or disputed. We use the reference and related account details for that purpose, not as a reason to request unrelated wallet credentials.

Yes. Send a correction request through the privacy contact route with the account identifier and the inaccurate field. We may verify your identity before changing information, then explain the result through the same route.

Use the privacy contact path and ask for an account data copy. Include enough detail for us to find your record, but avoid sending wallet passwords. We may complete an identity check before releasing account-linked data.

Cookies may keep your session and page choices available when you move from login to the mobile lobby. You can clear or restrict them in your browser settings, though account access may require another login.

You can ask us to consider removal through the privacy contact route. We assess the request against active account needs, dispute handling and legal duties, then explain which records can be removed or retained.