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

# Data retention

How long we keep information, and how it is deleted.

## Our approach

We keep personal information only for as long as we need it for the reason we collected it. That includes meeting legal, accounting and reporting obligations, and dealing with any legal claims. When we no longer need it, we delete or anonymise it.

## How we decide how long to keep information

| Type of record                                 | How long we keep it                                                                                 |
| ---------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Customer accounts and dashboards               | While the account is active, then deleted or anonymised after it is closed.                         |
| Discord bot records we control                 | While the bot or service is in use, then deleted.                                                   |
| Discord bot records we hold for a server owner | As the server owner sets it up, and deleted when the bot is removed or the service ends.            |
| Support tickets and transcripts                | While the request is open, and for a limited time afterwards in case the issue comes back.          |
| Applications through our own systems           | Until a decision is made and recorded, then deleted.                                                |
| Purchase, licence and entitlement records      | For as long as the licence or product support lasts, and as long as tax law requires.               |
| Accounting and tax records                     | For as long as HMRC record-keeping rules require.                                                   |
| Project records and deliverables               | For the aftercare period, and as long as needed to deal with any legal claims.                      |
| Files you send us                              | Deleted after the project and aftercare period end.                                                 |
| Access credentials                             | Deleted as soon as the work is complete.                                                            |
| Technical and access logs                      | A short period for security and troubleshooting, then deleted automatically.                        |
| Backups                                        | Replaced on a rolling basis.                                                                        |
| Security and incident records                  | As long as needed to investigate and prevent repeat incidents, and to show we met our legal duties. |
| Marketing opt-out records                      | As long as needed to respect your choice.                                                           |
| Subscription information                       | While active, and for a short period after it ends.                                                 |

## Deletion requests, closed accounts and ended subscriptions

* **Deletion requests** are handled as explained in [Your rights](https://docs.districtstudio.xyz/privacy-policy/your-rights.md).
* **Closed accounts:** when you close an account, we delete or anonymise its information, except records we must keep by law, such as purchase and accounting records.
* **Ended subscriptions:** see [Subscriptions & memberships](https://docs.districtstudio.xyz/privacy-policy/how-we-use-information/subscriptions.md).
* **Legal holds:** we may keep information for longer where we need it to comply with the law, settle a dispute, prevent fraud or deal with a legal claim.

## Backups and expired records

Information deleted from our live systems may stay in backups until those backups are replaced. We do not use backups to bring back deleted personal information, except to recover from an incident. If we do, we delete that information again. We review stored records regularly and remove those we no longer need.

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