The data controller decides why personal data is processed and how, in essence. The data processor processes personal data on the controller’s behalf and follows its instructions. You do not decide the role once for your whole company: you assess it for each processing activity, so the same business is often a controller for one activity and a processor for another.
What does the GDPR say?
Article 4(7) GDPR defines the controller as the party that, alone or jointly with others, determines the purposes and means of the processing of personal data. Article 4(8) defines the processor as the party that processes personal data on behalf of the controller.
So a processor is always a separate organisation (or person) from the controller. Your own employees are not processors: they work under your authority as part of your organisation.
Who decides the purposes and the essential means?
The European Data Protection Board (EDPB) explains the difference in its Guidelines 07/2020 on the concepts of controller and processor. The controller decides the purpose (why) and the essential means:
- which personal data is processed;
- whose data it is (the categories of data subjects);
- who gets access to it;
- how long it is kept.
Non-essential means, such as the choice of software or the detailed security measures, may be left to the processor. A processor that picks its own tools is therefore still a processor, as long as it stays within the controller’s instructions.
Why is the role assessed per processing activity?
The GDPR looks at what happens with personal data in each activity, not at the type of company. A payroll bureau is a good example:
- For the payroll it runs for its clients, it is a processor. The employer decides who is paid, what amounts and how long the data is kept.
- For its own staff administration, its own customer relationship (contracts, invoicing) and its own marketing, it is a controller.
So list your activities one by one and record the role for each. Your register and your documents follow from that list.
Typical examples for small businesses
| Service provider | Usual role | Why |
|---|---|---|
| Payroll bureau | Processor | Pays salaries on the employer’s instructions and may not use the data for its own purposes (EDPB example). |
| Accountant or bookkeeper | Depends | Bookkeeping on detailed client instructions: processor. A statutory audit, where the profession’s rules decide which data is needed: controller (EDPB example). In Germany, tax advisers are by law always controllers for their clients’ data (§ 11(2) StBerG). |
| IT support or managed service provider (MSP) | Processor | Systematically has access to client systems full of personal data, even if that is not the main goal of the service (EDPB example). |
| Marketing agency | Usually processor | Sends your newsletter or runs your campaign to your audience on your instructions. If it reuses your contacts for its own purposes, it is a controller for that use. |
| Call centre | Processor | Handles your customer contacts with your customer data for your purposes only (EDPB example). |
| Cleaning company | Not a processor | Is not engaged to process personal data and only comes across it by accident. You protect your data with security measures and a confidentiality clause (EDPB example). |
The same reasoning applies to your own suppliers: when you hire one of these parties, you are the controller and they are your processor.
What must a processor do?
A processor has its own obligations under the GDPR:
- Sign a data processing agreement. Article 28(3) GDPR requires a contract or other legal act with the controller that covers the subject, duration, nature and purpose of the processing and the processor’s obligations. See What is a processing agreement?.
- Act only on documented instructions. The processor may not process the data for anything else. If it thinks an instruction breaks the GDPR, it must tell the controller immediately.
- Secure the data. The processor takes appropriate technical and organisational measures (Article 32) and makes sure its staff are bound to confidentiality.
- Get permission for sub-processors. A sub-processor needs the controller’s prior specific or general written authorisation, and the same obligations must be passed on by contract (Article 28(2) and 28(4)).
- Help the controller. The processor assists with data subject requests, security, breaches and DPIAs, and reports a personal data breach to the controller without undue delay (Article 33(2)).
- Delete or return the data at the end of the service, unless the law requires it to be kept.
- Keep a processor register. Article 30(2) requires a record of the processing carried out for each controller. Read more in GDPR register: do I need one?.
What stays with the controller?
The controller remains responsible for the processing as a whole (Article 24). In particular, the controller:
- chooses the legal basis under Article 6 (the processor has none of its own for this processing);
- informs data subjects in its privacy notice (Articles 13 and 14);
- handles data subject requests, such as access or erasure, with the processor’s help;
- chooses a processor that offers sufficient guarantees (Article 28(1)) and puts the agreement in place;
- notifies a breach to the supervisory authority where required (Article 33(1)).
Common mistakes
- Relying on the contract label. Calling yourself a processor in a contract does not make you one. The EDPB stresses that the role follows from the actual facts. Supervisory authorities such as the Belgian GBA/APD, the Dutch AP, the French CNIL and the German state authorities look at who really decides.
- Using client data for your own purposes. A processor that decides purposes and means itself is treated as a controller for that processing (Article 28(10)). Sending your own newsletter to your clients’ customers is a typical example.
- Thinking the GDPR is only the client’s problem. Processors have their own obligations, can be fined for breaching them and are liable for damage when they act outside their instructions (Article 82(2)).
- One role for the whole company. A firm that is a processor for its clients is still a controller for its own staff, customers and marketing.
- Forgetting the processor register. The Article 30(2) register is separate from the register of your own activities.
Do you provide software to your customers? The SaaS situation has its own nuances, explained in Are you a processor or controller as a SaaS provider?. How to record processes you carry out for customers in the app is described in How GDPRWise handles processes you carry out as a processor.
Template: Data Processing Agreement (DPA)
A starting point for the Article 28 agreement between you and your controller or processor.
View the templatearrow_forwardGDPRWise maps your processes per dossier and, where your sector supports it, lets you mark customer processes you carry out as a processor, so your register and privacy notice reflect what you actually do.