- We store what the features need - mostly Discord IDs, server settings and statistics. Never what you write in your messages, unless you give the bot that text on purpose.
- We don't sell your data, don't use it for ads and don't use it to train AI.
- You can delete your statistics (
,stats privacy off) and your name history (,names clear) yourself, and ask us to delete everything else.
1Who we are
Bot is a Discord bot with a website and a web dashboard, run by its developer ("we", "us"). This policy explains which data the bot, the website and the dashboard process, why, who else gets it and how you can have it deleted. It applies to everyone who uses the bot or is a member of a server that uses it. How to reach us is in section 13.
2Data from Discord
To work, the bot receives data from Discord about the servers it's in:
- IDs of servers, channels, roles and messages;
- for members: user ID, username, display name, avatar, roles and when they joined;
- messages in channels the bot can see (see section 3);
- who joins, leaves or switches voice channels;
- status and activities, when that's turned on - for example to reward members who put the server's invite in their status.
Most of this is only used in the moment and never saved. Section 4 lists what is saved.
3Message content
The bot reads messages to answer commands and to run features that server staff turn on - for example filters (invites, links, spam, words), auto responders, levels, counting and AFK replies. It doesn't save what you write, with these exceptions:
- Text you give the bot on purpose, like an AFK status, a reminder, an embed, a custom command or a giveaway prize.
- Snipe: the last 25 deleted or edited messages and removed reactions per channel are kept in memory - never in the database - so members can see them with the snipe commands. They're gone when the bot restarts, and server staff can turn snipe off.
- AFK mentions: while you're AFK, messages that mention you are kept in memory (up to 50), so you can see who pinged you.
If server staff set up logging or ticket transcripts, the bot posts things like deleted or edited messages and ticket transcripts into a channel of that server. It doesn't keep its own copy.
4What we store
These are saved in the bot's database:
| Data | What exactly | How long |
|---|---|---|
| Server settings | Prefixes, module setups, welcome and boost messages, auto responders, embeds, custom commands, filters, roles, tickets, logging and other settings made by server staff. | Until staff remove them or ask us to delete them. |
| Moderation | Cases, warnings, moderator notes, jails, mutes and bans - with the member, the moderator, the reason and the time. Roles saved so they can be given back later (jail, sticky roles, role restore), and filter violations. | Until staff remove them. |
| Activity statistics | How many messages you send per channel and day, your voice time, your active hours, when and where you were last seen and which emojis you use. Never what you write. | Hourly data for 100 days, the rest until you opt out or staff reset it. |
| Levels, economy & games | XP and levels, coins and items, game, counting and roleplay stats, giveaway entries, starboard posts and invite tracking (who invited whom and when they joined). | Until staff reset them or we delete them on request. |
| Things you save | Your AFK status, reminders, Last.fm username, personal prefix and settings such as turning off level-up messages. | AFK until you write again, reminders until they're done, the rest until you remove it. |
| Name history | When you change your username or display name, the bot saves the old one - only while it shares a server with you. Others can look it up with the names command. | Until you clear it with ,names clear. |
| Tickets & confessions | Who opened, claimed and closed a ticket, the reason and the times. For confessions the bot remembers who sent each one, so staff can act on reports - other members never see it. | Until staff delete them. |
| Server backups | The server's layout (roles, channels, permissions) when staff make a backup - no messages and no member data. | Until staff delete the backup. |
| Blacklist | IDs of users and servers that may not use the bot, with the reason. | Until the block is lifted. |
5Website & dashboard
- Login: when you ask for a login link, the bot looks up the username you enter among the members of its servers and sends the link to that account's DMs. When you log in - with that link or with Discord - we save a session: a random token (we only store a hash of it), your user ID, username, display name and avatar. With the Discord login we also save the list of servers you manage (name, ID, icon). A session ends after 14 days or when you log out.
- Cookies: one cookie keeps you logged in, and a short-lived one protects the Discord login. No tracking, analytics or advertising cookies.
- Your browser remembers which channel you picked for channel actions in the dashboard (local storage on your device).
- Dashboard actions are written to the bot's log - who ran which command, in which server and channel - so misuse can be traced.
- IP addresses are kept in memory for a short time to limit requests. We don't keep access logs.
- Avatars and server icons are loaded from Discord. The website has no trackers or ads.
6Why we use it
- To run the features you and your server staff use.
- To keep servers and the bot safe - moderation, antinuke, antiraid, filters, the blacklist and request limits.
- To find and fix errors.
We don't sell or rent data, don't use it for advertising and don't use it to train AI models. Where the GDPR applies, we rely on providing the features you ask for (Art. 6(1)(b) GDPR) and on our legitimate interest in running a working and safe bot (Art. 6(1)(f) GDPR).
8How long we keep it
- As long as the features need it - see the table in section 4.
- When the bot is removed from a server, that server's data isn't deleted right away, so nothing is lost if the bot comes back. Server owners can ask us to delete it at any time.
- Data kept only in memory - snipe, AFK mentions, request limits - is gone when the bot restarts.
- The bot's technical log (errors, starts, dashboard actions) rotates by itself and keeps about 20 MB at most. Database backups are made regularly, and only the newest few are kept.
9Your choices & rights
You can do a lot yourself:
,stats privacy off- stops tracking your activity and deletes your statistics.,names clear- deletes your name history.,lastfm unlink- removes your Last.fm username.,remind delete- deletes a reminder. Your AFK status ends as soon as you write again.,levels messages off- no more level-up messages for you.
For anything else - a copy of your data, a correction, deletion or an objection - contact us and include your Discord user ID. We answer within one month. Moderation records may be kept when there's a good reason, for example to prevent abuse - we'll tell you if we can't delete something. If you're in the EU, the EEA or the UK, you can also complain to a data protection authority.
10Security
Access to a server's data follows Discord permissions: the dashboard only lets you do what your permissions allow, and every action goes through the same checks as in Discord. Login tokens are random, stored only as hashes and kept in cookies that scripts can't read. Only we have access to the bot's server and database. No system is perfectly secure, but we work to protect your data.
11Children
Discord requires users to be at least 13, or older where local law says so. The bot isn't meant for anyone younger, and we don't knowingly collect their data. If you think we store a child's data, contact us and we'll delete it.
12Changes
We may update this policy when the bot changes. The date at the top shows the current version. Where we can, we'll announce important changes - for example in our support server.
13Contact
Questions or data requests? Reach us here - please include your Discord user ID: