Quick answer
Under the GDPR, a data controller decides the purposes and means of processing personal data, and a data processor processes it on the controller's behalf and instructions. Roles follow what a party actually does, so a processor that sets its own purposes becomes a controller for that processing.
Data controller vs data processor: the short answer
Under the GDPR, a data controller is the party that, alone or jointly with others, determines the purposes and means of processing personal data (Article 4(7)). A data processor is a party that processes personal data on behalf of the controller (Article 4(8)). In plain terms, the controller decides why and how the data is used; the processor does the work on the controller's instructions.
The distinction is about what a party actually does, not what it is called. This page explains the concepts and is not legal advice. The wording follows the GDPR; other laws use other labels and tests, so check the one that applies to you.
Controller vs processor at a glance
| Question | Controller | Processor |
|---|---|---|
| Who decides why the data is processed? | The controller | Never; it acts on the controller's documented instructions (Art. 28(3)(a)) |
| What must the controller or processor have in place? | Only use processors that give sufficient guarantees (Art. 28(1)) | A binding contract or other legal act covering subject-matter, duration, nature and purpose, data types and categories of data subjects (Art. 28(3)) |
| Can the work be passed on to someone else? | Must authorise it | Cannot engage another processor without prior written authorisation, specific or general (Art. 28(2)); stays fully liable to the controller for it (Art. 28(4)) |
| What happens at the end of the service? | The controller chooses | Deletes or returns all personal data at the controller's choice (Art. 28(3)(g)) |
| Who is liable for damage? | Any controller involved in the processing (Art. 82(2)) | Only where it broke obligations aimed at processors or acted outside or against lawful instructions (Art. 82(2)) |
| What if the processor sets its own purposes? | It becomes the controller of that processing | Considered a controller in respect of that processing (Art. 28(10)) |
How to tell which one you are
Ask two questions about a specific processing activity: why is it happening, and who decided that it should? The European Data Protection Board (EDPB) calls the two roles functional concepts. The role depends on the actual activities of the parties in a specific situation, not on the label in a contract (Guidelines 07/2020, paragraph 12).
For the "how", the EDPB separates essential means from non-essential means (paragraph 40). Essential means are reserved to the controller; non-essential means can be left to the processor.
| Decision | Who normally makes it |
|---|---|
| Which personal data is processed | Controller (essential means) |
| For how long it is kept | Controller (essential means) |
| Who has access to it | Controller (essential means) |
| Whose data it is (which categories of data subjects) | Controller (essential means) |
| Which hardware, software or detailed security measures to use | Can be left to the processor (non-essential means) |
Sample scenarios, based on the GDPR text and the examples in the EDPB guidelines. They are illustrations, not legal conclusions for your case.
| Scenario | Role of the service provider | Why |
|---|---|---|
| An online shop uses an analytics service to count its own visitors | Processor | The shop decides the purpose and the data; the provider only delivers the shop's reports |
| The same provider also builds its own advertising profiles from the shop's visitor data | Controller for that extra use | It added a purpose of its own (Art. 28(10); the EDPB gives a similar marketing-agency example in paragraph 81) |
| A company outsources payroll to a firm that chooses its own software | Processor | Choosing software is a non-essential means (EDPB payroll example) |
| That payroll firm passes salary data to a bank to make the payments | The bank is a controller for its banking activity | The bank decides independently which data it needs and how long to keep it (EDPB bank example) |
| A cloud host stores a customer's files only on that customer's instructions | Processor | It does not process the data for its own purposes (EDPB cloud example) |
| Two companies jointly decide the purpose and means of one campaign database | Joint controllers | Article 26(1): where two or more controllers jointly determine purposes and means, they are joint controllers |
What an analytics vendor needs to be a processor
An analytics vendor is usually a processor for the data it collects on your website, because you decide that it should be collected and for what. It stays a processor only while its activity matches that. Four checks before you sign:
| Check | What to look for |
|---|---|
| Purposes | The vendor uses your data only to deliver your service. Read what it says about its own uses, such as benchmarks, product improvement, advertising or model training: anything beyond your instructions is where Art. 28(10) applies |
| Contract | A data processing agreement (DPA) covering Art. 28(3)(a)–(h): documented instructions, staff confidentiality, security under Art. 32, conditions for other processors, help with data-subject requests, help with Arts. 32–36, deletion or return at the end, and information for audits |
| Other processors | A list of the vendor's sub-processors and a notice before it adds one (Art. 28(2)) |
| Your tools | A way to delete, export and set retention yourself, so the instructions you give can be carried out |
Common mistakes
- Treating the contract label as the answer. Calling a vendor a "processor" in a contract does not make it one. The role follows the actual activities (EDPB paragraph 12).
- Assuming a processor carries less risk. A processor is liable when it breaks obligations aimed at processors or acts outside lawful instructions (Art. 82(2)), and one that sets its own purposes becomes a controller (Art. 28(10)).
- Giving a company one role for everything. The EDPB notes that the same entity can be a controller for some operations and a processor for others (paragraph 82). A software vendor is typically a controller for its own customer accounts and a processor for its customers' end-user data.
- Thinking the controller must see the data. A controller does not need access to the data to be a controller. A market-research client who only receives statistics can still be the controller.
- Treating a signed DPA as the finish line. Art. 28(1) puts a duty on the controller to choose processors with sufficient guarantees. The contract is part of that, not a replacement for data governance inside your own company.
- Collecting more than the purpose needs. Which data to collect is an essential means, so it is yours to decide and to limit; see data minimization.
For the wider rule set these roles come from, see GDPR.
Controller and processor in TapCub
Say you run an online shop and add the TapCub script. Who is who?
- For your visitors, you are the controller and TapCub is the processor. TapCub's privacy policy says it processes visitor data only on the customer's instructions, under its terms and a data processing agreement that is available on request. The terms add that visitor data belongs to you and that you are responsible for your notices to visitors and any consent your jurisdiction requires.
- For its own account data, TapCub is the controller. The same policy lists the people for whom TapCub decides why and how data is processed: people who register an account, are invited as members or agents, contact TapCub or browse its own website. One company, two roles, as in the mistakes above.
- Your instructions become settings. In Configuration › Privacy center you set the collection tier, whether consent is required by region, address truncation and retention. Data-subject requests (access, erasure, restrict, portability) can be created from the console.
- Ask for the DPA and the sub-processor list. Both are available on request. The privacy policy says customers with a DPA are told before a sub-processor is added, and the chat privacy page, which covers what visitors type into chat, adds notice within 72 hours of a breach that affects your data.
- Read the own-use wording. The terms say TapCub never sells visitor data, never uses it for advertising and never uses conversation content to train AI models. They also say TapCub may use aggregated, de-identified usage statistics to operate and improve the service. Whether that fits your own analysis is a question for the DPA and your own counsel.
Sources
- European Union, Regulation (EU) 2016/679 (GDPR), Articles 4(7), 4(8), 26(1), 28 and 82(2).
- European Data Protection Board, Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.1, adopted 7 July 2021.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Engineer
Writes about event design, data quality, and collection workflows, with verifiable implementation methods for reliable analytics.