Joint Controller vs Data Processor
People think any second firm on a data project is a processor, and that is not so. A processor only follows the controller's orders. A joint controller helps decide why and how the data is used. Joint controllers need a written deal on who does what. Each one can be held to account. Calling a partner a processor does not change what it does.
Joint Controller
Two or more firms that decide side by side why and how data is used.
Joint controllers are firms that decide together why and how the same data is used. The GDPR covers them in Article 26. They must agree, in writing, who does which job under the law. That deal says things like who answers people's requests and who writes the notice. The main points of it must be shared with the people whose data it is. A person can still use their rights against any one of the firms.
Data Processor
A firm that holds people's data for someone else. It does only what it is told.
A data processor handles personal data for a controller, and only as it is told. Email tools, cloud hosts and pay firms are often processors. The GDPR asks for a written contract between the two. It is often called a data processing agreement. A processor may not use the data for its own goals. If it does, it becomes a controller too, with all the duties that come with that.
In one line
- Joint Controller
- Two or more firms that decide side by side why and how data is used.
- Data Processor
- A firm that holds people's data for someone else. It does only what it is told.