Data controller or data processor – what is the difference?
If a company processes personal data together with a supplier, the parties must first understand their GDPR roles. It is the actual processing and who determines the purposes and means that govern – not the label the parties happen to write in the agreement.
What is a data controller?
The data controller determines the purposes and essential means of the processing of personal data. In a normal customer relationship, it is, for example, the company that determines why customer data is collected, what data is needed, and how long it should be used.
It is normally the organization that is the data controller – not the individual employee, manager, or system owner who works with the data.
What is a data processor?
A data processor processes personal data on behalf of the data controller and exists outside of the controller's organization. The Swedish Authority for Privacy Protection (IMY) mentions, for example, companies that store data or handle mailings for a client, as well as cloud service companies that process and store personal data for the customer.
The processor may process data according to the data controller's documented instructions and simultaneously has its own obligations under GDPR, including regarding security and, in some cases, records of processing activities and data protection officers.
Three examples
| Situation | Likely role distribution |
|---|---|
| A company uses a cloud service to store its customer register. | The company is normally the controller for the customer processing, and the cloud provider is the processor for the processing it performs for the customer. |
| An accounting firm processes data for the customer but also has its own legal obligations for certain processing. | Roles can differ between different types of processing. The same supplier can be a processor in one process and an independent controller in another. |
| Two organizations jointly determine why and how a processing activity should take place. | Joint controllership may apply instead of a controller-processor relationship. |
When is a data processing agreement (DPA) needed?
When a data controller engages a data processor, the processing must be regulated by a contract or other legal act according to GDPR Article 28. The contract must, among other things, regulate the subject matter and duration of the processing, the nature and purpose, the type of personal data, the categories of data subjects, and the parties' rights and obligations.
The processor may not freely engage sub-processors. IMY states that prior authorization is required, and the obligations must be passed on in the relationship with the sub-processor.
See our in-depth guide: Data Processing Agreements (DPA) – when are they needed and what should they include?
When is it not a processor relationship?
The fact that two companies exchange personal data does not automatically mean that one is a processor. If both independently determine their own purposes, both can be separate data controllers. If they jointly determine purposes and means, joint controllership may apply.
The practical control question is therefore: Who determines why the data is processed and the essential framework for how the processing takes place? The contract heading should reflect reality, not create a role that the parties do not have in practice.
Do you need a DPA?
Mallbutiken's DPA template 2026 is developed for GDPR Article 28 and includes, among other things, instructions, security, sub-processors, incidents, erasure, and third-country issues.
Price: 99 SEK.
See DPA Template Package 2026Related guides
SaaS agreements – what should the agreement contain? · SLA in SaaS agreements · AI, cybersecurity, and IT agreements
For associations, there is a special practical application in our guide on membership registers and GDPR.
The data controller must also handle requests for access to personal data. See our guide to GDPR access requests and data subjects' rights.
Sources
The controller must also establish a valid legal basis. Where legitimate interests are considered, read our guide to legitimate-interest assessments (LIA) under GDPR. Document the purpose, necessity and balancing of the individual's interests, as explained by the Swedish Privacy Protection Authority (IMY).
See also guide to GDPR data protection officers and when to appoint one.
Templates in this article
Explore the topic
Business guides – contracts, HR, AI & complianceData Processing Agreement – when is it needed and what should it include?
Determine whether a supplier is a data processor and what the data processing agreement needs to regulate. Practical examples, appendices, and chec...
Business guides – contracts, HR, AI & complianceSaaS agreement – what should the agreement include? 12 questions to regulate
What should a SaaS agreement contain? Go through the service, SLA, support, data, GDPR, security, liability, price, changes, termination, and exit.
Business guides – contracts, HR, AI & complianceSLAs in SaaS agreements – availability, response time, RTO, RPO, and service credits
Practical guide to SLAs for SaaS: availability, incident levels, response time, RTO/RPO, service credits, maintenance, and escalation.



