What we collect
- Discord identifiers: user IDs, usernames, and display names for ticket authors, claimers, closers, application applicants, and staff who take action (accept/deny/jail/etc.).
- Ticket content: channel names/IDs, and the ticket’s transcript (the message history at close time).
- Application content: the answers submitted to a category’s configured questions, plus decision reasons given by staff.
- Server configuration: whatever your admins configure through the bot’s settings menus (category names, role IDs, channel IDs, message templates, premium tier).
How it’s stored
- Guild configuration, ticket records, and application records are stored in a MongoDB database.
- Short-lived state (cooldowns, rate limits) is cached in Redis and expires automatically.
- Ticket transcripts are stored as HTML files in Cloudflare R2, access-protected, and cryptographically signed so you can verify a transcript hasn’t been altered with
/verify.
How long it’s kept
- Closed ticket records are automatically deleted 60 days after close, unless the ticket is tied to an active jail record (which is kept until the member is unjailed).
- Application records that never reach “submitted” (abandoned mid-conversation) are automatically deleted 60 days after being started.
- Submitted, accepted, and denied application records, and their answers, are kept until deleted on request (see below) or removed by server admins.
Who it’s shared with
We don’t sell data. Data is shared only with the infrastructure providers needed to run the bot:- Discord, as the platform the bot operates on.
- Cloudflare, for transcript storage (R2) and hosting.
