> 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/retention-and-incidents.md).

# Retention, deletion & incidents

Deleting customer data, handling security incidents and helping with rights requests.

## Data retention and deletion

### During the service

District Studio keeps customer data for as long as needed to provide the service, or as configured by the customer.

### At the end of the service

When a project ends, a hosted service is cancelled, a bot is removed from a server, or the customer asks, District Studio will, at the customer's choice:

* **return** the customer data in a commonly used format where reasonably possible; and/or
* **delete** the customer data from its live systems.

Unless otherwise agreed, District Studio will delete customer data from live systems within 30 days after the end of the service. Copies in backups are deleted when those backups are replaced on their normal rolling schedule.

Credentials provided for a project are deleted when the project is complete.

### Bot removal

When the District Studio bot is removed from a Discord server, server-specific configuration and records held by District Studio are deleted within 30 days, except records District Studio holds as controller (such as subscription and billing records).

### Legal retention

District Studio may retain data where required by law. It will keep such data confidential and process it only for that purpose.

## Security incidents

If District Studio becomes aware of a personal data breach affecting customer data, it will:

1. notify the customer **without undue delay** — District Studio aims to do so within 48 hours of becoming aware, so that the customer can meet the 72-hour ICO reporting deadline where it applies;
2. provide, as far as available, a description of the breach, the categories and approximate number of people and records concerned, the likely consequences and the measures taken or proposed;
3. take reasonable steps to contain the breach and reduce its effects;
4. co-operate with the customer's investigation; and
5. not notify the customer's end users or the ICO on the customer's behalf unless the customer asks or the law requires it.

The customer, as controller, is responsible for deciding whether to notify the ICO and affected individuals.

If the customer becomes aware of a security incident affecting systems District Studio has access to — for example a compromised Discord administrator account or server panel — the customer should tell District Studio promptly so that access can be reviewed.

## Assistance with rights requests and compliance

If District Studio receives a rights request from an end user relating to customer data, it will:

* not respond to the substance of the request unless the customer authorises it or the law requires it;
* pass the request to the customer without undue delay where it can identify the customer; and
* help the customer respond, for example by exporting or deleting records held by the service.

District Studio may charge a reasonable fee for assistance that goes beyond standard service functionality. We will tell you about any fee before starting the work.

{% 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/retention-and-incidents.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.
