1. Who is responsible for your data
Kitchen Sink is used by Discord server administrators to manage their communities. This creates two roles under data-protection law:
- Server administrators are the “controllers” of their members' data. They decide to add the bot, choose which features to enable, and configure retention. We act as their “processor”, handling that data on their instructions.
- We are the “controller” for the data we need to run the dashboard itself — principally your Discord login and session.
If you are a server member with questions about how a particular server uses the Service, contact that server's administrators first — they decide what is enabled. You can also contact us using the details at the end.
2. What we collect
Dashboard login (we are controller). When you sign in with Discord we receive, via Discord OAuth, your Discord user ID, username, avatar, and the list of servers you can manage (the identify and guilds scopes). We store a login session so you stay signed in.
Server data (we are processor for the server admins). Depending on the features a server enables, the bot may store:
- Discord identifiers — user, channel, role and message IDs, usernames/nicknames and avatars, cached so the dashboard can show names without re-querying Discord.
- Aggregated activity — daily per-user, per-channel counts of messages, reactions and voice minutes, plus join/leave events. Message content is not stored for these counts. Short-lived voice-session rows are purged within a few days.
- Moderation records — cases (bans, kicks, mutes, warnings, notes and reversals): the target and moderator, reason, duration and timestamps, plus evidence attached to the case — added by a moderator, or captured automatically when an action is taken or a protective filter matches (which may include message snapshots, links, or uploaded images). Moderation actions taken by other bots can be mirrored in too, where a server points us at their logs.
- Tickets — ticket metadata and HTML transcripts of ticket conversations (these do include the messages and attachment links from within that ticket), plus optional feedback ratings.
- Optional cached messages — a per-server message cache used for moderation evidence is off by default. When an admin turns it on, recently deleted/edited message content is held for a short, configurable period and then purged.
- Configuration & audit — a server's settings, and an audit log of configuration changes (what changed, by whom, and when).
3. Why we use it, and our legal bases
We use the data only to provide the Service: to run the dashboard, to deliver tickets and moderation, to produce activity insights for the server, and to keep the Service secure and working.
Under the UK GDPR and the Data Protection Act 2018, our legal bases are:
- Performance of a contract / taking steps at your request — providing the dashboard and Service to you and to the servers that install it;
- Legitimate interests — the server's interest in moderating and managing its own community, and our interest in operating and securing the Service;
- Consent — where a feature depends on it (for example, optional message caching enabled by an administrator).
We do not sell personal data, and we do not use it for advertising.
4. How long we keep it
Retention depends on the feature and on the server's configuration:
- Activity is aggregated to daily totals; raw voice-session rows are purged within a few days.
- Ticket transcripts and moderation cases are kept as the server's record until deleted.
- Cached messages (when enabled) are kept only for the short window the admin configures, then purged.
- The audit log is kept for the retention period the admin chooses.
- Login sessions expire after a period of inactivity.
When the bot is removed from a server, or on a valid deletion request, we delete or anonymise that server's data, except where we must keep something to meet a legal obligation.
5. Who we share it with
We share personal data only with the service providers needed to run the Service — for example, our hosting/infrastructure provider — who act as our sub-processors under appropriate terms. The data originates from, and is governed in part by, Discord's own Privacy Policy. We may disclose data where required by law. We do not sell it.
Separately, server administrators can enable optional features that send data elsewhere on their instruction — these are off unless an administrator turns them on:
- GitHub sync — where an admin links a Discord thread to a GitHub issue, messages posted in that thread are mirrored as comments on the linked issue, under GitHub's own terms and privacy policy.
- Ban federation — where two servers explicitly link with each other, ban records are shared between those linked servers so their staff can review them.
Where data is processed outside the UK/EEA, we rely on appropriate safeguards (such as adequacy decisions or standard contractual clauses).
6. Security
We use reasonable technical and organisational measures to protect personal data, including access controls and encryption in transit. No system is perfectly secure, but we work to limit what we store and to protect what we do.
7. Your rights
Under the UK GDPR and the Data Protection Act 2018 you have rights over your personal data, including to access it, correct it, erase it, restrict or object to its processing, and to data portability, plus the right to withdraw consent where processing relies on consent.
Because server administrators are the controllers for their members' data, the quickest route for a server member is usually to contact that server's administrators. You can also contact us at [email protected] and we will help you exercise your rights or route your request to the right controller. If you are unhappy with how your data has been handled, you can complain to the UK Information Commissioner's Office (ICO).
8. Children
The Service relies on Discord, which sets a minimum age for its users. We do not knowingly collect data from anyone below Discord's minimum age. If you believe a child's data has been processed, contact us and we will address it.
9. Changes to this policy
We may update this policy from time to time. The “last updated” date at the top shows the current version; material changes will be reflected here.
10. Contact
For any privacy question or data-rights request, contact the Kitchen Sink team at [email protected].