Privacy Policy
Last updated 9 September 2026
This policy covers the official PotatoBot instance, operated by Cyteon and invited via this link.
PotatoBot is open source under the GPLv3, so anyone can run their own copy. This policy only applies to the official instance. If you are using a self-hosted copy, ask whoever runs it what they do with your data.
Contact me@cyteon.dev or the support server
What we collect
Identifiers
We store numeric Discord IDs for users, servers, channels, roles and messages. We do not store usernames, display names, avatars or email addresses. Names shown in bot responses are read live from Discord and thrown away once the response is sent.
Per-server user data
For each user in each server where the bot is active, we may store:
- ·XP and level
- ·Economy balance and minigame state, such as farm progress and cooldown timestamps
- ·Warnings issued by that server's moderators, including the reason text and who issued them
- ·Jailed, whitelisted and trusted flags
Global user data
Across all servers, we may store:
- ·Whether you are blacklisted from the bot, and why
- ·Whether you are excluded from the AI, and why
- ·Counters: total commands run, times flagged by the word filter, NSFW requests, AI requests
- ·Moderation strikes issued by the bot's operators
Server configuration
Settings a server administrator chooses: command prefix, log and announcement channel IDs, level roles, jail and default role IDs, starboard settings, anti-nuke toggles, disabled commands and lockdown state.
If a server supplies its own Groq API key, that key is encrypted before it is stored.
Message content
The bot receives message content in servers it is in, because Discord's Message Content intent is required for prefix commands, spam filtering and the features below. Most of that content is handled in memory and never written anywhere.
The exception is the AI chatbot. In channels a server administrator has specifically set up as AI channels, your message and the bot's reply are saved so the assistant can follow the conversation. You are shown a notice explaining this the first time you use it.
Message content is read but not stored by us for:
- ·Parsing prefix commands
- ·Spam and mass mention detection
- ·Awarding XP, where only a counter is kept
- ·Starboard reposts, where we store the two message IDs and not the text
- ·Message edit and delete logs, which are posted as embeds into a channel the server chose
- ·The translate context menu
Command errors are reported to a private Discord channel through a webhook, and that report includes the text of the command that failed.
Server statistics
Daily message counts and member counts per server, kept for 30 days. No message content, no per-user breakdown.
Why we collect it
To make the bot work. XP has to persist for levels to mean anything, warnings have to persist for moderators to see history, jail state has to persist so leaving and rejoining does not wipe a punishment, and the AI needs recent messages to hold a conversation.
How long we keep it
| Data | Retention |
|---|---|
| AI conversation history | 7 days from your last message in that channel, then deleted automatically |
| Server statistics | 30 days, rolling |
| XP, economy, warnings, moderation flags | Until deletion is requested, or the bot is removed from the server |
| Server configuration | Until deletion is requested, or the bot is removed from the server |
AI and machine learning
Message content sent to the AI is used to generate a reply and nothing else. We do not use it to train, fine tune or evaluate any model, and we do not hand it to anyone else for that purpose. Groq states that it does not train on API data.
Your choices
Email or ping us in the support server and we delete what we hold against your user ID.
Removing the bot stops all collection straight away.
Staying out of the AI. The AI only responds in channels a server administrator has specifically designated, and in response to the AI commands. If you do not use those channels or commands, nothing of yours is stored by the AI.
Deleting your data. Email me@cyteon.dev or ask in the support server and we will delete what we hold, including any stored AI conversation history. We may keep blacklist records where deleting them would let someone dodge a ban, and we cannot delete moderation logs the bot posted into a server's own channels, because those messages belong to that server.
Getting a copy of your data. Same contact details. We will send you what we hold against your user ID.
Server data. A server administrator can ask us to delete everything tied to their server.
Storage and security
Data is stored in a self-hosted MongoDB database on infrastructure we control. Access is limited to the bot operator. Server-supplied API keys are encrypted at rest. No system is perfectly secure and we cannot promise against every possible breach.
Children
Discord requires users to be at least 13, or older where local law sets a higher minimum. The bot is not intended for anyone below that age. If we find out we hold data from someone under it, we will delete it.
Changes
We will update the date at the top when this policy changes. Anything significant will be announced in the support server.