Legal
Privacy Policy
What Rogue stores, why it needs it, how long it stays, and how to have it removed. Last updated August 2026.
The short version
Rogue stores the minimum needed to do what a server has asked it to do. It does not sell data, does not use it for advertising, and does not share it with anyone outside the services listed below. Remove the bot from a server and that server's configuration stops being used; ask and it will be deleted.
What is stored
Identifiers
Discord user, server, channel, role and message IDs. These are what make a setting belong to a server or a case belong to a member. Rogue does not store email addresses, passwords or payment details, and never sees them.
Configuration
Whatever a server sets up: prefixes, enabled modules, welcome and goodbye messages, ticket panels, reaction roles, protection thresholds, logging channels. This is content the server's own admins wrote.
Moderation records
When a moderator bans, kicks, times out, jails or warns someone, Rogue records who acted, who it was applied to, the reason given and when. A moderation log is only useful if it persists, so these are kept until the server deletes them or removes the bot.
Message content
Rogue stores message content in three narrow cases, each because a feature cannot work otherwise:
-
Snipe. Recently deleted and edited messages, so
,snipecan show them. Cleared automatically after 7 days. - Ticket transcripts. The conversation in a ticket, written when it closes, so staff can refer back. Kept until the server deletes them — the archive has a bulk delete.
- Confessions and quotes. Only what a member explicitly submits to those features.
Ordinary conversation is not logged or retained. Messages are read in transit to check for commands, triggers and spam, then discarded.
Aura
A balance, a daily streak, message counts per server, and a record of gifts and purchases. Aura is one balance per person across every server the bot is in.
Dashboard sign-in
Signing in uses Discord OAuth with the identify guilds
scopes — your username, avatar and the list of servers you are in.
Rogue cannot read your messages or act as you. The session is a
cookie; there is no third-party analytics or advertising on this site.
Changes made from the dashboard are recorded — who changed what and when — so a server can see its own history.
Why it is stored
Every item above exists to make a feature work. Settings have to persist or a server would reconfigure the bot on every restart; moderation records have to persist or a case log is pointless; transcripts have to persist or closing a ticket would destroy the conversation. Nothing is collected speculatively or for analysis beyond a per-server count of which commands get used.
Who it is shared with
Nobody, other than the infrastructure that runs the bot:
- Discord — the platform the bot operates on.
- The database host — where the data above is stored.
- The hosting provider — where the bot process runs.
Data is not sold, rented, or handed to advertisers or data brokers. It is disclosed otherwise only if the law requires it.
How long it is kept
| Sniped messages | 7 days, deleted automatically |
| Server configuration | Until changed, or the bot is removed |
| Moderation cases | Until the server deletes them |
| Ticket transcripts | Until the server deletes them |
| Aura balances | Until deletion is requested |
| Dashboard session | Cookie, expires or is cleared on sign-out |
Getting your data removed
Ask on the support server and it will be deleted. Server owners can request everything for their server; an individual can request their own records, including their aura balance and any moderation history.
Removing the bot from a server stops its configuration being used immediately. It is not deleted automatically, so that adding the bot back does not mean setting everything up again — ask if you want it gone for good.
Age
Discord requires users to be at least 13, or older where local law says so. Rogue is not intended for anyone below that age, and data belonging to someone under it will be deleted on request.
Changes
If this policy changes materially, the date at the top changes with it. Continuing to use the bot after that means accepting the revised version.