{"id":17413,"date":"2021-10-15T12:12:06","date_gmt":"2021-10-15T11:12:06","guid":{"rendered":"https:\/\/www.rosello-mallol.com\/?p=17413"},"modified":"2022-02-24T12:47:38","modified_gmt":"2022-02-24T11:47:38","slug":"data-protection-officer-do-i-need-it","status":"publish","type":"post","link":"https:\/\/www.rosello-mallol.com\/en\/data-protection-officer-do-i-need-it\/","title":{"rendered":"Data Protection Officer: do I need it?"},"content":{"rendered":"\n

Almost 7 years have passed since I spoke<\/a><\/strong> on this blog about the need (or not) for a Data Protection Officer (DPO)<\/strong>. Many things have happened since January 2015, and beyond defining the cases in which a DPO is legally required, I want to focus on the day to day of your Officer, if you have appointed one or are thinking of doing so.<\/p>\n\n\n\n

What does the law say?<\/strong><\/h2>\n\n\n\n

Both the GDPR <\/a><\/strong>and the LOPD<\/a><\/strong> provide for specific cases in which a DPO must be appointed<\/strong>. If your company or activity is included in these cases, end of discussion, you really need a DPO. <\/p>\n\n\n\n

Articles 37.1 of the GDPR and 34 of the LOPD, respectively, define these assumptions: I want to pause here to discuss the effective role of the DPO in your company beyond completing the procedure. It should be noted, however, that the DPO can be appointed on a voluntary basis<\/strong>, outside the cases marked by law and that, in fact, this circumstance can be taken into account as a mitigating factor<\/strong> in the event of penalty proceedings.<\/p>\n\n\n\n

What do you need to know if you appoint a Data Protection Officer?<\/strong><\/h2>\n\n\n\n