Lion Madness is a small, independently-run Minecraft server. This policy explains what we do with data when you play on the Server, visit this website, or take part in our Discord community. It also sets out where our responsibility ends and a platform's own begins.
Three people help run Lion Madness, but the server was founded by, and is principally owned and operated by, one of them: Filip Kasprzak, based in the United Kingdom. That person is responsible for the processing described below. Where Discord, Vercel, Mojang/Microsoft, or another provider processes data under their own policies, we say so and link to them.
What We Process
On the Server
When you connect, Minecraft authentication (Mojang/Microsoft) shares your account's username and UUID with us, the way it does with every Minecraft server. Depending on how you play, the Server and its plugins may also hold your connection times and playtime, your IP address where the server or proxy exposes it, in-game chat and commands, gameplay records such as claims, towns, and economy activity, and moderation records such as warnings, mutes, bans, anti-cheat events, and the evidence attached to them. Server software also writes ordinary technical and error logs.
If you choose to link your Minecraft account to a Discord account, we store that link, which pairs your Minecraft UUID with your Discord user ID. Linking is optional and changes how your bridged chat is shown and what account-linked features you get; it is not what turns chat bridging on. See Minecraft–Discord chat bridge below for how ordinary chat is handled with and without a link. If your linked account is banned from the Server, that link is also used to ban the same account from our Discord.
Minecraft–Discord chat bridge
The server uses DiscordSRV to connect designated Minecraft chat channels with designated Discord channels. An ordinary message sent in one of those channels may be transmitted to the other so players and Discord members can talk across both. This applies to linked and unlinked Minecraft players alike; being unlinked does not keep your ordinary chat out of Discord.
For an outbound message, the bridge sends the message text and a display name. If your account isn't linked, or is linked but our configuration shows Minecraft identities, that name is your Minecraft username or display name. If your account is linked and our configuration is set to show the linked Discord identity instead, it's your Discord display name. Discord also receives the ordinary technical information needed to deliver and display the message: the destination channel, message ID, timestamp, webhook metadata, and any attachment or rich-content data a supported feature generates.
We don't intentionally include your Minecraft UUID, IP address, password, private messages, coordinates, or other unrelated server data in an ordinary chat relay. One supported command is an exception by design: it renders your held item or your inventory as an image and posts it into the bridged Discord channel, and that image is only sent when you choose to run it. If you type identifying information into the message itself, that's still sent like any other chat content.
Once a message reaches Discord it's a message on Discord: Discord may process, store, moderate, or delete it under Discord's own policies and the rules of our Discord server, including on infrastructure outside the UK and EEA. We have not put our own data processing agreements or standard contractual clauses in place for this; as a small, volunteer-run operator we rely on Discord's own safeguards as a global platform rather than negotiating bespoke terms.
In the other direction, messages from the bridged Discord channel may be shown to online Minecraft players. An unlinked player may see a short notice that someone is chatting in Discord, rather than the sender's full Discord identity, depending on the server's routing configuration; use /linkinfo in-game to learn how linking changes what you see and send. The /discordnotice on|off|status command controls only that in-game notice for unlinked players — it does not stop your own Minecraft-to-Discord chat from being relayed.
This is separate from the staff /announce command, which is one-way from Discord into Minecraft and never sends a player's own chat, identity, or activity out to Discord.
A bridged message's Discord side stays on Discord, under Discord's own retention; we do not export or archive Discord's message history ourselves. The Minecraft-side server console and chat logs that also capture bridged chat are cleared periodically, on no fixed schedule, typically every few weeks to a month. Staff with moderation permissions can review a bridged conversation the same way any Discord moderator can on the Discord side, and through the Minecraft server logs while they still exist. If you ask us to delete a specific bridged message, we will delete our own copy where one still exists. We cannot delete Discord's copy of it for you; that has to go through Discord directly. Don't send passwords, payment information, government identifiers, private personal information, or someone else's confidential information through bridged chat. We may moderate or remove content under the Server Rules and Discord's rules.
On this website
There are no accounts, logins, or forms on this site, so we do not ask you for personal information. Two things still happen automatically:
Hosting. The site is hosted on Vercel, and serving a page necessarily involves request data: IP address, approximate location derived from it, browser and device information, referrer, timestamps, and error and security logs. Vercel describes this in its Privacy Notice. We do not use hosting logs to build a profile of you.
Analytics. We use Vercel Web Analytics for aggregate page-view and performance measurement. It sets no third-party cookie. Per Vercel's documentation, the data points can include timestamp, URL and dynamic path, referrer, filtered query parameters, approximate geolocation, operating system, browser, device type, and script version, and visitors are distinguished by a hash derived from the request which is discarded after 24 hours. We do not deliberately send names, email addresses, order references, or chat content into analytics URLs or events, and we re-check that when the site changes. We are not claiming this data could never be personal. It is aggregate by design, and we do not try to re-identify anyone from it. See our Cookie Policy.
On Discord
Discord operates Discord under its own Terms and Privacy Policy. We do not control Discord's platform-wide collection, retention, account systems, or enforcement, and we cannot answer for it.
Separately, we do have our own responsibilities as a server operator. Our staff can see what Discord shows moderators, and we process what you send us through reports, appeals, and support tickets. We do not export or archive the Discord's message history, and we do not treat ordinary messages as material we may republish. See Your Content in the Terms.
Our Discord bot
We run our own bot in the Lion Madness Discord. It handles the following:
- It stores Discord user IDs in its own database where a feature needs them: who may use which command, business registry entries and their listed owners and staff, and who owns a temporary voice channel.
- In staff-designated channels it keeps a short-lived copy of recent messages, including content, author, and attachment names. It is held in memory only, so that if a message is deleted the bot can post an alert with a short preview to a staff channel. This is an anti-tampering feature for moderation. Nothing is written to disk, the buffer is capped, and it is lost whenever the bot restarts.
- Some commands send what you give them to third parties. If you use the translation, lookup, or image-analysis commands, the text or image you supply goes to the relevant provider under that provider's own terms: Google or DeepL for translation, Google's Gemini API for image analysis, and Wikipedia, DuckDuckGo, MDN, or a dictionary service for lookups. Do not put anything into those commands that you would not want a third-party service to receive.
The bot does not scrape or mine the Discord, does not sell or license Discord data, does not use it to contact you off Discord, and does not use message content to train AI models. If something the bot does looks wrong, report it using the Reporting & Complaints page.
Purchases
The store is not open, so today we take no payments and hold no payment or billing data. We never receive card details in any case, as that stays with a payment provider. Before the store opens we will update this policy to name the provider and say exactly what it passes back to us.
Why We Process It
To run the Server and website, keep them secure, moderate the community, investigate cheating and abuse, answer reports and appeals, and publish community content where the creator has actually given us permission. We do not sell your data and we do not run advertising.
Where data-protection law such as the GDPR or UK GDPR applies to you, the legal basis depends on the activity. Running the Server and delivering what you asked for is normally contract or steps taken at your request. Moderation, anti-cheat, and security rest on our legitimate interest in keeping the community safe. Featuring your content rests on the permission you give, and some records are kept because the law requires it.
Who We Share It With
Only the providers needed to run Lion Madness: our server host and infrastructure provider, Vercel for the website and analytics, Mojang/Microsoft for Minecraft authentication, Discord for anything that happens on Discord, the lookup and translation services named above when you use the commands that call them, and appeal.gg if you use it to appeal a Discord ban, which then holds what you submitted under its own privacy policy. We may also disclose information where the law requires it, or where it is necessary to protect people, prevent abuse, or deal with a legal claim.
Some of those providers operate outside your country, including outside the UK and EEA. Discord, Vercel, Google, and Mojang/Microsoft are the most notable examples, and they are US-based, so data may be processed there. We have not negotiated our own data processing agreements or standard contractual clauses with these providers; we rely on each provider's own published safeguards for their global operations, consistent with running Lion Madness as a small, volunteer operation.
How Long We Keep It
We keep each kind of record only as long as it is doing a job, and longer only where safety, a legal claim, or a legal obligation requires it.
| Record | How long |
|---|---|
| Connection, technical, and error logs | Kept for routine operations and security, then rotated out. |
| In-game chat and ordinary moderation logs | Kept while useful for moderation, then purged, unless tied to an active ban, an open appeal, a safety investigation, or a legal claim. |
| Active bans and appeal records | Kept while the ban is in force and for as long as the decision may be revisited. |
| Minecraft-to-Discord account links | Kept while the link is in place. Unlinking removes it. |
| Minecraft–Discord bridged chat | Discord side: kept under Discord's own retention. Minecraft-side server logs: cleared periodically, on no fixed schedule, typically every few weeks to a month. |
| Deleted-message alerts in staff channels | The in-memory buffer clears on restart. The alert posted to the staff channel stays until staff clear it. |
| Bot database records (court cases, businesses, voice channels) | Kept while the case, listing, or channel exists, plus its archived history. |
| Content-submission permissions | Kept while the content is published and afterwards as a record of consent. |
| Website analytics | Held by Vercel on its own schedule, described in its analytics documentation. |
Your Rights
Depending on where you live, you may have the right to ask for a copy of the personal data we hold about you, to have it corrected, to have it deleted, to restrict or object to how we use it, to receive it in a portable form, and to withdraw permission you gave us. You may also have the right to complain to your national data protection authority.
To make a request, email lionmadnessminecraft@gmail.com with your Minecraft username or Discord handle. We may need to ask for enough information to be confident the request is really yours. We will respond within the time the applicable law allows, and if an exception or someone else's rights limit what we can do, we will explain why.
These are separate requests, and you can make one without the other. Asking us to take a repost down is not the same as asking us to delete every server record. We may need to keep limited records tied to an active ban, a safety investigation, or a legal obligation even after a deletion request.
Younger Players
Younger players are welcome on the Minecraft server, and we do not run an age check, so we may well have players under 13. We hold the same limited information about them as about anyone else: Minecraft username and UUID, playtime, in-game chat, and any moderation records. Under some laws, including the US COPPA rules, a username or a persistent identifier such as a UUID counts as personal information about a child, so we do not treat any of it as automatically harmless.
Under-13s cannot join our Discord, because Discord requires its own users to be at least 13. That doesn't stop their in-game chat from reaching Discord: the chat bridge relays ordinary Minecraft chat in bridged channels by default, whether or not the sending player is linked to a Discord account, so an under-13 player's messages can be delivered into our Discord channel even though that player could never join Discord themselves and takes no separate action to enable it. We do not restrict bridged channels because of this. This section is the notice: bridged chat is always on for every player regardless of age, and this disclosure is the safeguard we rely on rather than a separate in-game notice.
Parents and guardians can email lionmadnessminecraft@gmail.com to ask what we hold about their child, or to have it deleted. We do not ask a child for personal details beyond what the Server needs in order to run.
We knowingly allow under-13 players, relay their ordinary chat to Discord by default, and do not collect verified parental consent. Our position is that we hold only the same minimal gameplay data we hold about any player: Minecraft username and UUID, playtime, in-game chat, and moderation records. We do not run age verification or ask a child for anything beyond what the Server needs to function, and we rely on this policy's disclosure plus the parent/guardian contact route above rather than a formal consent mechanism.
Security
We limit who on the staff team can reach moderation data, rely on our providers' security controls, and keep records only as long as we need them. No online service can promise perfect security.
If there is an incident affecting your data, we will give notice where the law requires it, using a contact route that actually reaches you. We will announce it on this website and in Discord. We will not rely on Discord alone, because someone who has left, been banned, or never joined still needs to hear about it.
Changes to This Policy
This page is the authoritative home for the current version, and the date at the top reflects it. If the policy changes in a meaningful way we will update it here and announce it in Discord. We will review it whenever we add a plugin, a bot feature, an analytics event, a payment provider, or anything else that changes what we handle.
Who We Are & How to Reach Us
Lion Madness has three staff who help run the server and community day to day, but it was founded by, and is principally owned and operated by, one of them: Filip Kasprzak, based in the United Kingdom. That person is the operator responsible for what is described in these policies. In these policies, "Lion Madness," "we," "us," and "our" mean that operator.
For privacy questions and data requests, email lionmadnessminecraft@gmail.com. You do not need a Discord account to contact us, and you do not need to be unbanned. If you have been removed from the Server or the Discord, email still works. Our Discord is a community channel as well, but it is not the only way to reach us.
Copyright, privacy, and safety complaints have their own route and expected response window on the Reporting & Complaints page.