Data Controller vs Data Processor
People think whoever holds the data is in charge of it, and that is not so. The controller decides why and how the data is used, and answers for it under the law. The processor only works on the data as the controller says, under a contract. An email tool that sends your newsletter is a processor. If it used your list for its own ads, it would turn into a controller too.
Data Controller
The one who decides why and how personal data is used. It answers for the data.
A data controller is the person or firm that decides why and how personal data is used. Under the GDPR, the controller has the main duty to follow the law. A brand that runs a newsletter is the controller of its list. It answers people's requests and picks the lawful basis. It must also pick helpers that keep the data safe.
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
- Data Controller
- The one who decides why and how personal data is used. It answers for the data.
- Data Processor
- A firm that holds people's data for someone else. It does only what it is told.