> 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/website-development.md).

# Website development

Information we handle when building, hosting and maintaining websites.

District Studio designs and builds custom websites, redesigns, frontends and backends, dashboards, customer portals, APIs, databases and integrations. We also provide maintenance, troubleshooting and, where agreed, hosting, domain and DNS setup.

This work may involve:

* **website logins** for CMS, hosting, control panels and code repositories;
* **domain and DNS details**, including registrar access if you give it to us;
* **your content**, including text, images and information about your staff or customers that appears on your site;
* **contact form submissions and user account data** held in websites we build or host;
* **website analytics**, where you give us access; and
* **technical logs and error reports**.

If we build a website that collects personal information from your visitors, you are the controller of that information. If we host or maintain the site afterwards, we process it on your behalf. You stay responsible for your own privacy notice and cookie compliance unless we have agreed in writing to provide them as part of the project.

{% 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/website-development.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.
