Privacy
Palisade stores what it needs to do its job and no more. This page describes what that is in practice, including the parts that are less convenient to admit.
Last updated 29 August 2026.
The short version
- Ticket transcripts keep message content in full. Nothing else stores what people say.
- Three companies are involved: Discord, Railway for hosting, Stripe for payment. There is no analytics or advertising anywhere, and nothing is sold.
- Most records expire on a schedule you set per server. Moderation cases and transcripts are kept until you say otherwise.
- Signing in asks Discord for your profile and server list. It does not ask for your email, so Palisade cannot email you.
Who this covers
Palisade is a Discord bot and dashboard. Two different groups of people appear in its data, and they are not in the same position.
- People who sign in to the dashboard
- You authorise Palisade through Discord to configure servers you already manage. Palisade decides what to collect about you, and this page is the description of that.
- Members of a server that uses Palisade
- A server owner runs Palisade in their community and chooses what it does there: which events are logged, what automod removes, whether tickets keep transcripts. Palisade holds that data on their behalf. If you want your data in a particular server changed or removed, the server owner decides, and Palisade will act on a request they make.
What is stored
- Server configuration
- Your settings: log channels, automod rules, role menus, ticket panels, automations.
- Moderation records
- Case number, action, target and moderator IDs, reason, duration and timestamp. Kept indefinitely unless the server sets a retention window, because moderation history is the point of having it.
- Account details
- For people who sign in to the dashboard: Discord user ID, username, display name and avatar hash. Palisade requests only the identify and guilds scopes from Discord, so it never receives your email address and cannot send you email.
- Sessions
- A hash of your session token, an approximate location (IP truncated to a /24 or /48 prefix) and your browser’s user agent, so an unfamiliar sign-in is visible. The Discord tokens attached to a session are encrypted.
- Ticket transcripts
- When a ticket is closed, Palisade saves a transcript of that ticket channel: who sent each message, when, the message text, and the names and links of any attachments. This is message content, kept verbatim.
- Activity counts
- Per-server totals used for the analytics page and levelling: how many commands ran, how many messages a member sent. Counts, not content.
- Billing
- For servers on a paid plan: a Stripe customer and subscription id, the plan, and its status. Card details go to Stripe and never reach Palisade.
Message content
This is the part most worth being exact about, because a bot with these permissions could read everything and the honest answer is not a simple no.
- Automod
- Messages are inspected in memory and only the rule that matched is recorded. A short excerpt is kept only if the server turns that on, so appeals can be reviewed. Excerpts age out with the automod retention window.
- Tickets
- A closed ticket’s transcript keeps every message in that channel in full. It exists so staff can answer what happened after the channel is gone. By default it is kept until the ticket is deleted; a server can set a window after which transcripts are cleared, leaving the ticket record without its contents.
- Everything else
- Logging records that an event happened and who was involved, not what was said. Levelling counts messages without reading them. Analytics counts commands.
How long it is kept
| Record | Kept for |
|---|---|
| Automod matches | 30 days by default. |
| Automation runs | 14 days by default. |
| Security events | 90 days by default. |
| Configuration audit trail | 180 days by default. |
| Moderation cases | Indefinitely, unless the server sets a window. |
| Ticket transcripts | Indefinitely, unless the server sets a window. |
| Sessions | Seven days, or until you sign out. |
Each of these is configurable per server, and a background job enforces them daily.
Security
Discord OAuth tokens are encrypted before storage and revoked at Discord when you sign out. Session cookies are HTTP-only and cannot be read by scripts. Tokens, secrets and connection strings are redacted before a log line is written. Access to a server’s settings is recomputed from Discord on every request, so losing Manage Server in Discord removes dashboard access immediately rather than when a token expires.
Palisade holds no security certification and does not claim one. The database is reachable only from inside its private network and is not exposed to the internet.
Removing data
Removing Palisade from a server stops all collection immediately. Configuration and moderation history are retained so that re-adding the bot does not lose them, so an accidental kick does not erase a server’s records. Nothing is deleted automatically when the bot leaves.
To have a server’s data deleted outright, ask from an account that owns the server. Signing out deletes the session and revokes the Discord token. Requests are handled by hand rather than through a self-service portal, and backups are kept for a short period after a deletion, so data can persist there briefly after it is gone from the live database.
Children
Discord requires its users to be at least 13, or older where local law sets a higher age, and Palisade is not directed at children. It does not ask anyone’s age and has no way to tell how old a Discord account holder is. If you believe a child’s information is held here, contact us and it will be removed.
Where this is processed
In the United States. Palisade is not offered specifically to people in the European Economic Area or the United Kingdom, is priced in US dollars and is published only in English, but Discord is global and a server anywhere can add it.
Changes
The date at the top changes when this page does. A change that materially widens what is collected or who receives it will be announced before it takes effect rather than made quietly.
Contact
Privacy questions and requests can be sent to contact@palisade.wtf. If your question is about a particular server, say which one: the server owner decides what Palisade records there, and some requests have to be made by them.