Privacy policy

Last updated: 1 October 2026

This policy explains what data the Wardeny Discord bot and this website process, why, and for how long. We keep it as short as possible and only collect what the features need.

1. Who is responsible

[Your full name]
[Street and number]
[Postcode and city]
[Country]
Email: [Your email address]

2. Visiting this website

When you open this website, our server receives technical data your browser sends automatically: IP address, date and time, the page requested and your browser type. We use it only to deliver the site and keep it secure (Art. 6 (1) (f) GDPR). We don't keep access logs with your IP address. Technical error logs are deleted after 14 days at the latest.

Fonts, styles and scripts are hosted on our own server. We don't use analytics, advertising or tracking tools. Your light or dark mode choice is saved in your browser's local storage and never sent to us. If you switch the language, a cookie remembers your choice for one year. When you close the cookie notice, your browser remembers that in its local storage. It contains only the language code. Premium users who pick a website color get one more cookie that stores only the color name.

3. Logging in to the dashboard

You log in with Discord. Discord then shares your user ID, username, avatar and the list of servers you're in, including your permissions there. We use this to show you the servers you can manage (Art. 6 (1) (b) GDPR). The login is kept in memory on our server and ends when you log out, after 7 days, or when the bot restarts. A single cookie stores your session. It's technically required and contains no tracking.

4. The Wardeny bot on Discord servers

Server admins add Wardeny to their server and choose which features to use. Wardeny then processes the following data. The legal basis is Art. 6 (1) (b) and (f) GDPR: running the features the server uses and keeping the server safe.

Messages

Wardeny reads messages as they arrive to apply AutoMod rules and to run tickets. We don't store message content in our database. There are three exceptions the server admins can see: messages that break an AutoMod rule are copied to the server's log channel, ticket conversations are saved as a transcript in the log channel and sent to the ticket creator by DM, and suggestions are stored so members can vote on them.

Stored data

• Moderation: user IDs, reasons and times of warnings, bans, kicks and timeouts, including those done directly in Discord (read from the server's audit log).
• Tickets: who opened a ticket, topic, times, priority, which team member handled it, an AI-written summary, and the optional rating and comment.
• Verification: user ID and time of passing the captcha.
• Statistics: joins, leaves, AutoMod hits and a daily “was active” marker (user ID and date, no content).
• Community features: poll votes, suggestion votes, giveaway entries and button-role choices.
• Welcome messages: if a server turns them on, Wardeny loads a new member's avatar and name to create the welcome card image. The image is posted in the server's welcome channel and not stored by us.
• Premium: for servers with Premium, we store which Discord user activated it. A custom bot name, avatar, banner and bio set by the server's admins are sent to Discord and shown on that server.
• Nuke protection: to rebuild channels and roles an attacker deleted, Wardeny remembers deleted channels and roles (their settings and which members had a role) for 15 minutes, in memory only. If a server turns on message backup, the last 50 messages of each channel (author name, avatar, text and attachment links) are also kept in memory only, never written to disk, and are lost when Wardeny restarts. They are reposted only when a channel is rebuilt after an attack.
• New bots: when a bot joins, Wardeny stores which roles and permissions it had until the owner accepts or rejects it.
• Embeds, custom commands and to-do lists: what admins create in the embed builder, the command creator and the to-do list is stored for their server until they delete it.
• Hold music: an audio file a server uploads for its voice waiting room is stored on our server until it's removed.
• AI banner studio: the image description an admin writes is sent to Pollinations.ai to create the image. Generated images are stored on our server (the 30 newest per server) and can be opened by anyone who has the link, because Discord needs to load them.
• Sticky messages: the text of a sticky message and the channel it belongs to are stored until an admin removes it.
• Partners: for partner servers a server adds, Wardeny stores the invite code and the public server name, icon, banner and member counts that Discord shows for that invite.
• Premium users: when the bot owner grants Premium, we store the user's Discord ID and username, who granted it, when, and an optional note.
• Voice support queue: if a server turns it on, Wardeny keeps the order of members in the waiting room in memory only, posts the numbered queue in that voice channel's chat and notifies the server's team.
• Changelogs: posted changelogs are stored with version, title, text and who posted them, so admins can see earlier posts.
• AI server builder: the description an admin writes for /aibuild is sent to the AI provider (see section 5) to design the channels and roles.
• Minecraft linking: Minecraft username and UUID, together with the Discord user ID.
• Safety checks for new members: when a server turns them on, Wardeny looks at the account's age, whether it has a profile picture, its username and whether it was banned from that server before. Accounts above a risk limit can be placed in a quarantine channel until they verify. Only the risk score is stored, not the reasons.
• Minecraft VPN check: if a server turns it on, the IP address of a player joining the Minecraft server is sent to Wardeny and checked with proxycheck.io (proxycheck.io, United Kingdom) to detect VPNs and proxies. The result is kept in memory for up to 6 hours and the IP address is never stored in our database.
• Minecraft player stats: if a server uses the WardenyLink plugin, Wardeny stores each player's name, UUID, playtime, first and last join, deaths, kills, current world, position, ping, inventory and join and leave times (online history). Server admins see this in the dashboard; position is never shown in public commands. Online history is deleted after 180 days.
• Minecraft moderation and appeals: kicks, bans, temporary bans and warnings given with Wardeny are stored with the reason. Ban appeals sent with /appeal store the player's name, linked Discord account, the ban reason and the appeal text.
• Backups: server admins can save backups of their server's roles, channels, permissions and Wardeny settings. Backups contain member IDs only where a channel has permissions for a single member.
• Minecraft server status: the Minecraft server reports its version, uptime and the names of online players every 30 seconds. This is only kept in memory to show the status.
• Minecraft chat bridge: if a server turns it on, chat messages, joins, leaves and deaths from the Minecraft server are posted to a Discord channel, and messages from that channel are shown in the game. They're passed through without being saved in our database; the last 200 Discord messages are kept briefly in memory for delivery.

5. AI features

To answer ticket questions, set priorities, suggest closing solved tickets and write summaries, Wardeny sends the relevant ticket messages to an AI service. By default this goes through a router we run, which forwards the text to one of several AI providers (for example Google, Groq, Mistral or OpenRouter). Some of these providers are located outside the EU, for example in the USA, and their own privacy terms apply. If a server admin connects their own AI provider in the dashboard, ticket messages from that server go to that provider instead, under the admin's responsibility.

So it can explain punishments, the AI also sees the ticket owner's own warnings and punishments on that server (Discord and, if linked, Minecraft). It never sees other members' records.

Please don't share passwords or other sensitive personal data in tickets.

6. Other services involved

• Discord runs the platform the bot works on. See Discord's privacy policy.
• Hosting: our server is hosted by Contabo GmbH in Europe, based on a data processing agreement.
• Images in the dashboard: avatars and server icons load from Discord's servers, and Minecraft heads load from mc-heads.net. This transfers your IP address to them.

7. How long we keep data

• Server settings, moderation records and ticket records: as long as Wardeny is used on the server. Admins can delete all of a server's data at any time in the dashboard under Settings.
• Statistics (joins, leaves, AutoMod hits, activity markers): 180 days, then they're deleted automatically.
• Minecraft link codes: 10 minutes. Linked accounts stay until unlinked.
• Dashboard logins: until logout, at most 7 days.

8. Your rights

You have the right to access, correct and delete your data, to restrict or object to its processing, and to receive it in a portable format. Contact us at the email address above. You can also complain to a data protection supervisory authority, for example the one in your country or in the German state where we are based.

9. Age

Discord requires users to meet its minimum age. Wardeny is meant to be used within those rules.

10. Changes

If Wardeny changes how it handles data, we update this page and the date at the top.