Privacy Policy

Scope

This Privacy Policy explains data handling for the exact MVP pages at Home, Playstyle orientation, and Personal checklist. This is an independent, unofficial fan companion for Where Winds Meet. It is not affiliated with, endorsed by, or sponsored by NetEase Games or the game’s rights holders. Game names, trademarks, artwork, and other intellectual property belong to their respective owners.

This draft describes only the verified browser-local checklist behavior. It must be reviewed before publication if implementation adds any other collection, storage, transfer, analytics, cookies, or third-party processing.

Browser-local checklist data

On /tools/checklist, you may create user-authored checklist entries. In the verified current scope, the entry text and its marked or unmarked state are stored in localStorage in the same browser and device.

You can add, mark or unmark, edit, delete individual entries, and clear the checklist. Entries are not uploaded to a server and are not synchronized across devices.

Browser-local entries may remain in the same browser and device until you delete or clear them, clear the browser’s site data, use a browser mode that discards storage, or the browser or device otherwise removes or loses the data. The operator cannot retrieve, inspect, synchronize, or restore data that exists only in local browser storage. Changing devices, browsers, or browser profiles, or clearing site data, may permanently remove access to those entries.

MVP data boundary

In the exact verified MVP scope, the service has no accounts or login; no payment, subscription, or refund transaction; no file upload; no public user submission; no AI prompt processing; no advertising or affiliate tracking; and no cross-device synchronization feature. User-authored checklist entries remain local to the browser as described above.

Cookies, analytics, and consent

The verified current scope does not establish the use of non-essential cookies or tracking. This draft does not claim that analytics, advertising, affiliate measurement, pixels, fingerprinting, or comparable tracking is active. If final runtime evidence establishes any such behavior, publication must stop pending fresh compliance review of its purposes, providers, data categories, retention, user choices, consent requirements, and withdrawal controls.

Third parties, hosting, logs, and communications

The actual hosting and infrastructure providers, automatic request-log behavior, security logging, data locations or transfers, retention logic, deletion controls, and any active third-party services remain unresolved. No provider, retention period, or transfer practice is asserted in this draft.

An operator-controlled contact channel has not been verified. This draft therefore provides no mailbox or contact endpoint.

Retention and user choices

For browser-local checklist entries, retention is controlled by the browser, device, and user controls described above. The operator cannot delete or restore local-only entries remotely. Any runtime logs, messages, or other data discovered during publication verification require a fact-specific retention statement and applicable user instructions before publication.

Security and children

Browser-local storage is not a secure vault. Do not place passwords, payment information, sensitive personal data, or confidential information in checklist entries. No method of storage is guaranteed to be completely secure.

The intended audience, age treatment, and any jurisdiction-specific children’s privacy wording remain unresolved and require publication-time legal review.

Changes and contact

This draft may be updated when the service or applicable requirements change. Operator identity, a tested contact channel, and an effective date remain unresolved. A future approved version must show verified facts and preserve an accessible current version.