{"id":1589,"date":"2018-01-17T19:08:55","date_gmt":"2018-01-17T19:08:55","guid":{"rendered":"https:\/\/crigroup.com\/?post_type=blog&p=1589"},"modified":"2022-11-14T15:27:55","modified_gmt":"2022-11-14T15:27:55","slug":"gdpr-data-protection-officer","status":"publish","type":"post","link":"https:\/\/crigroup.com\/ar\/gdpr-data-protection-officer\/","title":{"rendered":"Appointment of Data Protection Officer under GDPR"},"content":{"rendered":"

There is the growing misconception surrounding the need for appointing a Data Protection Officer (DPO) under GDPR which is effective on 25th May 2018. The role of DPO is critical for correct implementation of the newly drafted regulation. Relating to this, the organisation needs to ask itself four main questions before appointing a DPO which are:<\/p>\n

    \n
  1. Do they even need to appoint a DPO?<\/li>\n
  2. Should they need a DPO anyway for safe measures of compliance?<\/li>\n
  3. Can the role of DPO be outsourced?<\/li>\n
  4. Will the DPO be personally liable?<\/li>\n
  5. When should a DPO be appointed?<\/li>\n<\/ol>\n

    I will start by answering the first question. According to article 37(1), GDPR requires data controllers and processors to designate a DPO in any case where:<\/p>\n