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

# Lawful bases

The legal grounds we rely on to use personal information.

UK data protection law requires a lawful basis for each use of personal information. We do not rely on every basis for every activity. These are the main bases we rely on as a controller.

| Lawful basis                                           | What it means                                                                                                                     | When we rely on it                                                                                                                                                                                                                                                                                                                         |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Contract** (UK GDPR Article 6(1)(b))                 | Needed to carry out a contract with you, or to take steps you ask for before one.                                                 | Quotes, orders, commissions, product delivery, licences, subscriptions, dashboard accounts, projects and support.                                                                                                                                                                                                                          |
| **Legal obligation** (Article 6(1)(c))                 | Needed to comply with the law.                                                                                                    | Tax and accounting records; lawful requests from the authorities; handling your rights requests; reporting breaches.                                                                                                                                                                                                                       |
| **Legitimate interests** (Article 6(1)(f))             | Needed for our legitimate interests, or someone else's, where your rights do not override them.                                   | Website and service security; preventing fraud and abuse; enforcing licences; answering enquiries from people who are not yet customers; improving our services; keeping records to defend legal claims; some marketing to existing customers ([Marketing & communications](https://docs.districtstudio.xyz/privacy-policy/marketing.md)). |
| **Recognised legitimate interests** (Article 6(1)(ea)) | A basis added by the Data (Use and Access) Act 2025 for specific purposes such as preventing crime, safeguarding and emergencies. | Only where one of those purposes genuinely applies, for example sharing information with the police to help prevent a crime.                                                                                                                                                                                                               |
| **Consent** (Article 6(1)(a))                          | You have given clear, specific and informed agreement.                                                                            | Non-essential cookies; marketing where the soft opt-in does not apply; showing your work in our portfolio. You can withdraw consent at any time.                                                                                                                                                                                           |
| **Vital interests** (Article 6(1)(d))                  | Needed to protect someone's life.                                                                                                 | Only in rare emergencies, such as a support message suggesting someone is at risk.                                                                                                                                                                                                                                                         |
| **Public task** (Article 6(1)(e))                      | Needed for a task in the public interest or an official function.                                                                 | Not normally used by District Studio.                                                                                                                                                                                                                                                                                                      |

Where District Studio is a processor, the customer, as controller, is responsible for choosing the lawful basis.

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