Trust and safety
Is Security Bot safe?
Security Bot has run since December 2019. Why it requires Administrator, what it reads and stores, what it logs, and how to tell the real bot from copies.
- Running since
- December 2019
- Added to
- 1M+ servers since 2019
- Bot permission
- Administrator
- Login scopes
- identify, guilds
Who runs Security Bot
Sina founded Security Bot in December 2019, when it started as a small script. Since 2019 it has been added to more than 1,000,000 Discord servers. A volunteer moderation team helps members in the support server. The project returned to active development in 2026.
Public documentation lives at docs.securitybot.gg, and questions are answered in the support server linked from this site. The announcement page has a letter from Sina and lists the moderation team.
Why Security Bot requires Administrator
Security Bot requires the Administrator permission. Without it, anti-nuke ignores the events it watches and the dashboard refuses to save settings, replying "I must have the administrator permission in order to function".
The actions themselves map to narrower Discord permissions: Kick Members, Ban Members, Manage Roles, Manage Channels, Manage Messages, Manage Server, Manage Webhooks, Timeout Members, and View Audit Log. Administrator also bypasses every channel permission overwrite, so no channel is hidden from the bot.
Role position matters as much as the permission. The bot can only act on members below its highest role. Members whose highest role is above Security Bot's role are exempt from anti-nuke. Put it above your staff roles so anti-nuke covers them.
Administrator does not let a bot read your private DMs.
What Security Bot reads and stores
The privacy policy lists what is stored and for how long. The bot keeps each server's settings and whitelists until you ask for them to be deleted. Removing the bot does not delete them, so a nuker who kicks it cannot wipe your protection.
The bot also keeps anti-nuke punishment records for 90 days and anti-raid join records for 30 days. Timed bans, locks, and mutes are kept until they expire, and verification entries until the member verifies. When Recovery is on, it keeps server backups and a 90-day bin of deleted items.
The dashboard keeps your Discord account details from login, and paid plans keep billing records.
Security Bot reads message content in real time, because its filters need it. The invite-link filter, anti-spam, and the AutoMod link filters check each message as it is posted.
Message content is not stored. When the bot's internal event bus is on, raw Discord events, including message content, pass through it and are kept for at most 2 minutes.
Logs are messages the bot posts in your own Discord channels, so you decide how long they stay. To have your server's settings or your account data deleted, ask in the support server.
The bot is bound by its own limits
While Anti Ban and Anti Kick are on, ban, softban, banid, and kick commands run through Security Bot are capped at their limits. They are counted per moderator and reset every 10 minutes. At the cap the command is refused until the counter resets.
The whitelist does not raise this cap. The server owner and Administrators ranked above Security Bot are not capped.
Only the server owner and Administrators ranked above Security Bot can open its dashboard and view or change settings, including whitelists.
The security log channel receives User Warning, User Punished, and Anti Raid Lock entries, plus web check denials, possible alt accounts, and raids that Adaptive Verification detects. User Warning is posted for each counted action below an anti-nuke limit, with the attempts remaining. User Punished is posted when anti-nuke or Beast Mode punishes a member.
The moderation log channel receives the bot's moderation commands except /clear and /raid ban, with the moderator, target, and reason. It also receives anti-raid timeouts and channel locks (reason "Anti Raid"; anti-raid bans are not logged), plus the timeouts, kicks, and bans from AutoMod and the link guards.
The server owner also gets a DM when anti-nuke punishes someone. Free servers get the moderation and security log channels. Premium adds audit and AutoMod log channels.
How to make sure you have the real bot
Other bots can use a similar name. Invite Security Bot from securitybot.gg or docs.securitybot.gg, and use the support server linked from this site. If an invite came from a DM or an unfamiliar site, do not accept it.
The dashboard runs at securitybot.gg and asks Discord only for the identify and guilds scopes when you log in. It never asks for your password, email, or card details.
Premium checkout starts on the dashboard. Card payments go through Patreon or Polar; crypto is paid in advance with no automatic renewal.
Reliability
Security Bot runs 24/7, but no bot can promise it will never go offline. If it is offline, Discord's own permission system is unchanged. Your staff keep the permissions you gave them, and anti-nuke resumes when the bot reconnects.
This is one reason to pair the bot with a sensible native permission setup rather than relying on it alone.
Official links
Only trust these sources
- securitybot.gg
- docs.securitybot.gg
- Support Discord
- Privacy policy
Questions
Safety FAQ
Is securitybot.gg legit?
Yes. securitybot.gg is the official site for Security Bot, alongside docs.securitybot.gg and the support Discord linked from this site.
Is it safe to give Security Bot Administrator?
Security Bot requires Administrator. Without it, anti-nuke ignores events and the dashboard cannot save settings. It acts only on members below its role. Its ban and kick commands are capped by your anti-nuke limits while Anti Ban and Anti Kick are on. Punishments and moderation commands are logged in your own channels. Only the owner and Administrators ranked above Security Bot can change its settings.
Does Security Bot read my messages?
Yes. It reads message content in real time because its filters need it. The invite-link filter, anti-spam, and the AutoMod link filters check messages as they are posted. Message content is not stored. When the bot's internal event bus is on, raw events that include it are kept for at most 2 minutes.
Can Security Bot nuke my server?
The bot acts on its own when one of its protections fires, such as punishing a member who reaches an anti-nuke limit or deleting an invite link. Seven anti-nuke triggers are on from the start, and Premium also starts with Anti Mention Spam and Anti-Spam on. You can turn any of them off.
The bot also lifts timed bans and locks when their time runs out. On Premium, it runs the Recovery backups and restores you turn on, and the Premium Bot leaves servers that have no premium slot.
Everything else is a command run by someone allowed to use it. While Anti Ban and Anti Kick are on, ban, softban, banid, and kick commands are capped at their limits per moderator.
What happens if the bot goes offline?
Your Discord permissions are unchanged and protection resumes when the bot reconnects. Keep native permissions tight so an outage is not an opening.
How do I remove Security Bot?
Kick the bot from Server Settings, Integrations. Removing it does not delete your server's settings. To have them or your account data deleted, ask in the support server.