> For the complete documentation index, see [llms.txt](https://docs.districtstudio.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/discord-bots.md).

# Discord bots & services

What our bots process, what they cannot see, and who is responsible.

District Studio builds custom Discord bots for customers and runs its own Discord bot, which you can find at [bot.districtstudio.xyz](https://bot.districtstudio.xyz/), with subscription plans and a dashboard. Features can include welcome messages, tickets, applications, moderation, automated messages, server management, custom commands, configuration and integrations.

Depending on the features used, our bots may process:

* **Discord User IDs, usernames and display names** of people who interact with the bot;
* **Server (Guild), Channel and Role IDs**, to apply settings in the right places;
* **bot configuration** set by server administrators;
* **ticket messages and support conversations**, including attachments;
* **application submissions** made through application systems;
* **moderation records**, such as warnings, mutes, kicks and bans, with reasons and the moderator responsible;
* **command usage and activity logs**, to run and troubleshoot the bot and prevent abuse; and
* **subscription and entitlement information** linked to a server or user.

{% hint style="info" %}
**What our bot can and cannot see.** Our bots only process information that Discord makes available to them, through the permissions and settings granted by Discord and by server administrators. They cannot read your private messages with other users, servers they have not been added to, channels they cannot view, or anything else Discord does not provide to bots.
{% endhint %}

**Who is responsible.** Where a server owner decides what is collected and why, such as the questions on an application form or whether moderation logs are kept, the server owner is the controller and District Studio is their processor. Where District Studio uses information for its own purposes, such as subscription records, security and abuse prevention, District Studio is the controller.

Discord's own use of your information is covered by the [Discord Privacy Policy](https://discord.com/privacy).

{% hint style="info" %}
**Questions about your information?** Email <mattwright@districtstudio.xyz>.
{% endhint %}


---

# 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://docs.districtstudio.xyz/privacy-policy/how-we-use-information/discord-bots.md?ask=<question>&goal=<user_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.
