Captain Guild
Privacy
Captain Guild runs on a machine controlled by the people who run the server you're in. This copy serves only its owner's own Discord servers. This page says what it keeps, for how long, and who can see it.
What it keeps
| Data | Why | How long |
|---|---|---|
| Message text, attachment names and links, and who wrote them | To log edits and deletes and let staff review a report | 30 days by default, and each server can change it |
| Log entries: joins, leaves, role and name changes, voice moves, server changes, and the full text of deleted, edited, purged and pinned messages and of messages automod caught | Moderation records and log search | 90 days by default, and each server can change it |
| Moderation cases: action, reason, moderator, time, and automod incidents | The server's moderation history | With no set end. Staff can void a case, which marks it and keeps it. |
| Moderation notes: text, author, time | The server's moderation history | Until staff delete them |
| Running mutes, temporary bans and lockdowns: who, who applied it, when it ends | To end each one on time | Until it ends |
| People raid mode holds: ID, name and the role put on them, and who turned raid mode on | So staff can look them over and let them go | Until they're let go, and until raid mode ends |
| Reports: who reported whom, the reason, and copies of the reported message and its files | So staff can act on a report, even if the message is deleted | Until staff delete them |
| Voice reports, voice access requests and who decided them, mini mutes, and who voted how on a mini mute | The server's voice moderation | With no set end. A mini mute's own row goes when it ends. |
| XP and level, rank card background, birthday, reminders, highlight words, game scores, message counts | The features those belong to | Until you or staff remove them. A rank card background goes 30 days after you leave. |
| Roles you held when you left | To give them back when you return | Until you return, or 30 days by default, and each server can change it |
| Giveaways: who entered and who won | To run the draw and keep its result | With no set end. Your entries go when you delete them with /my_data. |
| Starboard: a preview of each starred message, its author, and who starred it | To keep the board's count and numbers | Until the post leaves the board |
| Suggestions: their text, the author's name and avatar link, the vote totals and the decision | The server's record of what was suggested | Until staff delete them |
| Who reacted on a reaction role message, and who had the bot repeat a message | To hand out roles once, and to tell staff who sent what | A reaction record goes when the message stops handing out roles. Who had the bot repeat a message has no set end. |
| Tags, triggers, posted messages and their earlier versions, saved messages, scheduled posts, server settings, and who changed them | The server's setup and its change history | Until staff delete them. The change history keeps each server's newest 5,000 entries. |
| A role rules sync that's running: who started it, its progress post and how far it has got | To pick the sync up again after a restart | Until the sync finishes |
| Which roles could read a deleted channel | So log search shows what was said there only to those who could read it | As long as that channel's log entries last |
| Backup snapshots: a copy of a server's stored data, and copies of its XP board | To put a server back after a mistake | The newest 14 scheduled snapshots by default, and each server can change it. Staff delete the ones taken by hand. Someone's rows in a snapshot stay until that snapshot goes, except levels, which come out of the XP copies when deleted. |
| Which commands you ran, counted by day | Command use numbers for staff | 90 days |
| Proposals: their text, who submitted them and the vote totals | The server's record of what was put to a vote | Until staff delete them. Who voted which way stays on Discord, as reactions on the post, and isn't stored. |
| Your Discord ID, name and avatar link when you sign in to the dashboard | To keep you signed in | 14 days from sign-in |
You sign in with Discord. The site asks Discord only who you are, then revokes the token right away and never stores it. The bot's /dashboard command also answers with a private sign-in link, which works once and expires after five minutes. No IP addresses are stored.
Who can see it
Staff of the server the data belongs to, through the dashboard and the log channels they set up, and the person who runs the machine. It isn't sold, shared with anyone else, or used to train machine learning models.
What goes to other services
A lookup sends what you typed to the service that answers it. /games fortnite sends the player's name and platform to Fortnite-API, and /games roblox sends the user name to Roblox. The full list of outside services is in the project's THIRD_PARTY.md.
How it's protected
The databases and their scheduled copies are encrypted at rest with SQLCipher (AES-256). The key is held apart from them. The site forces HTTPS.
Getting your data removed
Type /my_data in Discord. The private link opens a page that shows what the bot holds about you, gives you a copy, and deletes your birthday, highlights, reminders, levels, giveaway entries, game scores, usage counts and message counts for voice access. For anything else, open a ticket with the server's staff or contact the person who runs the bot. Moderation records stay when staff need them to keep the server safe, and stored messages and log entries stay until their retention ends.
Changes
This page changes when the bot's handling of data changes. The history is in the project's public source.