> For the complete documentation index, see [llms.txt](https://locked.gitbook.io/dispatch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://locked.gitbook.io/dispatch/privacy-policy.md). # Privacy Policy What Dispatch stores, why, and for how long **Effective date:** October 5, 2026 This policy explains what **Dispatch** (the "bot") stores, why, and for how long. The bot is run by Pixalon ("we", "us"). The short version: the bot keeps the IDs it needs to post alerts in your server and to keep them up to date, and nothing about what people say. ### 1. What the bot does not collect * **No message content.** The bot does not read messages in your server. It uses only Discord's "guilds" intent, which gives it the list of servers, channels and roles; it has no access to what people write. * **No direct messages**, and nothing from users' profiles beyond their Discord user ID in the one case below. * **No Patreon accounts.** The bot has no Patreon login. It reads only what Patreon's website shows to a logged-out visitor. ### 2. What the bot stores **Server settings** (chosen by a moderator with /setup and /patreon settings) * the server's ID, the channel IDs the alerts go to, and the role IDs used for pings; * the Patreon creators the server follows, with the server's choices for each: who gets pinged, filters, an extra line under the alerts, which extras are switched on; * the Discord user ID of the moderator who added or changed a creator, and when; * the IDs of the roles the bot makes for the "Follow a show" buttons, and the IDs of the server events it creates for Lives. **Alert history** (so nothing is announced twice, and so alerts can be updated) * the Patreon posts it has seen: their ID, title, link, type and publication time, as shown publicly by Patreon; * the IDs of the messages it posted for them, the channel and server they are in, and the discussion threads it opened; * a post's public like and comment counts on Patreon, and the **number** of 🔥 👍 😐 reactions under its alert in each server (counts only — not who reacted). **Show lookups:** the names, posters and episode lists of shows it looked up on AniList and TVmaze, so each show is only looked up once in a while. **Pictures:** thumbnails and posters are downloaded to be attached to the alerts and are kept in memory only briefly. Pressing a "Follow a show" button gives you a role in that server, through Discord; the bot does not keep a record of who pressed it. Slash commands are answered privately to the person who ran them and are not stored. ### 3. Why Everything above is used for one purpose: posting the alerts a server asked for, and keeping them correct (updating a card with its likes, adding a button when the next episode is out, not posting the same thing twice). Nothing is used for advertising, profiling or analytics, and nothing is sold or shared with anyone. ### 4. Where it's kept, and who can see it The data is stored in files on a server we control. Only we have access to it. It is sent to no one else, except that the bot necessarily sends messages and requests to: * **Discord**, to post and edit alerts ([Discord's privacy policy](https://discord.com/privacy)); * **Patreon**, to read creators' public pages ([Patreon's privacy policy](https://www.patreon.com/privacy)); the bot doesn't send Patreon anything about your server; * **AniList** and **TVmaze**, to look up show artwork; only a show's name is sent. ### 5. How long * Server settings are kept while the server follows at least one creator. They are deleted when a moderator removes the last creator (/patreon remove) or when the bot is removed from the server. * Alert history is kept for the most recent posts of each creator (the oldest entries are dropped as new ones come in) and is deleted when no server follows that creator any more. * Show lookups are refreshed from time to time and don't contain anything about your server. ### 6. Your rights A server's moderators can see and change everything the bot stores about their server with /patreon settings and /patreon status, and delete it by removing the bot. If you want something about you or your server deleted, or want to know what is stored, contact us (section 9) and we'll do it. ### 7. Children The bot is for Discord users, who must be at least 13 (or older where the law requires). We don't knowingly store anything about younger children; if you think we have, contact us and it will be removed. ### 8. Changes We may update this policy; the effective date at the top says when it last changed. ### 9. Contact Message infam0ux on Discord. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://locked.gitbook.io/dispatch/privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.