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

# Responsibilities

What District Studio does as a processor, and what you are responsible for as controller.

## District Studio's responsibilities as a processor

When acting as a processor, District Studio will:

1. process personal information **only on the customer's documented instructions**, including those in the project brief, quote, order, configuration of the service, or written messages;
2. tell the customer if, in District Studio's opinion, an instruction would breach data protection law;
3. ensure that anyone authorised to process the information is subject to **confidentiality** obligations;
4. take **appropriate security measures** as described in [Security & sub-processors](https://docs.districtstudio.xyz/for-customers/security-and-sub-processors.md);
5. engage **sub-processors** only as described in [Security & sub-processors](https://docs.districtstudio.xyz/for-customers/security-and-sub-processors.md);
6. **assist the customer** in responding to rights requests, so far as reasonably possible ([Retention, deletion & incidents](https://docs.districtstudio.xyz/for-customers/retention-and-incidents.md));
7. **assist the customer** with security, breach notification, data protection impact assessments and prior consultation with the ICO, taking into account the information available to District Studio;
8. **delete or return** personal information at the end of the service, as the customer chooses, unless the law requires retention ([Retention, deletion & incidents](https://docs.districtstudio.xyz/for-customers/retention-and-incidents.md));
9. make available information reasonably necessary to **demonstrate compliance**, and allow for and contribute to reasonable audits or inspections, subject to confidentiality and reasonable notice; and
10. **notify the customer without undue delay** after becoming aware of a personal data breach affecting the customer's data ([Retention, deletion & incidents](https://docs.districtstudio.xyz/for-customers/retention-and-incidents.md)).

These obligations reflect UK GDPR Article 28(3).

District Studio will not:

* sell customer data;
* use customer data for its own marketing;
* disclose customer data to third parties except sub-processors, or where required by law; or
* access customer data beyond what is needed for the task.

## Customer responsibilities as a controller

The customer is responsible for:

### Lawful basis and transparency

* identifying a **lawful basis** for processing its end users' information, and an Article 9 condition if special category information is collected;
* providing a **privacy notice** to its end users — for example, informing Discord server members that a bot logs moderation actions or stores application answers, or informing website visitors how their data is used;
* obtaining any **consent** required, including for cookies under PECR on websites it controls.

### Data minimisation and configuration

* configuring services to collect **only what is necessary** — for example, not asking for unnecessary personal details in application forms;
* not instructing District Studio to collect special category information unless it has a lawful basis and condition, and has told District Studio;
* setting **retention** periods for logs, transcripts and records it controls where the service allows this.

### Access and accounts

* controlling who in its organisation or community can access data held in the service — for example, which Discord roles can view tickets or applications;
* giving District Studio **only the access it needs**, preferably through separate, limited accounts;
* **revoking** District Studio's access and rotating shared credentials when work is complete.

### Credentials and files

* sending credentials and files through the secure method agreed with District Studio, not through public channels;
* removing unnecessary personal information from files before sending them where practical (for example, providing a database schema or a test database rather than a full live export where that is enough for the task).

### Children

* assessing whether its server, website or service is likely to be accessed by children and complying with the ICO's Age Appropriate Design Code where it applies;
* applying age requirements of the platforms it uses, such as Discord.

### Rights requests and complaints

* responding to rights requests and complaints from its own end users. District Studio will assist as set out in [Retention, deletion & incidents](https://docs.districtstudio.xyz/for-customers/retention-and-incidents.md).

### Third-party platforms

* complying with the terms of the platforms it uses, including Discord's Developer Terms and policies, Cfx.re/FiveM terms, Tebex terms and hosting provider terms.

## Customer instructions

The customer's instructions are given through:

* the agreed **quote, brief or specification**;
* the **configuration** of the service, such as bot dashboard settings;
* **written instructions** by email or in a support ticket from an authorised person.

Instructions that change the scope of processing, such as collecting new categories of information or sending data to a new third party, should be given in writing. District Studio may decline instructions that are unlawful, outside the agreed scope or that would compromise the security of its services. Changes to scope may be subject to additional charges.

District Studio may treat the person who placed the order, or the owner of the Discord server, as authorised to give instructions unless told otherwise.

## Data access

District Studio accesses customer data only:

* to carry out agreed development, hosting, maintenance or support;
* to investigate and fix errors or security incidents;
* where the customer asks it to; or
* where required by law.

Access is limited to the people who need it for the task.

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