LEGAL REFERENCE

How win live4d Handles Your Account Data

This is our privacy policy — the page that explains what we collect when you open an account with win live4d, why we keep it, and how long...

Plain-language policyIndonesia-focusedAccount data onlyUpdated regularlyContactable team
win live4d How win live4d Handles Your Account Data

Our Data Posture and Your Rights

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP CHANNELS

Reaching Us About Your Data

Privacy Inbox Email our privacy desk directly with the subject...
Live Chat Open the chat bubble inside your account and...
Account Settings Most data actions — updating your phone, changing...
EDITORIAL CLARITY

How We Maintain This Policy

Legal Review

Our policy text is checked by counsel familiar with Indonesia data rules before each revision goes live, so the wording you read reflects the current obligations we operate under, not a template borrowed from elsewhere.

Versioned Edits

Every change to this page carries a date and a short note explaining what moved. You can scroll to the footer of the policy to see the active version and the prior one we replaced.

Data Map

We keep an internal map of where account fields sit, which partner sees what, and how long each record lives. That map is what this public policy summarises in reader-friendly form.

Staff Training

Agents who touch your account complete privacy refreshers before they handle tickets, so the person reading your data request understands the limits of what they can disclose over chat.

Partner Vetting

Payment processors and identity vendors we connect to sign data agreements before integration. We don't share fields with marketing networks that haven't been scoped into this policy.

Breach Protocol

If something goes wrong on our side, we have a written response path — contain, assess, notify affected accounts and the relevant authority within the timelines Indonesia rules require.

Consistency Across Our Policy Pages

Privacy vs Terms
Our terms cover the contract between you and the brand; this privacy page covers the data side. Where they overlap on account closure, the wording matches deliberately so neither contradicts the other.
Privacy vs Cookies
Cookies sit in their own notice with granular toggles. This page references the categories at a high level and points to the cookie panel for the actual on/off controls.
Privacy vs KYC
Identity checks are described here in summary form. The KYC notice goes deeper on document handling, retention of scans, and the verification partner we route uploads to.
Privacy vs Payments
Payment partner data sharing is named on this page; the payments help section explains the user-facing flow without repeating the legal basis we rely on for processing.
Privacy vs Marketing
Marketing consent rules live here so you can withdraw cleanly. The promo board itself doesn't restate the policy — it links back to this page for the consent mechanics.
Privacy vs Security
Security controls are summarised in the trust block above and detailed on the security page. Both reference the same encryption and access-control standards we apply.
Privacy vs Contact
General contact channels accept any query. The privacy inbox is reserved for data requests so the right reviewer picks them up rather than a frontline agent.

What This Policy Page Includes

Plain Sections

We've broken the policy into short blocks with clear headers so you can jump to the part you need — collection, sharing, retention, rights — without reading the entire page end to end.

Revision Date

A visible revision date sits at the top and bottom, so you always know whether the wording in front of you is current or whether you're looking at an archived copy from a prior version.

Rights Summary

Your access, correction, deletion and portability rights appear together in one block, written so you can act on them rather than having to translate legal phrasing into a support ticket.

Contact Block

Direct contact details for the privacy desk are surfaced inside the page itself, not buried in a separate footer link, so a request takes seconds to send when you need one filed.

Scope Notes

Each clause notes whether it applies to all accounts or only to supported regions in Indonesia, so you're not guessing whether a paragraph is relevant to your situation.

Change Log

A short change log records meaningful edits to the policy. If a clause moved or a partner was added, you can read why before deciding whether to continue with the account.

Privacy Questions We Hear Most

We collect the signup fields — name, contact, birth date — plus the wallet handle for DANA, OVO, GoPay or QRIS top-ups, and session data linked to lobby activity needed to keep the account secure.

Yes. Send a deletion request to the privacy inbox and we'll close the account, purge marketing fields immediately, and remove transactional records once the retention window required by Indonesia financial rules has fully elapsed.

Only the partners named in the policy: payment processors handling your wallet top-ups, identity vendors verifying signups, and infrastructure providers hosting the platform. We don't sell account data to outside marketing networks.

Open your profile, find the communications panel, and toggle the channels off. The change applies on our next send cycle. Lobby access and account standing are not affected by withdrawing marketing consent.

Active accounts retain their full record. Closed accounts keep transactional data for the period Indonesia financial regulations require, after which the residual fields are purged from our live systems on the schedule documented above.

Material changes trigger a notice inside your account and an updated revision date on this page. Minor edits are logged in the change block at the foot of the policy without a separate alert.

Start with our privacy inbox so we can resolve it directly. If our response doesn't satisfy you, the policy names the Indonesia authority you can escalate to, along with the reference details you'll need.