> 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/for-customers/security-and-sub-processors.md).

# Security & sub-processors

How customer data is secured, who helps us process it, and transfers outside the UK.

## Data security

District Studio applies security measures appropriate to the nature of the data and the risk, which may include:

* restricted access to systems holding customer data;
* multi-factor authentication on accounts with access to customer systems;
* secure storage of credentials;
* encryption in transit (HTTPS/TLS) for hosted websites and APIs;
* encryption at rest where supported by the hosting provider;
* separation of customer environments where practical;
* keeping software, dependencies and servers updated;
* backups for hosted services where agreed; and
* deleting credentials and files at the end of the project.

See also the [Security & data breaches](https://docs.districtstudio.xyz/privacy-policy/security-and-breaches.md) page of the Privacy Policy.

Security is a shared responsibility. The customer is responsible for the security of systems it controls, including its own Discord server permissions, hosting accounts, FiveM server, txAdmin access and website administration accounts.

No system is completely secure. District Studio does not guarantee that a security incident will never occur.

## Sub-processors

### General authorisation

The customer gives District Studio general authorisation to use sub-processors to provide its services. District Studio will:

* use only sub-processors that provide sufficient guarantees of appropriate security;
* have a written contract with each sub-processor imposing data protection obligations equivalent to those in this document, usually through the sub-processor's standard data processing terms;
* remain responsible to the customer for its sub-processors' performance; and
* inform customers of intended changes to sub-processors by updating the list below, and announcing the change in our Discord community at least 14 days before it takes effect, so that customers have the opportunity to object.

### Sub-processor list

| Type of sub-processor | Service                                     | Data processed                                            |
| --------------------- | ------------------------------------------- | --------------------------------------------------------- |
| Cloud hosting         | Hosting bots, websites, dashboards and APIs | Hosted application data and logs                          |
| Database hosting      | Storing databases                           | Hosted databases                                          |
| File storage          | File storage and backups                    | Customer files and backups                                |
| Source code hosting   | Storing source code                         | Code and configuration that may refer to customer systems |
| Google Workspace      | Business email                              | Messages and attachments                                  |

Customers can ask for the names and locations of the specific sub-processors at any time by emailing <mattwright@districtstudio.xyz>.

Discord is not a sub-processor of District Studio for bot data. Discord is an independent controller of its platform, and both the customer and District Studio use it under Discord's own terms.

## International transfers

Some sub-processors may process data outside the United Kingdom. Where District Studio, as processor, transfers customer data outside the UK, it will ensure the transfer is covered by UK adequacy regulations or appropriate safeguards (such as the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses), as described in the [Sharing & international transfers](https://docs.districtstudio.xyz/privacy-policy/sharing-and-transfers.md) page of the Privacy Policy.

Where the customer instructs District Studio to integrate a third-party service located outside the UK, the customer is responsible for assessing that transfer as controller. District Studio will provide information it reasonably has to help.

{% 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/for-customers/security-and-sub-processors.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.
