Yes, entirely. Every protection, moderation and community module, and the whole web panel, are free — no premium tier, no per-server limits and no feature unlocked by a payment. There is no price list because there is nothing to price.
There is no hidden payment and no limit waiting to appear later. The bot shows no ads, sells no data and needs no account beyond Discord. The project runs on its own funds and on voluntary support that unlocks nothing.
The bot sees messages in the channels it has access to — otherwise AutoMod could not catch spam and LinkShield could not catch a phishing link. Seeing is not the same as storing: Venon keeps NO message archive. Content reaches the database only where you send it to the bot yourself — a suggestion, a report, a quote, a reminder — or where it is already public, like a message pinned on the starboard.
The full list of data categoriesThe server configuration, the state of time-based features (temporary bans, reminders), the activity profiles that levels and statistics need, and the moderation records. Every category in the Trust Center names the database table and the source file, so it can be checked rather than taken on trust.
Data categories with table namesRemove the bot from the server — the deletion starts on its own. The configuration and personal data disappear after 30 days, the audit records after 90 (longer, because they serve to reconstruct an incident). Nothing needs reporting. If you want it sooner, or want to file a request about a specific person, write to the privacy address given in the Trust Center.
Retention periods and the request procedureThe bot stops doing anything immediately — no moderation, no recording, no replies. The configuration stays for 30 days, so adding the bot back within that window does not mean setting everything up again. After that it is deleted without asking.
No. The install link asks for a specific set of permissions derived from the operations the bot actually performs. The Administrator permission bypasses the role hierarchy and every channel setting — a bot holding it could do anything on the server, whatever you configure. Venon used to ask for it; it no longer does.
The permission list, explainedYes — protection keeps no office hours, because a raid at three in the morning does not wait for a moderator. We do not promise a hundred percent availability with it: outages happen and they are visible on the public status page, together with a note when the monitoring itself goes quiet.
Live service statusA new member lands in the verification channel and only after passing it receives the role that opens the rest of the server. You can add a minimum account age to filter out accounts created moments earlier. All of it is set in the panel — no commands to type.
How Verify worksYes, every module works on its own and every one can be turned off in the panel. You can go further and take away the permission a given module needs — then only that module stops, and the rest stays. Nothing is forced as a bundle.
Which permission belongs to which moduleYes. MSIoU works on reciprocity: a server sees signals from other servers only while it publishes its own. Turning it off cuts both directions at once — there is no watching without sharing. It is the only feature that carries information beyond your server, which is why it has its own description in the Trust Center.
How MSIoU worksYou remove the bot and that is the end of it — no notice period, no account to delete, no subscription to cancel. The data disappears by itself on the schedule above. If you would rather see how the bot behaves first, look at the demo — it shows the course of a response without adding anything to your server.
Protection demoThis page answers the questions that come before installing. If the bot is already running and something is off — the help centre collects the usual post-rollout problems, and the documentation describes the configuration module by module. For questions answered nowhere, ask on the support server.