> 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.md).

# How we use information

How information is used in each District Studio service.

Choose a service to see what information it involves and how it is used.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-gamepad">:gamepad:</i> <strong>FiveM development</strong></td><td>Server details, databases, logs and credentials in FiveM work.</td><td><a href="https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/fivem-development.md">FiveM development</a></td></tr><tr><td><i class="fa-code">:code:</i> <strong>Website development</strong></td><td>Information we handle when building, hosting and maintaining websites.</td><td><a href="https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/website-development.md">Website development</a></td></tr><tr><td><i class="fa-robot">:robot:</i> <strong>Discord bots &#x26; services</strong></td><td>What our bots process, what they cannot see, and who is responsible.</td><td><a href="https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/discord-bots.md">Discord bots &amp; services</a></td></tr><tr><td><i class="fa-palette">:palette:</i> <strong>Graphics &#x26; design</strong></td><td>Briefs, brand assets, artwork and portfolio permission.</td><td><a href="https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/graphics-and-design.md">Graphics &amp; design</a></td></tr><tr><td><i class="fa-box-open">:box-open:</i> <strong>Digital products &#x26; software</strong></td><td>Ownership, licence and entitlement records for products.</td><td><a href="https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/digital-products.md">Digital products &amp; software</a></td></tr><tr><td><i class="fa-pen-ruler">:pen-ruler:</i> <strong>Custom orders &#x26; commissions</strong></td><td>Enquiries, quotes, invoices and project records.</td><td><a href="https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/custom-orders.md">Custom orders &amp; commissions</a></td></tr><tr><td><i class="fa-headset">:headset:</i> <strong>Support &#x26; communications</strong></td><td>Our support channels and how messages are handled.</td><td><a href="https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/support-and-communications.md">Support &amp; communications</a></td></tr><tr><td><i class="fa-repeat">:repeat:</i> <strong>Subscriptions &#x26; memberships</strong></td><td>How subscription information is used and what happens when a plan ends.</td><td><a href="https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/subscriptions.md">Subscriptions &amp; memberships</a></td></tr></tbody></table>

{% 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.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.
