> 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/terms-of-service.md). # Terms of Service The rules for using Dispatch **Effective date:** October 5, 2026 These terms cover **Dispatch** (the "bot"), a Discord bot that posts alerts in Discord servers when a Patreon creator publishes a new post or goes live. The bot is run by Pixalon ("we", "us"). By adding the bot to a server or using its commands, you agree to these terms. ### 1. What the bot does * It checks the public page of the Patreon creators a server chooses to follow and posts a message in that server when there's something new: a new post, a scheduled or started Live, a weekly recap, a season wrap. * It only reads what Patreon shows to anyone who isn't logged in: a post's title, when it was published, its thumbnail, and whether it is free or for members. **It never shows members-only content.** To watch a video, people still have to go to Patreon and have the right membership. * It can also look up show artwork (posters, episode names) from AniList and TVmaze to decorate the alerts. ### 2. Who can use it * You must follow [Discord's Terms of Service](https://discord.com/terms) and [Community Guidelines](https://discord.com/guidelines), and be old enough to use Discord (13 or older, or the age required where you live). * Adding the bot to a server and changing its settings requires the **Manage Server** permission in that server. The people with that permission are responsible for how the bot is set up there: which creators it follows, which channel it posts in, who it pings. ### 3. Acceptable use Don't use the bot to: * redistribute, leak or help people get around paying for a creator's members-only content; * spam, harass or ping people in ways that break your server's rules or Discord's; * interfere with the bot's operation (flooding it with commands, trying to break it, or accessing it in ways it isn't meant to be used). We may remove the bot from a server, or stop serving it, if it's being used in those ways. ### 4. Patreon, AniList, TVmaze and Discord The bot depends on these services and on their public data staying available. We are not affiliated with Patreon, AniList, TVmaze or Discord. The creators' names, pictures and posts belong to the creators; show artwork belongs to its rights holders. Their own terms apply when you follow a link to them. ### 5. Availability and changes The bot is provided **as is**, free of charge, with no guarantee that it will be available, accurate or on time. Alerts can be delayed or missed, for example when Patreon or Discord are down or change how they work. We may change, pause or shut down the bot at any time, and we may update these terms; the effective date at the top says when they last changed. If you keep using the bot after a change, you accept the new terms. ### 6. Liability To the extent the law allows, we are not liable for any loss or damage that comes from using the bot or from not being able to use it, including missed or wrong alerts. ### 7. Privacy What the bot stores and why is explained in the Privacy Policy, the next page on this site. ### 8. Contact Questions about these terms: 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/terms-of-service.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.