GuardBot is operated by Siedro Productions ("we", "us"). We decide what the bot stores and why, and we are the party to contact about it. Discord Inc. runs the platform the bot lives on and has its own privacy policy covering your Discord account.
Everything the bot stores is tied to Discord IDs — long numbers Discord assigns to users, servers, channels and messages — rather than to names, email addresses or anything from outside Discord. The bot never asks for, and has no way to see, your real name, phone number or location. The one exception is the email address you give Stripe at checkout, which Stripe passes to us so we can match a payment to a plan and handle refunds.
| Category | What is stored | Why |
|---|---|---|
| Server settings | Server ID; the channel, role and level choices staff make with /setup and other commands; the server's own allowed-word list; template choices from /build. | So the bot behaves the way each server configured it. |
| Moderation records | For each detection or moderator action: the user ID, server ID, channel ID and message ID; the matched word or short fragment; the severity; the time; what was done (reported, deleted, timed out) and how quickly; whether staff marked it a wrong call. Warnings and cases include the reason a moderator typed and that moderator's ID. | To escalate repeat offenders, show staff the history (/strikes, /case, /modstats), produce the weekly digest, and measure the filter's accuracy. |
| Plans | The Discord user ID of the person who bought a plan, the tier, the server IDs it is linked to, and start and renewal dates. For plans bought through Stripe, also the Discord username typed at checkout, the email address given to Stripe, and Stripe's subscription and customer IDs, which Stripe sends us when a payment, renewal or cancellation happens. Subscription status is fetched from Discord when a plan is bought there. | To unlock paid features on the right servers, activate a purchase on the right Discord account, and end it when the subscription ends. |
| Things you give it | Economy balances and level XP per server; birthdays (day and month only); reminders and their text; custom tags and auto-responses; suggestions; saved playlists; AFK messages; highlight keywords; poll and giveaway entries; ticket and temporary-voice records. | Because those features cannot work without them. |
| Operational logs | Errors, start-up messages, and a line per detection naming the server, channel and user tag, held in our hosting provider's log stream. | To keep the bot running and fix problems. |
To do its job the bot receives the text of messages, attachment names, and nicknames in the servers it is in, using Discord's Message Content permission. Each message is checked as it arrives and is not stored by us. The exceptions, all of which are visible to the server's staff:
/server logs set, to have deleted and edited messages posted to a log channel. Again, that is a message in your server, not a copy held by us./snipe. The bot holds the most recently deleted message per channel in memory only, so staff can see what was just removed. It is never written to disk and is gone when the bot restarts.The bot does not read direct messages. It sends one — to tell someone why they were timed out — and does not process replies.
A server can opt in with /setup intel. When it does, each automod strike in that server adds an event to a shared record for that user ID: the contributing server's ID, the severity, and the time. When an account that has strikes elsewhere joins another opted-in server, that server's staff are told how many other servers have struck them in the last 30 days and the worst severity. They are never told which servers, and never shown message content. A server that has not opted in neither contributes nor receives.
Events expire after 30 days. Clearing someone's strikes in the contributing server withdraws its events, and a wrong-call retracts the single event it created.
We do not use the data for advertising, do not build profiles of people for any purpose beyond the moderation records described above, and do not sell it to anyone.
If Siedro Productions were ever to transfer the service to someone else, the data would go with it under this policy, and we would tell affected server owners beforehand through the bot.
| Data | Kept until |
|---|---|
| Automod strikes | Counted toward escalation for 30 days; the entry itself is kept with the server's records. |
| Cross-server events | 30 days, then expired automatically. |
/snipe cache | The next deleted message in that channel, or the next restart — memory only. |
| Everything for a server | While the bot is in the server, plus 30 days after it is removed. If the bot is added back within those 30 days the records are kept; otherwise they are deleted automatically. One thing survives: a note of the date the server's free trial started, so a trial cannot be restarted by removing and re-adding the bot. |
| Plan records | While the plan is active, then as long as needed to handle refunds and disputes (up to 12 months). |
| Operational logs | Rotated by the hosting provider; typically days, not months. |
If you run a server, you control most of this directly: /setup sets the filter level and turns intelligence sharing and the digest on or off; /server logs off stops message logging; /strikes clear removes a member's strikes; removing the bot stops all collection and starts the 30-day deletion clock. To have a server's data deleted sooner, email us with the server ID.
If you are a member of a server that uses the bot, the server's staff are the ones who decided to use it and who can see your records there. You can ask them, or us, what is held about your user ID and to correct or delete it. Where your local law gives you rights to access, correct, delete, restrict or port your data, or to object to processing — for example under the GDPR or the UK GDPR, where our basis for processing is the legitimate interest of servers in keeping their communities safe and, for plans, the contract with the buyer — you can exercise them by contacting us. We will respond within 30 days. You also have the right to complain to your local data-protection authority.
We may need to keep a moderation record despite a deletion request when it is needed to enforce our terms or comply with the law; we will say so if that applies.
Data is stored on an encrypted disk at the hosting provider and reached only by the bot's own process; there is no public database. Access to the hosting account and the bot's credentials is limited to Siedro Productions. No system is perfectly secure; if we learn of a breach affecting your data we will notify affected server owners through the bot and, where the law requires, the relevant authority.
Discord requires users to be at least 13, and older in some countries, and the bot is not directed at anyone younger. We do not knowingly collect data about children below Discord's minimum age; if you believe we have, contact us and we will delete it.
We will update this policy when the bot's behaviour changes. The effective date at the top always shows the current version. For changes that expand what is collected or shared, we will notify server owners through the bot before they take effect.
Siedro Productions
Email: siedroproductions@gmail.com
Please include the server ID (Server Settings → Widget, or from /serverinfo) for anything about a specific server.