> 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/support-and-communications.md).

# Support & communications

Our support channels and how messages are handled.

You can contact District Studio through any of these channels:

| Channel                 | Provided by                                                      | Notes                                                                                                      |
| ----------------------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Discord support tickets | Discord                                                          | Ticket conversations are held in Discord and may be saved as a transcript when the ticket is closed.       |
| Website contact form    | Our website on [districtstudio.xyz](https://districtstudio.xyz/) | Messages are sent to our business email.                                                                   |
| WhatsApp Business       | WhatsApp (Meta)                                                  | Messages are also covered by the [WhatsApp Privacy Policy](https://www.whatsapp.com/legal/privacy-policy). |
| Email                   | Google Workspace                                                 | <mattwright@districtstudio.xyz>                                                                            |
| Telephone               | Mobile network provider                                          | 07852879877. Calls are not recorded.                                                                       |

We use the messages, screenshots, attachments, logs and other information you send to handle custom order enquiries, bug reports, billing questions, product support, troubleshooting and feedback.

Please do not send passwords, full card details or special category information in support messages, unless we have asked for them through a private method we have agreed with you.

When you contact us through a third-party platform, that platform also processes your messages under its own privacy policy.

{% 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/support-and-communications.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.
