> 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/data-processing-agreements.md).

# Data Processing Agreements

When a separate Data Processing Agreement is needed, and how to request one.

### When a Data Processing Agreement is needed

UK GDPR Article 28 requires processing by a processor to be governed by a written contract containing specified terms. District Studio's position is:

* for **standard services** (such as the District Studio bot and standard support), this document, together with District Studio's [Terms of Service](https://docs.districtstudio.xyz/legal/terms-of-service.md), sets out the required terms;
* a **separate Data Processing Agreement** is recommended where:
  * the customer is a business or organisation processing significant volumes of personal information;
  * District Studio hosts a website, database, bot or application containing the customer's end users' data on an ongoing basis;
  * special category information, children's information or financial information is processed;
  * the customer requests one; or
  * the customer's own obligations, or those of its clients, require one.

To request a Data Processing Agreement, email <mattwright@districtstudio.xyz>.

### What a Data Processing Agreement will cover

A Data Processing Agreement will set out at least:

* the subject matter, duration, nature and purpose of processing;
* the types of personal information and categories of individuals;
* the customer's obligations and rights;
* the processor obligations in [Responsibilities](https://docs.districtstudio.xyz/for-customers/responsibilities.md);
* the sub-processors in [Security & sub-processors](https://docs.districtstudio.xyz/for-customers/security-and-sub-processors.md);
* transfer safeguards in [Security & sub-processors](https://docs.districtstudio.xyz/for-customers/security-and-sub-processors.md);
* retention and deletion terms in [Retention, deletion & incidents](https://docs.districtstudio.xyz/for-customers/retention-and-incidents.md); and
* breach notification terms in [Retention, deletion & incidents](https://docs.districtstudio.xyz/for-customers/retention-and-incidents.md).

### Customer-provided agreements

Customers may provide their own Data Processing Agreement. District Studio will review it and may propose changes where terms are not proportionate to the service.

## Contact

Questions about this document, requests for a Data Processing Agreement, sub-processor objections and incident reports should be sent to:

**Email:** <mattwright@districtstudio.xyz>

{% 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/data-processing-agreements.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.
