Short Reads

The External DPO: Controller or Processor?

The External DPO: Controller or Processor?

The External DPO: Controller or Processor?

10.04.2018 NL law

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.

1. 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.

2. 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.

Team

Related news

24.01.2020 NL law
Can the government refrain from imposing enforcement measures if it is not within the offender’s power to comply with a standard?

Short Reads - What should be done if a stakeholder makes a request to the government for enforcement to rectify violations in a scenario where the offender does not have full power to comply because of a reliance on third parties? The Administrative Division of the Dutch Council of State ruled on 23 January 2019 that an administrative body cannot simply reject an enforcement request in such a situation, but must consider whether, for example, the imposition of an order subject to a penalty payment may provide an incentive for the actual termination of the violation.

Read more

20.01.2020 NL law
Planologische medewerking mag worden geweigerd als initiatiefnemer zich in strijd met gemeentelijk beleid onvoldoende heeft ingespannen voor draagvlak

Short Reads - De Afdeling bestuursrechtspraak van de Raad van State heeft op 18 december 2019 (ECLI:NL:RVS:2019:4209) overwogen dat een bestuursorgaan geen planologische medewerking hoeft te verlenen aan de wijziging van een bestemmingsplan als de aanvrager zich niet heeft ingespannen om maatschappelijk draagvlak te creëren.

Read more

16.01.2020 NL law
De Amsterdamse milieuzone voor brom- en snorfietsen: voertuigen van een bepaald jaar weren is mogelijk bij ontbreken van een redelijk alternatief

Short Reads - ABRvS 20 november 2019, ECLI:NL:RVS:2019:3865 Deze blog is het vierde deel in een reeks Stibbeblogs over gemeentelijke milieuzones. In 2017 oordeelde de Afdeling over de milieuzone voor personen- en bestelauto’s met dieselmotoren in Utrecht. In 2018 presenteerde de staatssecretaris van Infrastructuur en Waterstaat haar beleid voor harmonisatie van uiteenlopende gemeentelijke milieuzones. Een jaar geleden maakten wij in een FAQ de balans op over de harmonisatie van milieuzones.

Read more

16.01.2020 BE law
24 January 2020: Carol Evrard participates in a panel session on Global Compliance at the CPDP conference in Brussels

Speaking slot - Stibbe is a long standing partner of the International Computers, Privacy and Data Protection Conference (CPDP) which takes place in Brussels between 22 and 24 January 2020 This year's theme is “Data protection and Artificial intelligence”. Carol Evrard, associate in our TMT team, participates in a panel organised by TrustArc (a privacy compliance technology company based in San Francisco, California) on "Changing Technology and Laws: Can Accountability be a Key to Global Compliance?"

Read more

Our website uses functional cookies for the functioning of the website and analytic cookies that enable us to generate aggregated visitor data. We also use other cookies, such as third party tracking cookies - please indicate whether you agree to the use of these other cookies:

Privacy – en cookieverklaring