The upcoming General Data Protection Regulation (GDPR) has caused many companies intense compliance headaches due to its comprehensive scope, far-reaching obligations and severe penalties. However, the new rules have also brought about a range of new economic opportunities, in particular through the creation of the roles of Data Protection Officer (DPO) and EU-representative.
Both roles can be fulfilled by external parties if desired. If, for instance, a smaller company does not need a full-time DPO, it can outsource the role to a qualified market party on the basis of a service contract. A lively trade has already arisen in this arena, with various market parties offering these services. Although this must be seen as a welcome development, some questions regarding the legal implicationss of both roles remain unanswered. In a two-part blog post, we examine the respective roles, highlight some of the issues surrounding them, and attempt to provide some guidance.
The role of the DPO
Not all organizations that process personal data are required to appoint a DPO. Article 37(1) GDPR only makes the officer a mandatory requirement for public authorities, organisations that process large amounts of sensitive data (such as medical records), and organisations that engage in ‘regular and systematic monitoring of data subjects on a large scale’, of which a classic example would be behavioural advertising.
Even those who are not strictly required to appoint a DPO may consider bringing one in. This is already happening in some European countries: in France, for instance, appointing a data protection officer is not (yet) mandatory, but doing so exempts the organisation from having to make declarations to the national data protection authority (CNIL).
The DPO, whose role is set out in articles 37 – 39 GDPR, is designed by the legislator to be simultaneously an independent monitor responsible for ensuring GDPR compliance, an educator of employees and management on data protection practices, and the contact person for both data subjects and the relevant data protection authority. He reports to “the highest level of management” (art. 38) of the processor or controller, which is generally presumed to be the C-suite or board.
A key aspect of the DPO is his independence, which means he cannot receive instructions from management on how to do his job, and cannot be dismissed for doing said job properly, and art. 37 stipulates that the DPO should be “designated on the basis of professional qualities, in particular with regard to the tasks listed in art. 38″; a requirement which is expanded on further in the relevant guidelines issued by the Article 29 Working Party.
As mentioned earlier, the GDPR allows for appointing an external DPO. This can be a particularly cost-effective solution for a smaller company that is obligated to appoint a DPO, but does not require one on a full-time basis. The question remains, however, whether an external DPO can maintain his independence and special status if he is performing these duties as part of a wider range of tasks on behalf of the controller. Herein lies a looming risk of a potential conflict of interest.
Controller or Processor?
One question that seems to have evaded the attention of the legislators, the Working Party, and most commentators is this: what happens to the legal position of the external DPO when he receives personal data on behalf of the controller or processor in the performance of his duties? It is clear that the mere act of receiving and holding this data qualifies as processing it for the purposes of the GDPR (art. 4(2)), and there are no exceptions or special regimes for the DPO role. Thus, the external DPO must be either a controller or processor. Which is it?
A processor may only process data according to the instructions given by the controller (art. 28(3)(a)). The DPO, however, cannot receive instructions regarding the exercise of his tasks (art. 38(3)). This contradiction almost certainly rules out the possibility of the DPO being a processor, and so the external DPO in all likelihood becomes a data controller by default.
The above is supported by the 2010 Working Party guidelines on controllers and processors, in which the reaonably analogous position of the accountant is described in similar terms: if working as an employee, he is a processor; as an external service provider, he can only be a data controller.
What is the practical significance of all this? Firstly, it means that a processing agreement must be made between the controller/processor and the external DPO as part of the latter’s service contract. This agreement should, among others, make it clear what security measures the DPO is to take, and how he is to act in the event of a data breach.
Secondly, although the DPO cannot be held liable for the controller or processor’s unlawful processing of data, this can theoretically change if he becomes a controller in his own right, meaning that – in the absence of further guidance – the DPO could be liable for administrative fines and civil law damages in respect of his own handling of the data.
To summarise: it is imperative for both those offering external DPO services and those seeking to engage them to consider – and contract for – this issue, by acknowledging and defining the position of the DPO as a data controller, by ensuring the DPO’s independence remains unquestionable, and by having clear procedures in place for unforeseen calamities.
All posts by Judica Krikke
Joe Jay de Haas
All posts by Joe Jay de Haas