Although organizations in the United States have dealt with privacy issues for years, only in the past decade have they begun to view the complexities of privacy as requiring formal organizational structure and, in some cases, one, or more, dedicated employees. While in some organizations “data privacy” and “data security” falls within the ambit of the legal department, other organizations have created offices that are focused solely on privacy issues. There is little commonality in how these offices are staffed, funded, or organized. For example, while some organizations have “Chief Privacy Officers” or “Chief Information Technology Officers” that report directly to senior management, other organizations have privacy officers that report through a General Counsel or to a Chief Compliance Officer.

Like the United States, the appointment of a privacy officer was not required under the EU Privacy Directive. Unlike the United States, some individual member states – most notably Germany – enacted legislation that went beyond the requirements of the EU Privacy Directive required that most businesses that operated in that country appoint a data protection officer.

The EU’s new General Data Protection Regulation (“GDPR”) adopts the German concept that a data-heavy company must appoint a data protection officer. In addition, the GDPR purports to apply the requirement to data-heavy United States companies that process personal information and (1) intend to offer products or services to people in the EU, or (2) monitors people in the EU.1 Specifically the GDPR requires:

  • All companies that process data as a “core activity” and that engage in “regulator and systematic monitoring of data subjects on a large scale” must appoint a Data Protection Officer.2
  • All companies that process certain types of sensitive data (g., race, ethnicity, political opinion, religious beliefs, union membership, biometric data, health information, etc.) as a “core activity” and on a “large scale” must appoint a Data Protection Officer.3
  • Other companies (e., that don’t monitor individuals on a large scale and/or process sensitive information on a large scale) may be required by individual Member States (e.g., Germany and others) to appoint Data Protection Officers.4
  • The Officer that is appointed must have “expert knowledge of data protection law and practices.”5 The level of expert knowledge should be proportionate to the company’s “data processing operations carried out and the protection required for the personal data processed.”6
  • The Officer can either be an employee, or work for a third party (g., a law firm), but must be independent.7 If they are an employee, independence may inhibit a company’s ability to terminate their employment.8
  • The Officer must be given company resources to carry out their responsibilities and to obtain ongoing training to maintain their expert knowledge, access to the company’s data processing personnel, and significant independence in the performance of his or her duties.9

The following provides a snapshot of information concerning privacy officers:

85%

Percentage of privacy officers that spend at least 50% of their time on privacy-specific activities.10

9

The average number of years of experience a privacy officer has in privacy related roles.11

28,000

Estimate of the number of new data protection officers that will be needed under the GDPR.12

63%

Percentage of privacy officers that are currently housed within the Legal Department.13

3.3 – 25

The number of full time employees retained by Fortune 1000 companies to deal specifically with privacy-related issues.14

 

The following summarizes some of the duties of the data protection officers required by the GDPR:

  1. Report to C-Suite. The Officer must directly report to the “highest management level” of the company.15
  2. Consult on All Privacy Issues. The officer must be “involved in all issues which relate to the protection of personal data.”16
  3. Inform Company of Legal Obligations. The officer must “inform and advise” the company of their obligations under the GDPR and member state data privacy laws.17
  4. Monitor Company Compliance with Law. The Officer must “monitor” the company’s compliance with (1) the GDPR, (2) member state data privacy laws, and (3) the company’s own data related policies.18
  5. Monitor Company Privacy and Security Training. The Officer must monitor the company’s efforts to conduct data privacy and security related training of employees.19
  6. Monitor Company Privacy and Security Audits. The Officer must monitor the company’s efforts to conduct data privacy and security related audits.20
  7. Respond to Questions From Consumers / Employees. The Officer must be available to data subjects who raise questions or concerns regarding the processing of their data by the company, such as issues related to data security, withdrawal of consent, right to be forgotten, data portability, and cross-border data transfers.21
  8. Publicly Identified. The officer’s contact information must be made available to member state supervisory authorities.22
  9. Deal with Regulators. The Officer must act as a point of contact (if needed) with government agencies on issues relating to data.23
  10. Conduct Privacy Impact Assessments. The Officer must assist the company, if needed, in conducting data protection impact assessments.

1. GDPR Recitals ¶¶ 20, 21; GDPR Art. 3(1), (2).

2. GDPR Art. 35(1)(b).

3. GDPR Art. 35(1)(c).

4. GDPR Art. 35(4).

5. GDPR Art. 35(5).

6. GDPR Recital 75.

7. GDPR Art. 35(8); Recital 75..

8. GDPR Art. 36(3).

9. GDPR Art. 36.

10. IAPP, Benchmarking Privacy Management and Investments of the Fortune 1000, p.13 (2014), https://iapp.org/resources/article/full-report-benchmarking-privacy-management-and-investments-of-the-fortune-1000/

 

11. Id. at 11.

12. IAPP, Study: At Least 28,000 DPOs Needed To Meet GDPR Requirements (Apr. 19, 2016).

13. Id. at 21.

14. IAPP, Benchmarking Privacy Management and Investments of the Fortune 1000, p. 17, 20 (2014), https://iapp.org/resources/article/full-report-benchmarking-privacy-management-and-investments-of-the-fortune-1000/. Survey found that on average companies in the Fortune 1000 with an “early stage” privacy program had 3.3 FTEs whereas companies with a “mature stage” privacy program had 25 FTEs.

15. GDPR Art. 36(3).

16. GDPR Art. 36(1).

17. GDPR Art. 37(1)(a).

18. GDPR Art. 37(b).

19. GDPR Art. 37(b).

20. GDPR Art. 37(b).

21. GDPR Art. 36(2a).

22. GDPR Art. 35(9).

23. GDPR Art. 37(h), (g).