> For the complete documentation index, see [llms.txt](https://docs.assenteo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.assenteo.com/key-legislation/the-gdpr/is-your-business-a-data-controller-or-a-data-processor.md). # Is your business a data controller or a data processor? ### Contents * [1. What is a data controller?](#id-1.-what-is-a-data-controller) * [2. What is a data processor?](#id-2.-what-is-a-data-processor) ### 1. What is a data controller? If your business is **making decisions** about **what** personal data is processed, **why** it is processed, and **how** it is processed, then it is likely a **data controller** under the [GDPR](/key-legislation/the-gdpr.md). * For example, if your business runs an app which collects patient symptoms to provide health recommendations, you decide **what** data to collect, **why** to collect it and **how** to collect it. This makes your business a **data controller**. ### 2. What is a data processor? If your business performs operations on personal data **on behalf** of a data controller (who has made the decisions about the whys and hows of that processing), it is a **data processor** under the [GDPR](/key-legislation/the-gdpr.md). * For example, if hospitals use your platform to store patient records, your business is processing personal data **on their behalf**. This makes your business a **data processor**. In practice, given the broad definition of processing, if your business is a data controller it is likely also a data processor. However, the processor role under the GDPR is really designed to capture a separate entity that processes personal data on the controller’s behalf. * For example, if your app analyses patient symptoms using a third-party AI system, that AI system provider is working as your data processor. Data processors might also engage third parties to assist with data processing on behalf of the originaln controller. These entities are known as **subprocessors** under the GDPR. [Here](/key-legislation/the-gdpr/subprocessors-and-vendors.md), we explore the role and obligations of subprocessors and their linked controllers. --- # 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.assenteo.com/key-legislation/the-gdpr/is-your-business-a-data-controller-or-a-data-processor.md?ask=&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.