Privacy policy

Effective 17 October 2026

This page explains what data WynnChaYuan handles across three things: the WynnChaYuan Minecraft mod, this website (wynnchayuan.com) and the Discord bot. WynnChaYuan is an unofficial fan project maintained by the WynnChaYuan team (contact: LyuChaCha).

What the mod sends

Capes and the leaf before your name need a connection to wynnchayuan.com. The mod checks in once when you join Wynncraft and sends:

• Your Minecraft UUID and your public profile as signed by Mojang (name and skin)
• A public key and signature proving the account is yours (the key pair Mojang issues to every premium account)
• Whether to wear your cape, and your badge settings (coloured leaf, which roles to show)
• When you upload a cape, the image you chose

Your private key and login credentials never leave the game. The mod does not send the world you are in, chat, or any other game content. Checking in has no switch: it happens whenever the mod is installed and you join Wynncraft. To hide your cape from others, turn off "Wear my cape" under F6 → "Badge & cape".

The mod never uploads in-game text on its own. Files made by "Export untranslated strings" stay on your computer; sending them to us is up to you. "Update now" only downloads a new version from GitHub Releases when you press it.

Website account

Website accounts sign in with Discord using only the identify scope: we keep your Discord user ID and display name. We do not read your email or your server list, and the access token Discord gives us is thrown away after use. Once you link your game account with /wcy link, the account also stores your game UUID, name and the time you linked.

Capes

• The uploaded image, its format and size, when it was uploaded, and who uploaded it (moderators need to know)
• The public gallery shows only the image and a code hashed from the UUID, never the UUID or name; only developers can see who uploaded which cape
• Your history of worn capes and your starred favourites are visible only to you
• Capes set to private stay out of the gallery; capes awaiting review are visible only to you and moderators until approved
• To stop bursts of uploads, the times of your recent uploads are kept for at most thirteen hours
• If you are banned or put on the review list, we store your UUID, name, the time and the moderator involved

Translate

When you suggest a translation, vote, or open a term poll on /translate, we store your display name and ID, the time, and what you wrote. Suggestions and votes are visible to others. Accepted translations are written to the public GitHub repository (licensed CC BY-NC-SA 4.0) and stay in its history once merged.

Feedback

When you send feedback on /feedback or with the bot’s /feedback command, we store your Discord user ID and display name, the category, what you wrote (including “where” and the language), the time and whether it came from the website or the bot; to stop flooding we also briefly keep the times of what you sent in the last hour. Feedback is only visible to developers and moderators. Feedback in the “Translation suggestion” category automatically opens an issue in the public GitHub repository containing what you wrote and your Discord display name (not your user ID); anyone can see it, and it stays on GitHub until a maintainer removes it.

Discord bot

The bot only receives the slash commands you use: the command and its options, your Discord user ID, the server and channel IDs and your client language (fields Discord always sends). It cannot read any chat messages and, apart from feedback sent with /feedback (see “Feedback” above), does not keep what you sent.

Cookies and browser storage

• lang: remembers the website language you chose
• wcy_oauth, wcy_intent: protect the Discord sign-in and only matter for the few minutes it takes
• Browser localStorage: your sign-in pass (valid for one day) and small display preferences

There are no ads and no analytics or tracking cookies.

What we do not record

Our code does not record IP addresses, the world you are in, chat or any other game content.

Third-party services

• Cloudflare: the website and its data run on Cloudflare Workers and KV. Cloudflare processes connection data (including IP addresses) for security and network operation under its own privacy policy
• Discord: sign-in and the bot
• GitHub: source code, translations, release downloads, pull requests from Translate and issues from translation suggestions
• minotar.net: player heads on the website are loaded by your browser directly from it; for the Discord bot's cape preview, the website fetches that player's skin from it
• jsDelivr: the 3D cape viewer is loaded by your browser directly from it

We do not sell or rent any data, and we do not use it for advertising.

How long we keep it

• Check-in list: you drop off after fourteen days without checking in
• Capes nobody wears: kept for seven days, then deleted
• Passes expire after seven days (game) or one day (website)
• Feedback: deleted automatically 180 days after it is marked handled; open feedback stays until it is handled or deleted; the send times kept for rate limiting disappear after an hour
• Website accounts, ban and review records: until you ask for deletion or a moderator lifts them

Your choices

You can remove your cape yourself on the account page. To stop checking in, remove the mod. To see or delete your account and related data, contact LyuChaCha on Discord or open a GitHub issue (please do not post private details in a public issue). We will handle requests within a reasonable time.

Age

You need to meet the age requirements of Minecraft and Discord to use these services.

Changes

If this policy changes, we update this page and the date above. Significant changes are announced on Discord or in the changelog.