Privacy Policy

ZeroBot is run by an individual, not a company:

Mirko Goldschmidt
Am Sophienhof 8, 24941 Flensburg, Germany
contact@zeropvp.xyz

The bot, its data and the dashboard run on a server in Germany. The data ZeroBot stores there is encrypted at rest (AES-256-GCM). Everything runs on Discord as well, and Discord's own privacy policy covers what Discord does with it.

Which ZeroBot features run on a server is decided by that server's staff. For questions about why a feature is on in a particular server, ask its staff; for anything about what ZeroBot itself stores, use the address above.

The settings staff make on the dashboard or with commands: which modules are on, which channels and roles they use, panels, messages, word lists, ticket categories, staff teams, the bot's profile on that server, and similar configuration. These are stored against the server's ID and hold channel and role IDs rather than anyone's personal data.

ZeroBot also keeps a record of which account added it to a server and when. For support and to handle abuse, the ZeroBot team can see a server's setup and metadata in its staff panel: the server's public Discord details, its owner's public profile, who added ZeroBot, which modules are on, ZeroBot's own counters for that server (for example tickets, cases and AI use) and the change journal. Message text and member lists are never shown there.

ZeroBot also keeps a history of the servers it joins and leaves: the server's ID, its name and member count at the time, the date and, for a leave, the reason when known. The ZeroBot team uses it to follow ZeroBot's growth. It is kept for one year and deleted with the rest of a server's data on request. The team can also keep internal notes about a server, for example about a partnership or about abuse reported to the team. These notes are about the server, never about a member: names and user IDs are not written into them. They are kept until the team removes them, and deleted with the rest of a server's data on request.

Depending on which features a server has switched on, ZeroBot stores the following against your Discord user ID:

Messages. ZeroBot reads messages in channels it can see, to run filters, count XP and answer commands. It does not keep them in a database. Recent messages are held in memory for about a day (at most 25 hours) so that, if a server has message logs on, a deleted or edited message can be shown in that server's log channel. Restarting the bot clears that memory. When a filter or AI moderation acts on a message, the case record keeps the matched part (at most 500 characters) so staff can review the decision. Exception: on servers that switch on the message backup in Undo changes, messages in the chosen channels are kept for a limited time (see How long it is kept).

AI providers. ZeroBot's AI features are off until a server switches them on. When they are on, text is sent to one AI provider at a time, in this order, the next one only if the one before is unavailable: Groq (Groq, Inc., Mountain View, USA), Google Gemini (Google LLC, Mountain View, USA) and Mistral AI (Mistral AI SAS, Paris, France). Where the operator adds it, Anthropic (Anthropic, PBC, San Francisco, USA) is used for ZeroBot AI's server designs. Each acts under its own data processing terms; transfers to the USA rely on the EU standard contractual clauses or the EU-US Data Privacy Framework, as the provider offers. Training on this data is switched off wherever the provider allows it. Google's free Gemini service may use what it receives to improve Google's products, which is why it is only the second choice. ZeroBot keeps only the result, not the request.

AI moderation. On servers that switch it on, the text of messages in the channels it watches is sent to the AI providers above to be scored for threats, harassment, hate, sexual content and similar. Images are checked by Mistral. Only the score and, when it acts, the case record are kept.

Names and profiles. Screening, when a server has switched it on, looks at usernames, display names, avatars, banners and account age when someone joins or changes them. Nothing is stored unless a check flags the account, in which case the report is posted to that server's staff log.

Images. On servers that use the strict chat filter, scam screening or profile screening, images posted in chat, and the avatars and banners of members who join or change them, are sent to Mistral AI (Mistral AI SAS, Paris, France) to be checked for scams, sexual content, gore and hate symbols. If the operator adds Anthropic, it is asked first. ZeroBot keeps only the result. On the operator's own server, partnership proof screenshots are checked the same way.

Support questions. On servers that switch on AI answers for a ticket panel or Auto replies, the question you type, and your in-game name if you give one, are sent to the AI providers above together with that server's own support text, so that an answer can be shown to you. The answer is shown only to you; the question and the answer are also posted to that server's ticket log channel for its staff, and copied into the ticket if you choose to open one. ZeroBot keeps only a daily count.

ZeroBot AI on the dashboard. What server staff type into ZeroBot AI is sent to the AI providers above to design or set up their server. Questions about the server's own numbers (Ask your server) and the morning briefing send only totals, never names, user IDs or message text.

Public pages. A server can choose to publish a Live Server Map or a monthly Monthly video. They show counts for channels everyone on that server can see. Member names appear on them only if the server's staff switch that on.

Uploaded images. Images staff upload on the dashboard (for example a card background) are stored by ZeroBot and can be opened by anyone who has the link, so Discord can show them.

Web verification. When a server verifies members through a web page, that page is served by the dashboard (on the operator's own server, by its website), whose web server sees your IP address like any website does. It is not linked to your Discord account and not kept beyond the ordinary access logs.

What a log channel or case forum shows is stored by Discord, in that server, and managed by that server's staff.

Signing in uses Discord. You allow ZeroBot to read your Discord ID, username and avatar, and the list of servers you are in. The server list is used to show which of your servers you can manage; it is read when you sign in and when you open the server list, held in memory for up to a minute so the page does not ask Discord twice, and not stored. ZeroBot does not ask for your email address.

Signing in sets one session cookie. It is encrypted and holds your Discord ID, name and avatar link, the server you are managing, and the Discord access token that lets the dashboard read your server list. It lasts until you sign out, or 30 days after you last used the dashboard.

The dashboard has no analytics, no advertising and no tracking. The web server keeps ordinary access logs, including IP addresses, for security and fault finding, and rotates them away after a short time.

Premium bought on the dashboard is paid through Stripe (Stripe Payments Europe, Ltd., Dublin, Ireland). Your card or other payment details are entered on Stripe's page and are never seen by ZeroBot. Stripe's privacy policy covers the payment itself.

ZeroBot receives and keeps: which server the subscription is for, the Discord ID of the person who paid, Stripe's IDs for the customer and the subscription, its status, and when the paid period ends. That is what switches Premium on and lets only the payer open the billing page.

Premium bought inside Discord is handled by Discord, and ZeroBot only learns which server has it.

Some features act on their own once a server's staff switch them on: auto moderation can delete a message and time out or ban a member after repeated hits, and screening can ban an account whose name, avatar or banner is clearly sexual, advertising or hateful. Borderline cases are flagged to staff instead of being acted on.

Every automatic action is recorded with the reason. The person affected sees a short notice in the channel. ZeroBot sends only two kinds of direct message: one welcome note to the person who adds it to a server, and, if a server switches on Bot approval, a security alert to the server owner when a new bot joins. You can ask for a human review at any time: ask the server's staff (for a ban, on the server's ban appeal page when it has one, or by contacting a staff member or the owner), or email contact@zeropvp.xyz. Staff can undo any of these actions in one click.

Servers can choose to take part in the Shared ban list, which is off by default. When ZeroBot on a taking-part server stops a nuke attempt, catches a scam it is certain of, or when that server's staff confirm a raid wave, or when that server's owner reports an account with an evidence link, ZeroBot stores: the account's Discord ID, a category (scam, nuke attempt, raid, spam bot, other), a short reason, a hash of what was caught (never the message itself) or the evidence link the owner gave, and which servers reported it, with the time.

Why: to protect servers and their members from accounts that already harmed another server. Legal basis: legitimate interest in preventing abuse and fraud (Art. 6(1)(f) GDPR). Other servers only see the category, the reason and how many servers confirmed it, never which servers. Only ZeroBot's operator sees which servers reported, to stop misuse. One server's report by hand never lists anyone on its own.

How long: a listing ends after 90 days, after 180 for a second listing and 365 from the third. Unconfirmed reports end after 30 days. Ended entries are deleted after another 30 days; a count of past listings is kept for a year so repeat cases are recognised.

Your rights: sign in with Discord on Account reputation to see whether you are listed and why. If you are, you can appeal; an accepted appeal removes the entry on every server at once. You can also write to us for access, correction or deletion.

ZeroBot inside Discord (the Activity): when you open ZeroBot's panel from Discord's App Launcher, Discord asks you to share your account's name and ID (the identify scope). ZeroBot uses them to check that you may manage that server, keeps a one-hour sign-in only in the open panel, and stores nothing new. Changes you make there are logged like changes on the dashboard.

Polish with AI: the text an owner asks to polish is sent to the AI providers named above and not kept. ZeroBot keeps only a count per server and day.

Rules in plain words, on servers that switch it on: messages are checked against the server's own rules, quick checks on ZeroBot itself and, for messages worth a look, the AI providers above. When a rule acts or flags a message for staff, ZeroBot keeps a case: the member's id, the channel, the rule, the message text (up to 500 characters) and what was done, for 90 days (at most 200 per server). Strikes (member id and time) are kept 30 days. Purpose: enforcing the rules the server wrote (legitimate interest of the server and its members).

The welcome A/B test, on servers that run it: which welcome version a new member got, stored against a salted hash of the member id (never the id), with when they joined, whether they left and whether they wrote a message in their first 7 days. After 7 days each row becomes plain counts per version and is deleted. Purpose: showing the server which welcome works better (legitimate interest).

How you compare: once a day ZeroBot works out a few counts for every server (member growth, how many new members stay a week, the share of members who wrote this week, messages per writer, moderation cases per 1,000 members, ticket closing time) and keeps only the sorted numbers per server size, never which server they belong to and nothing about any member. A server sees its own percentile only where 10 or more servers of its size have data. Servers can leave themselves out on the Insights page. Purpose: showing a server how it is doing (legitimate interest).

AI auto events, on servers that switch it on: event points per member id for the running season and week, the top three of each event (the last 30 events) and of each season (the last six seasons), who holds the weekly winner role, and during a weekly challenge the member id and message id of each entry, deleted when the challenge closes. Quiz button answers are kept in memory only while the event runs. Questions are written by the AI providers named above from the server's topics; no member data is sent to them. Purpose: running the server's events (legitimate interest of the server and its members).

The LFG board, on servers that switch it on: each open post's author id, the ids of members who joined, the mode, rank, region and note they picked, until the post closes (at most six hours); then it is deleted. The gaming setup keeps, for 24 hours, which channels and roles it made on the server so they can be undone. Purpose: helping members find people to play with (legitimate interest of the server and its members).

On servers that switch them on: canned replies and tags (the server's own text), staff notes on open tickets (the staff member's id and name, the text) and, per open ticket, its priority, tags, who it is assigned to and when the first staff reply came. With Ticket history on, each closed ticket is kept for 365 days without message text: the ids and names of the opener and of the staff who handled it, its topic, times, priority, tags and response target. With Full transcripts on, the whole conversation of a closed ticket (names, ids, message text, attachment links, staff notes) is kept for 90 days, or up to 365 days on Premium servers that choose it, then deleted; it is shown to the server's staff on the dashboard and posted in the server's transcript channel, never sent by DM. Purpose: running the server's support (legitimate interest of the server and its members). A deletion request removes every transcript that mentions the person.

Temporary roles: on servers that use them, the member's ID, the role ID, the end time, who gave it and the short reason they typed, until the role ends. Role persistence, on servers that switch it on: the IDs of a member who left and the chosen roles they had, for 1 to 90 days (30 by default), then deleted, or at once when the server switches it off. Purpose: the server's own role management (legitimate interest of the server). A deletion request removes both.

Giveaways: the IDs of the members who entered, the winners and, with a claim window, when each winner claimed. Shown to the server's staff on the dashboard. Kept with the giveaway until the server deletes it; a deletion request removes the person from every giveaway.

Reminders and AFK, on servers that switch them on: a reminder's member ID, channel, time and text until it fires (a repeating one until cancelled), and an AFK note with the member's ID and since when, until they write again or for 30 days at most. Switching either off deletes what it stored for that server. Nothing is ever sent by DM.

Starboard, on servers that switch it on: which messages reached the board, their channel, the author's ID, the board card's ID and the star count, for 180 days. The text stays in Discord. Switching the starboard off deletes the list.

Bump reminder, on servers that switch it on: per server list, the time, channel and member ID of the last bump, and per member how many bumps they made this month and the two months before. Switching it off deletes both.

Invite extras, on servers that switch them on: whether a join counts as fake, how often a member rejoined, bonus invites staff gave, and the members who hid themselves from the public board, kept with the invite records. The public board, when a server switches it on, shows display names, avatars and invite counts of its top inviters, never IDs; members leave it with /invites hide.

Minecraft monitor, on servers that switch it on: per watched Minecraft server, hourly counts of checks, how many were online and the number of players, for 7 days (30 with Premium). No player names are stored. Switching it off deletes the history.

Public link checker: the link you check is not stored or logged; only the number of checks per day is kept, for 30 days. To stop abuse, the checker keeps a one-way hash of your network address in memory for a day to count your checks.

XP import, when a server's staff runs it: member IDs with their XP and level, from Lurkr's public leaderboard for that server or from a file staff upload. The loaded data is deleted after the import or after 15 minutes; the copy of each member's previous XP for Undo is deleted after 24 hours.

Ask ZeroBot, on servers that switch it on: a member's question and the last few messages of their conversation go to the AI providers named above and are held in memory for 30 minutes, never written to disk. ZeroBot stores only a count per server and per member for the current day.

Translate, on servers that switch it on: the message a member picks goes to the AI providers to be translated. Neither the text nor the translation is stored, only a count per server and member for the current day.

Confessions, on servers that switch them on: the text goes to the AI providers for the safety check. ZeroBot stores the confession's number, the author's ID, the time, its status and the IDs of members who reported it for 30 days, and the text only while it waits for staff review. People with Manage Server on that server can look up the author, and every lookup is logged.

Form application extras: when a form has staff votes on, the IDs of the reviewers who voted and their vote are kept with the submission, as long as the submission is kept.

Partnership desk, on servers that switch it on: per partner the server's name and ID, its invite code and member count (read from Discord's invite endpoint), and the IDs of who asked and who approved, kept until staff remove the partner; the ad and invite of an open request, kept until its ticket closes.

Emoji manager, on servers that switch it on: per emoji of that server, how many times it was used in messages and reactions per month, for three months. Never who used it. Switching it off deletes the counts.

Fun pack, on servers that switch it on: who opted out of fun actions, duo pairs and since when, and per member the collectibles they found and the time of their last explore. Switching it off deletes all of it.

On Premium servers with Backups: the server's roles, channels and permission settings, including permissions set for single members, the settings the server made in ZeroBot (for example ticket panels, welcome messages and the staff members named in a setting), which Marketplace setups it installed, and who made each backup or restore.

Only when a server switches the message backup on: for the channels it chose, the last messages with their text, the author's ID, display name and avatar link, the time, the message they replied to, embeds and attachment links, and optionally small attachments themselves. Never DMs, never channels ZeroBot cannot read, and NSFW channels only when the server names them.

Before switching it on, the server's owner or an admin confirms that the members are told, and ZeroBot records who confirmed it and when.

Message data leaves a backup after the time the server chose, at most 30 days, and right away when the server switches the message backup off or deletes it. The backups themselves are kept until newer ones replace them (7 daily and 10 manual), until they are deleted, or until deletion is requested. An undo snapshot taken before a restore is kept for 24 hours.

A data deletion request also removes the person's messages and attachments from every backup, takes their mentions out of the text that is left, and removes their name from who made a backup.

A restore posts the messages back in the same server through a temporary webhook that is deleted afterwards. It never sends a DM and never pings anyone.

When a server owner switches on a public page, ZeroBot shows the server's name, icon and banner, the owner's description, category and tags, the member and online counts from Discord, and the sections the owner turned on, at a public address and in the server directory. The page is off by default and is gone at once when the owner turns it off. Servers Discord marks as age-restricted are never shown.

The leaderboard on a public page lists only members who opted in themselves with /public-page leaderboard, by display name and level. For that, ZeroBot stores the member's Discord ID per server. It is removed when the member opts out with the same command, leaves the server, or asks for their data to be deleted.

Nothing about the visitors of public pages and the directory is stored.

ZeroBot Plus, Pro and Ultra bought inside Discord are sold and billed by Discord. ZeroBot only receives Discord's notice that a server has a plan (the server, the plan and when it ends), never payment details.

On ZeroBot Ultra, Undo changes change journal is kept for 90 days or the last 6,000 entries, and the setting history for 365 days or the last 5,000 changes, per server. Messages in a backup are still kept at most 30 days.

Yearly plans are paid through Stripe (Stripe Payments Europe, Ltd.). Stripe receives your payment details and email address; ZeroBot receives only the subscription's status, plan, billing interval and end date, the server it is for and the Discord ID of the person who paid.

The checkout and thank-you pages read which servers you manage and their plan, to show them to you. Nothing about that is stored.

When a server is built with the Server Builder, ZeroBot keeps the IDs of the channels, roles and panels the build made and the settings it changed for 24 hours, so the owner can undo it. Nothing about members is in that record.

Permission check: when someone presses Fix, what the fix changed (the role or channel ID and the permission bits before and after) and who pressed it, kept 24 hours so it can be undone, then deleted.

Rule tests: when a server's staff start one, ZeroBot reads up to 5,000 recent messages from channels it can see, only in memory. The text is never saved; a few shortened examples are shown to that staff member and forgotten 10 minutes after the test. Only the number of tests a day is stored.

Raid drills: the drill's own lines are made up. The report keeps the time and the ID of the first staff member who reacted, and the command names used, for the last 10 drills.

Auto slowmode: how many messages each channel got in the last minute, in memory only, with no text and no member IDs.

Bulk role tools: the IDs of the members a job changed and who started it, kept 24 hours so the job can be undone, then deleted.

Setting history: when someone saves a setting on the dashboard, ZeroBot keeps which fields changed, their old and new values, who saved them (Discord ID, name and avatar link) and when, so the server's managers can see the change and put it back. Secrets such as webhook links, keys and tokens are never kept, and member data is never part of it. Kept 30 days or the last 200 changes per server (90 days or 1,000 with Plus or Pro).

Phone alerts: if you turn them on, ZeroBot stores your Discord ID, the server, your browser's push address and its two public keys, the events you chose, a short device name and your language. Alerts go through your browser's push service (Google, Mozilla, Apple or Microsoft, depending on the browser), encrypted so only your browser can read them, and name only the server and the event. Your entry is deleted when you turn alerts off, when the push service says it is gone, when you leave the server or no longer manage it, and when ZeroBot leaves the server. They are never sent as Discord DMs.

Website widget: the widget on a server's website shows only what its public page shows (name, icon, member and online counts, the next event and the Join link). It sets no cookies, and ZeroBot stores nothing about the people who see it; like any web request, our server receives their IP address and browser details to deliver it.

Discord sign-in check: if a server uses it, members sign in with Discord on ZeroBot's verify page with the identify scope only. ZeroBot reads their Discord ID and whether they have a profile picture, once, to check it is the account that joined and to apply the server's rules (account age, avatar, the Shield list). Discord's token is revoked straight away; nothing from the sign-in is stored and no cookie stays behind.

Cloudflare Turnstile: on the verify page, the One click and Press and hold methods, and servers that switch it on, show Cloudflare's bot check (Cloudflare, Inc.). It runs in the browser and Cloudflare receives the browser and device signals it needs for the check; it sets no tracking cookies. ZeroBot sends Cloudflare only the check's token, never the member's IP address. Without it, these methods are not offered.

Quiz, picture pick, math and press and hold: the answers are checked by ZeroBot and never stored after the check. The verify page keeps a short-lived, hashed count per connection in memory to stop abuse; IP addresses are not stored or logged.

Server Studio shows a server's owner and staff how the server is doing. For it ZeroBot keeps one small record per server per day: numbers of messages, joins, leaves, active members, voice minutes, messages per hour, the busiest channels, and counts of level-ups, moderation actions, raids, tickets, giveaways, events and starboard posts. It never stores what anyone wrote.

Two parts name people. The top chatters list reads the monthly message counts ZeroBot already keeps for Monthly recap; members who hid themselves from the public invite board or opted out of the fun pack are never named, and the server can switch names off. The busiest staff list counts moderation actions and ticket replies per staff member.

The daily records are kept for 365 days and then deleted. A new member's first message is noted as a time for 8 days, only to count it once. A deletion request removes a person's id from these records like from every other.

The weekly report is off until a server switches it on. It posts one card in the channel the server picked, with these numbers and the names of the busiest staff as plain text. It never mentions or messages anyone.

The help chat in the corner of this website sends what you type there to an AI provider to write the answer. Conversations are not stored: only daily counts of chats and messages are kept. To limit misuse, a salted hash of your IP address is held in memory for one hour.

When a ticket is closed, ZeroBot sends the member who opened it one direct message with the server's name, the ticket, who closed it and the reason. It is not sent when they closed the ticket themselves, and a server's staff can turn it off on the Tickets page. Apart from this, ZeroBot only messages the person who adds it (one welcome message) and, where a server turns it on, the server owner when someone adds a bot.

• Running the features a server has switched on, the dashboard sign-in, and Premium: performance of a contract (Art. 6(1)(b) GDPR).
• Moderation records, logs, screening, AI moderation, risk score, Staff activity alerts, the change journal and security logs: legitimate interest in keeping servers and the service free of abuse (Art. 6(1)(f) GDPR).
• Linking a Minecraft account with /sync: your consent, which you can withdraw by unlinking (Art. 6(1)(a) GDPR).
• Keeping payment records for as long as tax law requires: legal obligation (Art. 6(1)(c) GDPR).

• Server settings stay after the bot is removed, so adding it back restores the setup. A server owner can ask for them to be deleted at any time.
• Server join and leave history: one year. Staff notes about a server: until the team removes them or deletion is requested.
• Member records stay until staff clear them (warnings, for example, can be removed on the dashboard) or until deletion is requested.
• Messages in memory for at most 25 hours.
• Auto moderation strikes for 30 days.
• Undo changes change journal for 30 days, or the last 2,000 entries per server. The message backup, only where a server switches it on: 7, 30 or 90 days depending on the plan, at most 300, 1,000 or 2,000 messages per channel. A message its author or staff deletes is removed at once, and switching the backup off deletes everything.
• Staff activity alerts counts for 28 days.
• Reputation, coins, quest contributions and form answers until staff remove them, the server deletes the form, or deletion is requested.
• Uploaded images until deletion is requested.
• Backups until they are replaced by newer ones, deleted on the dashboard, or deletion is requested. Messages in a backup at most 30 days.
• Referrals for one year after the referral is decided (counted or not).
• Session cookie until sign-out, or 30 days after the last visit.
• Payment records for as long as German tax law requires, up to ten years.

Under the GDPR you can ask for a copy of what is stored about you, have it corrected or deleted, object to processing based on legitimate interest, and get it in a portable form. Email contact@zeropvp.xyz with your Discord user ID and, if it is about one server, that server's name.

One honest limit: a ban or case record can be kept after a deletion request where a server needs it to keep a banned person out. You can object to that, and it is then weighed case by case.

You can complain to a supervisory authority. For this controller that is the Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein.

If this policy changes, the date at the top changes with it. A change to what is collected or why is announced on the dashboard before it applies. The Terms of Service cover everything else about using ZeroBot.