> 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/security-and-breaches.md).

# Security & data breaches

How we protect information, and what we do if something goes wrong.

## How we protect information

### Our commitment

District Studio uses technical and organisational measures that suit the level of risk, to protect personal information against unauthorised access, loss, change and disclosure. No system is completely secure, and we cannot promise a breach will never happen, but we work to reduce that risk.

### Security measures

Depending on the system, our measures include:

* limiting access to personal information to people who need it;
* using strong, unique passwords and additional sign-in security on business accounts;
* encrypting connections to our websites (HTTPS);
* using encryption at rest where our providers support it;
* restricting access to databases;
* keeping secrets, such as passwords and tokens, out of source code;
* applying security updates to servers, software and devices;
* taking backups;
* keeping files secure when we store or share them; and
* deleting information and wiping devices securely when they are no longer needed.

District Studio does not hold a security certification.

### Your credentials

If you give District Studio access credentials, we keep them private, use them only for the agreed work, and delete them when the work is finished. We recommend you change any shared passwords once the work is done.

## Personal data breaches

A personal data breach is a security incident that causes personal information to be accidentally or unlawfully destroyed, lost, changed, disclosed or accessed.

If a breach happens, District Studio will:

1. **Identify** it, and record when we became aware of it.
2. **Investigate** what happened and what information is affected.
3. **Contain** it, for example by removing access or taking systems offline.
4. **Assess the risk** to the people affected.
5. **Tell the people affected** without undue delay, where the breach is likely to put their rights and freedoms at high risk.
6. **Report it to the ICO** within 72 hours of becoming aware, where it is likely to put people's rights and freedoms at risk.
7. **Fix** the cause, and take steps to stop it happening again.
8. **Record** the breach, its effects and what we did, whether or not it had to be reported.

Where District Studio is a processor, we tell the customer without undue delay so they can meet their own obligations. See [Data Processing & Customer Responsibilities](https://docs.districtstudio.xyz/for-customers/customer-data-processing.md).

If you think information District Studio holds about you has been misused or exposed, please tell us straight away ([Contact & complaints](https://docs.districtstudio.xyz/privacy-policy/contact-and-complaints.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/security-and-breaches.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.
