Security
What Kirzen asks for, and what it never asks for
Kirzen joins a Discord server with four permissions and never asks for Administrator. Anything more is something you give to the Kirzen role, one permission at a time, and this page says what each one is for.
What it asks for when it joins
View Channels, Send Messages, Embed Links and Read Message History. That is enough to answer in a channel, and it is also what makes Discord create the Kirzen role.
What it never asks for
Administrator. A bot with Administrator could undo anything, including everything Kirzen does to protect the server, so Kirzen does not ask for it.
What each extra permission is for
You give these to the Kirzen role only for the features you want. Without one, the feature that needs it does not work. The dashboard shows which ones are missing on the Overview of each server.
| Permission | What Kirzen uses it for |
|---|---|
| Manage Roles | Take the roles from an attacker, hand out verification roles and quarantine someone. |
| Manage Channels | Put back a deleted channel, lock channels, and create ticket and counter channels. |
| Ban Members | Ban, and lift a ban wave afterwards. |
| Kick Members | Kick members. |
| Moderate Members | Put someone in timeout. |
| Manage Messages | Delete a message that automod filtered, or clear messages. |
| View Audit Log | Know who performed an action. Without it, Anti-nuke is nearly blind. |
| Manage Server | Read invites, to trace a raid to one code, and raise Discord's verification level while the server is closed. |
Checking on us
The live state of the bot, the API and the database is public. What Kirzen collects and keeps is written in the Privacy Policy.