Data Protection Officer vs Data Controller
People think the DPO answers for a firm's data, and that is not so. The controller is the firm that decides why the data is used. It carries the legal duty. The DPO is a person inside the firm who checks and advises, and takes no orders on what to find. When the rules are broken, the watchdog fines the controller, not the DPO.
Data Protection Officer (DPO)
The person inside a firm who checks it keeps to data law. Nobody may tell them what to find.
A data protection officer is the person who checks that a firm follows data protection law. Article 37 of the GDPR makes one a must in three cases. These are public bodies, firms whose main work is tracking people on a large scale, and firms whose main work uses sensitive data on a large scale. The DPO advises, trains staff and talks to the regulator. The firm may not tell the DPO what to conclude. It may not fire the DPO for doing the job either.
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.
In one line
- Data Protection Officer (DPO)
- The person inside a firm who checks it keeps to data law. Nobody may tell them what to find.
- Data Controller
- The one who decides why and how personal data is used. It answers for the data.