> 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/websites-and-infrastructure.md).

# Websites & infrastructure

Technical information on our websites, and the providers that run our services.

## Our websites

When you visit [districtstudio.xyz](https://districtstudio.xyz/) or [bot.districtstudio.xyz](https://bot.districtstudio.xyz/), our hosting and infrastructure providers automatically process technical information such as:

* your IP address;
* browser, device and operating system;
* the date and time of your visit;
* the pages and files requested;
* the website that referred you; and
* error reports and security events.

This is needed to show you the pages, keep the sites secure and fix problems.

## Infrastructure providers

District Studio uses outside providers to run its services. They process personal information on our behalf, as processors, and only on our instructions.

| Type of provider         | What it does                                                                  |
| ------------------------ | ----------------------------------------------------------------------------- |
| Cloud hosting            | Runs our websites, bot, dashboards and APIs.                                  |
| Databases                | Stores account, bot, entitlement and configuration data.                      |
| File storage and backups | Stores project files and backup copies.                                       |
| Domain and DNS           | Namecheap manages our domains and the DNS that directs visitors to our sites. |
| Source code hosting      | Stores the code for our products and customer projects.                       |
| Documentation            | GitBook hosts this documentation.                                             |
| Email                    | Google Workspace provides our business email.                                 |

You can ask us for the names of the specific providers we use at any time.

## Logs, monitoring and backups

Our websites, APIs, bot and servers may produce application logs, access logs, error reports and security events. We use them to run, secure and troubleshoot our services, and keep them only for a short period before they are deleted automatically.

Backups may contain copies of personal information. They are kept on a rolling basis and replaced or deleted over time ([Data retention](https://docs.districtstudio.xyz/privacy-policy/data-retention.md)).

{% 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/websites-and-infrastructure.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.
