Article 25 GDPR: Difference between revisions

From GDPRhub
(Time of the determination of means)
Line 198: Line 198:
==Commentary==
==Commentary==
Article 25 GDPR establishes the idea of data protection "by ''design'' and by ''default''”.<ref>The Data Protection Directive did not contain a similar provision. Although Article 17 DPD Recital 46 had a similar thrust, the focus in those provisions revolved mostly around security. See, ''Bygrave'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 25 GDPR, p. 573 (Oxford University Press 2020). However, these concepts were not new: privacy by design -and default was originally conceptualized in the 1990s by the Canadian Information and Privacy Commissioner of Ontario. They held that, in order to be effective, data protection must be implemented ''ex ante''. Hence, the controller must define the privacy requirements that need to be taken into account while engineering, and determine the default settings of the final product. See, ''Nolte, Werkmeister'', in Gola, Datenschutz-Grundverordnung, Article 25 GDPR, margin number 1 (C.H. Beck 2018, 2nd Edition).</ref> Accordingly, controllers must put in place appropriate technical and organisational measures that are designed to implement data protection principles.<ref>Although the controller is responsible for adherence with these principles, Recital 78 stipulates that producers of applications, products, and services, are ''encouraged'' to consider the data protection obligations that controllers need to fulfil. Hence, the goal is to have developers and controllers embrace a culture of responsibility and systematically indicate processes which could infringe the GDPR, and to strengthen the data subject's trust in the processing systems. ''Martini'', in Paal, Pauly, DS-GVO, Article 25, margin number 11 (C.H. Beck 2021, 3rd Edition), citing 'Cavoukian Privacy by Design - The 7 Foundational Principles', 2011, p. 1 (available [https://privacy.ucsc.edu/resources/privacy-by-design---foundational-principles.pdf here]). See also, AEPD, Guía de Privacidad desde el Diseño, October 2019, pp. 6-7 (available [https://www.aepd.es/sites/default/files/2019-11/guia-privacidad-desde-diseno.pdf here]).</ref> This means that when programming, designing, and conceptualizing systems and programs, as well as when acquiring systems and services from third parties, the relevant data protection aspects should be taken into account and integrated into the technology.<ref>''Bygrave'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 25 GDPR, p. 576 (Oxford University Press 2020).</ref> The first paragraph describes the principles of data protection by ''design'' in more detail. The second paragraph expands on this by describing the principles of data protection by ''default''. The third paragraph explains that an approved certification mechanism, pursuant to Article 42, may be used as an element to demonstrate compliance.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 25, margin number 10 (C.H. Beck 2020, 3rd Edition).</ref>
Article 25 GDPR establishes the idea of data protection "by ''design'' and by ''default''”.<ref>The Data Protection Directive did not contain a similar provision. Although Article 17 DPD Recital 46 had a similar thrust, the focus in those provisions revolved mostly around security. See, ''Bygrave'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 25 GDPR, p. 573 (Oxford University Press 2020). However, these concepts were not new: privacy by design -and default was originally conceptualized in the 1990s by the Canadian Information and Privacy Commissioner of Ontario. They held that, in order to be effective, data protection must be implemented ''ex ante''. Hence, the controller must define the privacy requirements that need to be taken into account while engineering, and determine the default settings of the final product. See, ''Nolte, Werkmeister'', in Gola, Datenschutz-Grundverordnung, Article 25 GDPR, margin number 1 (C.H. Beck 2018, 2nd Edition).</ref> Accordingly, controllers must put in place appropriate technical and organisational measures that are designed to implement data protection principles.<ref>Although the controller is responsible for adherence with these principles, Recital 78 stipulates that producers of applications, products, and services, are ''encouraged'' to consider the data protection obligations that controllers need to fulfil. Hence, the goal is to have developers and controllers embrace a culture of responsibility and systematically indicate processes which could infringe the GDPR, and to strengthen the data subject's trust in the processing systems. ''Martini'', in Paal, Pauly, DS-GVO, Article 25, margin number 11 (C.H. Beck 2021, 3rd Edition), citing 'Cavoukian Privacy by Design - The 7 Foundational Principles', 2011, p. 1 (available [https://privacy.ucsc.edu/resources/privacy-by-design---foundational-principles.pdf here]). See also, AEPD, Guía de Privacidad desde el Diseño, October 2019, pp. 6-7 (available [https://www.aepd.es/sites/default/files/2019-11/guia-privacidad-desde-diseno.pdf here]).</ref> This means that when programming, designing, and conceptualizing systems and programs, as well as when acquiring systems and services from third parties, the relevant data protection aspects should be taken into account and integrated into the technology.<ref>''Bygrave'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 25 GDPR, p. 576 (Oxford University Press 2020).</ref> The first paragraph describes the principles of data protection by ''design'' in more detail. The second paragraph expands on this by describing the principles of data protection by ''default''. The third paragraph explains that an approved certification mechanism, pursuant to Article 42, may be used as an element to demonstrate compliance.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 25, margin number 10 (C.H. Beck 2020, 3rd Edition).</ref>
The obligations under Article 25 are directed specifically at the controller ([[Article 4 GDPR|Article 4(7) GDPR]]) which remains accountable for fulfilling all legal obligations related to data processing. Processors are indirectly affected since, under [[Article 28 GDPR|Article 28(1) GDPR]], a controller shall only use processors providing the same standards under Article 25 GDPR.<ref>Article 28(1) partially repeats the wording of Article 25(1): "''processors providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that processing will meet the requirements of this Regulation and ensure the protection of the rights of the data subject''".</ref> However, ultimately the controller is responsible for the compliance of the processing carried out by their processors and sub-processors.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), margin number 1 (available [https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref>
Manufacturers or producers of systems are not directly addressed by the GDPR. Nevertheless, as suggested by Recital 78, they are influenced by data protection laws, either indirectly or due to market dynamics. This encourages manufacturers and service providers to offer and introduce products, systems, and services that prioritize data protection.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 25 GDPR, margin numbers 13 (C.H. Beck 2020, 3rd Edition). The Author also highlishts the existance of an ongoing discussion regarding whether the delivery of software that does not prioritize data protection could be considered a defect that holds the manufacturer liable, even without a specific agreement. However, it is important to note that if there are no data protection-friendly technologies available on the market, and this represents the current state of the industry, manufacturers are not obligated to create new technologies. This aspect of the standard has received criticism due to potential interference with the economic freedom of manufacturers.</ref>


EDPB Guidelines: [https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en Guidelines 4/2019 on Article 25 Data Protection by Design and by Default]  
EDPB Guidelines: [https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en Guidelines 4/2019 on Article 25 Data Protection by Design and by Default]  
Line 203: Line 207:
===(1) Data protection by design===
===(1) Data protection by design===
The controller must implement technical and organisational measures that are capable of effectively realizing the data protection principles set out in [[Article 5 GDPR]], meeting the requirements of the GDPR and ensuring the protection of the data subject's rights (including Articles [[Article 12 GDPR|12]]-[[Article 22 GDPR|22]]). This should already happen when the controller determines the ''means of the processing'', i.e. in the ''design process''. This ensures that appropriate technical and organisational measures are implemented at the beginning of the processing and throughout the processing itself. These obligations must be addressed with practical and effective solutions.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref>
The controller must implement technical and organisational measures that are capable of effectively realizing the data protection principles set out in [[Article 5 GDPR]], meeting the requirements of the GDPR and ensuring the protection of the data subject's rights (including Articles [[Article 12 GDPR|12]]-[[Article 22 GDPR|22]]). This should already happen when the controller determines the ''means of the processing'', i.e. in the ''design process''. This ensures that appropriate technical and organisational measures are implemented at the beginning of the processing and throughout the processing itself. These obligations must be addressed with practical and effective solutions.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref>
==== The controller ====
The main obligations under Article 25 are directed specifically at the controller ([[Article 4 GDPR|Article 4(7) GDPR]]) which remains accountable for fulfilling all legal obligations related to data processing. Processors are indirectly affected since, under [[Article 28 GDPR|Article 28(1) GDPR]], a controller shall only use processors providing the same standards under Article 25 GDPR.<ref>Article 28(1) partially repeats the wording of Article 25(1): "''processors providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that processing will meet the requirements of this Regulation and ensure the protection of the rights of the data subject''".</ref> However, ultimately the controller is responsible for the compliance of the processing carried out by their processors and sub-processors.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), margin number 1 (available [https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref>
Manufacturers or producers of systems are not directly addressed by the GDPR. Nevertheless, as suggested by Recital 78, they are influenced by data protection laws, either indirectly or due to market dynamics. This encourages manufacturers and service providers to offer and introduce products, systems, and services that prioritize data protection.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 25 GDPR, margin numbers 13 (C.H. Beck 2020, 3rd Edition). The Author also highlishts the existance of an ongoing discussion regarding whether the delivery of software that does not prioritize data protection could be considered a defect that holds the manufacturer liable, even without a specific agreement. However, it is important to note that if there are no data protection-friendly technologies available on the market, and this represents the current state of the industry, manufacturers are not obligated to create new technologies. This aspect of the standard has received criticism due to potential interference with the economic freedom of manufacturers.</ref> 
==== Taking into account... ====
==== Taking into account... ====
Article 25 (1) lists elements that the controller has to take into account when determining the technical and organisational measures of a specific processing operation.
Article 25 (1) lists elements that the controller has to take into account when determining the technical and organisational measures of a specific processing operation.
Line 225: Line 223:
These criteria have the same meaning as in [[Article 24 GDPR#1|Article 24(1)]] and [[Article 32 GDPR#1|Article 32(1)]]. See therefore commentary on [[Article 24 GDPR]].  
These criteria have the same meaning as in [[Article 24 GDPR#1|Article 24(1)]] and [[Article 32 GDPR#1|Article 32(1)]]. See therefore commentary on [[Article 24 GDPR]].  


=====Risks of varying likelihood and severity for rights and freedoms of natural persons=====
=====Risks of varying likelihood and severity for rights and freedoms of natural persons posed by the processing =====
The GDPR stipulates a risk assessment in a number of its provisions like Articles [[Article 24 GDPR|24]], 25, [[Article 32 GDPR|32]] and [[Article 35 GDPR|35]]. For detailed remarks see therefore commentary on [[Article 24 GDPR]].   
The GDPR imposes the duty to perform a risk assessment in a number of its provisions like in Articles [[Article 24 GDPR|24]], 25, [[Article 32 GDPR|32]] and [[Article 35 GDPR|35]]. The risk assessment should always be performed with regard to a given processing activity. For detailed remarks see therefore commentary on [[Article 24 GDPR]].  <blockquote><u>EDPB</u>: For example, a controller assesses the particular risks associated with a lack of freely given consent, which constitutes a violation of the lawfulness principle, in the course of the processing of personal data of children and young people under 18 as a vulnerable group, in a case where no other legal ground exists, and implements appropriate measures to address and effectively mitigate the identified risks associated with this group of data subjects.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), pp. 9-10 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref></blockquote>The methods used in carrying out a Data Protection Impact Assessment (DPIA) under Article 35 may be useful in this regard.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), pp. 9-10 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref>


During the risk analysis to ensure compliance with Articles 25, the controller is required to identify risks to the rights of data subjects that may arise from a breach of the principles. The likelihood and severity of these risks must be determined to implement effective measures for mitigating them. A controller shall always perform a data protection risk assessment with regard to a given processing activity. <blockquote><u>EDPB</u>: For example, a controller assesses the particular risks associated with a lack of freely given consent, which constitutes a violation of the lawfulness principle, in the course of the processing of personal data of children and young people under 18 as a vulnerable group, in a case where no other legal ground exists, and implements appropriate measures to address and effectively mitigate the identified risks associated with this group of data subjects.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), pp. 9-10 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref></blockquote>The methods used in carrying out a Data Protection Impact Assessment (DPIA) under Article 35 may be useful in this regard.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), pp. 9-10 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref>
==== At the time of the determination of the means [...] and at the time of processing ====
Controllers must assess the implementation of appropriate measures "''at the time of the determination of the means for processing''" and "''at the time of the processing itself''". Therefore, the controller has to consider this obligation already in the design stage of the processing activity - i.e. when it considers how the processing will be conducted and which mechanisms and tools it will use for the processing.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), margin number 34 (available [https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref> Hence, the privacy by design principle should be considered as early as possible in order to right away choose appropriate processing mechanisms (e.g. software, hardware, processors) and to avoid later changes in the basic components of the processing activity.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), marginal number 36 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref> <blockquote><u>Example</u>: A bank wants to implement a whistle-blower tool for its employees. According to the privacy by design principle set out in Article 25(1) GDPR, the bank, as a controller, has to consider the requirements of the GDPR already during the design stage of the processing activity. Therefore, it has to consider how it can ensure compliance with data protection principles and protect the rights of data subjects (e.g. by choosing a GDPR compliant software by a third party and defining the strictly necessary information collected by whistle-blower). </blockquote>Obviously the obligations also applies throughout the live circle of the processing activity. Therefore, the controller has to consider the privacy by design principle also when it considers any later changes in the processing activity.   
 
This can lead to problems for processing activities that were already in place before the GDPR entered into force and that cannot easily be changed. However, Article 25 GDPR also applies to such pre-existing systems. Controllers must re-asses their means of processing if the systems they use are outdated, and incompatible to ensure compliance with the GDPR.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), marginal number 38 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref> Because the state of the art continuously changes, updating systems will be a continuous and necessary practical component of adhering to the privacy by design principle during ongoing processing activities.<ref>''Nolte, Werkmeister'', in Gola, Heckmann, Datenschutz-Grundverordnung, Article 25 GDPR, margin number 14 (C.H. Beck 2022, 3rd Edition).</ref>


==== Shall implement appropriate technical and organizational measures and necessary safeguards ====
==== Shall implement appropriate technical and organizational measures and necessary safeguards ====
Line 251: Line 252:
The EDPB clarifies that "effectiveness is at the heart of the concept of data protection by design." This means that the controller must implement any necessary measure to ensure the three aforementioned objectives are individually met. As a result, there is no predefined list of required measures. What matters is achieving the desired outcome, which means the measure is "effective".<ref>Any method that implements the data protection principles "effectively" can be used. As the EDPB stipulates, the "appropriateness" requirement is closely related to the requirement of "effectiveness". EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).
The EDPB clarifies that "effectiveness is at the heart of the concept of data protection by design." This means that the controller must implement any necessary measure to ensure the three aforementioned objectives are individually met. As a result, there is no predefined list of required measures. What matters is achieving the desired outcome, which means the measure is "effective".<ref>Any method that implements the data protection principles "effectively" can be used. As the EDPB stipulates, the "appropriateness" requirement is closely related to the requirement of "effectiveness". EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).
</ref> Furthermore, in line with the accountability principle stated in Article 5(2) of the GDPR, the controller should adopt additional measures to demonstrate the effectiveness of their choices.<blockquote><u>EDPB</u>: To do so, the controller may determine appropriate key performance indicators (KPI) to demonstrate the effectiveness. A KPI is a measurable value chosen by the controller that demonstrates how effectively the controller achieves their data protection objective. KPIs may be quantitative, such as the percentage of false positives or false negatives, reduction of complaints, reduction of response time when data subjects exercise their rights; or qualitative, such as evaluations of performance, use of grading scales, or expert assessments.<ref>Alternatively to KPIs, controllers may be able to demonstrate the effective implementation of the principles by providing the rationale behind their assessment of the effectiveness of the chosen measures and safeguards. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref></blockquote>
</ref> Furthermore, in line with the accountability principle stated in Article 5(2) of the GDPR, the controller should adopt additional measures to demonstrate the effectiveness of their choices.<blockquote><u>EDPB</u>: To do so, the controller may determine appropriate key performance indicators (KPI) to demonstrate the effectiveness. A KPI is a measurable value chosen by the controller that demonstrates how effectively the controller achieves their data protection objective. KPIs may be quantitative, such as the percentage of false positives or false negatives, reduction of complaints, reduction of response time when data subjects exercise their rights; or qualitative, such as evaluations of performance, use of grading scales, or expert assessments.<ref>Alternatively to KPIs, controllers may be able to demonstrate the effective implementation of the principles by providing the rationale behind their assessment of the effectiveness of the chosen measures and safeguards. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref></blockquote>
==== Both at the time.. ====
Controllers must assess their implemented measures "''at the time of the determination of the means for processing''" and "at the time of the processing itself", therefore from beginning to the end, continually. Hence, the processing operations should be considered as early as possible, and the controller can not use the "excuse" that it would lead to disproportionally high costs to implement data protection friendly measures at a later stage.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 10 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]); ''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 25, margin number 23 (C.H. Beck 2020, 3rd Edition).</ref> More problematic is what to do with an existent system (that pre-dated the coming into force of the GDPR) that cannot easily be changed. Companies and institutions must re-asses their means of processing if the systems they use are outdated, and incompatible to ensure compliance with the GDPR.<ref>EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 11 (available [https://edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-42019-article-25-data-protection-design-and_en here]).</ref> Because the state of the art continuously changes, updating systems will be a continuous and necessary practical component of adhering to the privacy by design principle during ongoing processing activities.<ref>''Nolte, Werkmeister'', in Gola, Datenschutz-Grundverordnung, Article 25 GDPR, margin number 14 (C.H. Beck 2018, 2nd Edition).</ref>


===(2) Data protection by default===
===(2) Data protection by default===

Revision as of 09:43, 4 July 2024

Article 25 - Data protection by design and by default
Gdpricon.png
Chapter 10: Delegated and implementing acts

Legal Text

Article 25 - Data protection by design and by default

1. Taking into account the state of the art, the cost of implementation and the nature, scope, context and purposes of processing as well as the risks of varying likelihood and severity for rights and freedoms of natural persons posed by the processing, the controller shall, both at the time of the determination of the means for processing and at the time of the processing itself, implement appropriate technical and organisational measures, such as pseudonymisation, which are designed to implement data-protection principles, such as data minimisation, in an effective manner and to integrate the necessary safeguards into the processing in order to meet the requirements of this Regulation and protect the rights of data subjects.

2. The controller shall implement appropriate technical and organisational measures for ensuring that, by default, only personal data which are necessary for each specific purpose of the processing are processed. That obligation applies to the amount of personal data collected, the extent of their processing, the period of their storage and their accessibility. In particular, such measures shall ensure that by default personal data are not made accessible without the individual's intervention to an indefinite number of natural persons.

3. An approved certification mechanism pursuant to Article 42 may be used as an element to demonstrate compliance with the requirements set out in paragraphs 1 and 2 of this Article.

Relevant Recitals

Recital 78: Appropriate Technical and Organisational Measures
The protection of the rights and freedoms of natural persons with regard to the processing of personal data require that appropriate technical and organisational measures be taken to ensure that the requirements of this Regulation are met. In order to be able to demonstrate compliance with this Regulation, the controller should adopt internal policies and implement measures which meet in particular the principles of data protection by design and data protection by default. Such measures could consist, inter alia, of minimising the processing of personal data, pseudonymising personal data as soon as possible, transparency with regard to the functions and processing of personal data, enabling the data subject to monitor the data processing, enabling the controller to create and improve security features. When developing, designing, selecting and using applications, services and products that are based on the processing of personal data or process personal data to fulfil their task, producers of the products, services and applications should be encouraged to take into account the right to data protection when developing and designing such products, services and applications and, with due regard to the state of the art, to make sure that controllers and processors are able to fulfil their data protection obligations. The principles of data protection by design and by default should also be taken into consideration in the context of public tenders.

Commentary

Article 25 GDPR establishes the idea of data protection "by design and by default”.[1] Accordingly, controllers must put in place appropriate technical and organisational measures that are designed to implement data protection principles.[2] This means that when programming, designing, and conceptualizing systems and programs, as well as when acquiring systems and services from third parties, the relevant data protection aspects should be taken into account and integrated into the technology.[3] The first paragraph describes the principles of data protection by design in more detail. The second paragraph expands on this by describing the principles of data protection by default. The third paragraph explains that an approved certification mechanism, pursuant to Article 42, may be used as an element to demonstrate compliance.[4]

The obligations under Article 25 are directed specifically at the controller (Article 4(7) GDPR) which remains accountable for fulfilling all legal obligations related to data processing. Processors are indirectly affected since, under Article 28(1) GDPR, a controller shall only use processors providing the same standards under Article 25 GDPR.[5] However, ultimately the controller is responsible for the compliance of the processing carried out by their processors and sub-processors.[6]

Manufacturers or producers of systems are not directly addressed by the GDPR. Nevertheless, as suggested by Recital 78, they are influenced by data protection laws, either indirectly or due to market dynamics. This encourages manufacturers and service providers to offer and introduce products, systems, and services that prioritize data protection.[7]

EDPB Guidelines: Guidelines 4/2019 on Article 25 Data Protection by Design and by Default

(1) Data protection by design

The controller must implement technical and organisational measures that are capable of effectively realizing the data protection principles set out in Article 5 GDPR, meeting the requirements of the GDPR and ensuring the protection of the data subject's rights (including Articles 12-22). This should already happen when the controller determines the means of the processing, i.e. in the design process. This ensures that appropriate technical and organisational measures are implemented at the beginning of the processing and throughout the processing itself. These obligations must be addressed with practical and effective solutions.[8]

Taking into account...

Article 25 (1) lists elements that the controller has to take into account when determining the technical and organisational measures of a specific processing operation.

State of the art

In general, this means, that the controller has to be aware of and take into account the latest developments in its field and has to stay up-to-date with technology. The idea is that a controller shall never go below what is commonly considered the appropriate technological standard at a given time. In detail, the interpretation of this criterion can be challenging, requiring appropriate technical expertise and input from expert. Guidelines by supervisory authorities can also be helpful to interpret the current state of the art.[9] But since the state of the art is a dynamic concept which has to be assessed continuously and in the context of the technological progress even existing standards or guidelines can only be indicative for the assessment whether respective measures of the controller still suffice.[10]

The "state of the art" criterion does not exclusively apply to technical measures. Also the organisational measures like data protection and IT-security trainings or policies of the controller have to reflect any developments in the state of the art.[11]

Cost of implementation

Regularly the controller has a choice between different technical and organisational measures. When deciding which technical and organisational measures to implement, the controller can take the cost of implementation of those measures into account and is not forced to allocate an excessive amount of resources for one specific measure if there are alternative measures available that are less resource-intensive yet still effective. Such costs include not only costs necessary to develop privacy compliant technologies, but more broadly all business resources allocated to achieve data protection goals (e.g. efforts by individual employees).[12]

However, it is important to stress that the implementation cost should be taken into consideration when incorporating data protection by design, rather than being used as a justification for not implementing it. Whatever measures the controller implements, they have to be effective and ensure that all the requirements of the GDPR are met and the rights of data subjects are protected.[13]

Nature, scope, context and purpose of processing

These criteria have the same meaning as in Article 24(1) and Article 32(1). See therefore commentary on Article 24 GDPR.

Risks of varying likelihood and severity for rights and freedoms of natural persons posed by the processing

The GDPR imposes the duty to perform a risk assessment in a number of its provisions like in Articles 24, 25, 32 and 35. The risk assessment should always be performed with regard to a given processing activity. For detailed remarks see therefore commentary on Article 24 GDPR.

EDPB: For example, a controller assesses the particular risks associated with a lack of freely given consent, which constitutes a violation of the lawfulness principle, in the course of the processing of personal data of children and young people under 18 as a vulnerable group, in a case where no other legal ground exists, and implements appropriate measures to address and effectively mitigate the identified risks associated with this group of data subjects.[14]

The methods used in carrying out a Data Protection Impact Assessment (DPIA) under Article 35 may be useful in this regard.[15]

At the time of the determination of the means [...] and at the time of processing

Controllers must assess the implementation of appropriate measures "at the time of the determination of the means for processing" and "at the time of the processing itself". Therefore, the controller has to consider this obligation already in the design stage of the processing activity - i.e. when it considers how the processing will be conducted and which mechanisms and tools it will use for the processing.[16] Hence, the privacy by design principle should be considered as early as possible in order to right away choose appropriate processing mechanisms (e.g. software, hardware, processors) and to avoid later changes in the basic components of the processing activity.[17]

Example: A bank wants to implement a whistle-blower tool for its employees. According to the privacy by design principle set out in Article 25(1) GDPR, the bank, as a controller, has to consider the requirements of the GDPR already during the design stage of the processing activity. Therefore, it has to consider how it can ensure compliance with data protection principles and protect the rights of data subjects (e.g. by choosing a GDPR compliant software by a third party and defining the strictly necessary information collected by whistle-blower).

Obviously the obligations also applies throughout the live circle of the processing activity. Therefore, the controller has to consider the privacy by design principle also when it considers any later changes in the processing activity.

This can lead to problems for processing activities that were already in place before the GDPR entered into force and that cannot easily be changed. However, Article 25 GDPR also applies to such pre-existing systems. Controllers must re-asses their means of processing if the systems they use are outdated, and incompatible to ensure compliance with the GDPR.[18] Because the state of the art continuously changes, updating systems will be a continuous and necessary practical component of adhering to the privacy by design principle during ongoing processing activities.[19]

Shall implement appropriate technical and organizational measures and necessary safeguards

Technical and organisational measures

The "technical and organisational measures" mentioned in this provision are in principle the same measures mentioned in other provisions of the GDPR like Articles 24 and 32. Only the concrete aim of the measures is specified somewhat differently in the various provisions.

Article 25 GDPR specifically mentions pseudonymisation (Article 4(5) GDPR) as a technical and organisational measure and notes that these measures should be designed (i) to implement data-protection principles, such as data minimization (Article 5(1)(c) GDPR), in an effective manner and (ii) to integrate the integrate the necessary safeguards into the processing in order to meet the requirements of this Regulation and protect the rights of data subjects.

For detailed remarks on "technical and organisational measures" see the commentary on Article 24 GDPR.

Appropriate measures

"Appropriate" is a technical or organisational measure that effectively addresses the issues posed by the specific processing and circumstances. In general, the "appropriateness" of measures chosen by the controller is a point upon which several GDPR provisions touch, most notably - alongside with Article 25 - Articles 24 and 32. The EDPS Guidelines on assessing the proportionality of measures that limit the fundamental rights to privacy and to the protection of personal data[20] can be used as a starting point to gain some insight.

In lack of an exhaustive catalogue, technical or organisational measure can be anything from the use of advanced technological solutions to the basic training of personnel.[21] Examples that may be suitable, depending on the context and risks associated with the processing in question, includes pseudonymization of personal data;[22] storing personal data available in a structured, commonly machine-readable format; enabling data subjects to intervene in the processing; providing information about the storage of personal data; having malware detection systems; training employees about basic "cyber hygiene"; establishing privacy and information security management systems, obligating processors contractually to implement specific data minimisation practices, etc.[23]

Designed to implement data-protection principles in an effective manner and protecting data subjects' rights and freedoms

It is at this point in Article 25 that the term "design" is introduced. The measures and safeguards implemented by the controller must be "designed" from the outset to fulfill their three main objectives "in an effective manner": implementing the principles of data processing (Article 5), protecting the rights of data subjects (primarily, Articles 12-22 of the GDPR), and more generally, complying with the requirements of the Regulation.

The EDPB clarifies that "effectiveness is at the heart of the concept of data protection by design." This means that the controller must implement any necessary measure to ensure the three aforementioned objectives are individually met. As a result, there is no predefined list of required measures. What matters is achieving the desired outcome, which means the measure is "effective".[24] Furthermore, in line with the accountability principle stated in Article 5(2) of the GDPR, the controller should adopt additional measures to demonstrate the effectiveness of their choices.

EDPB: To do so, the controller may determine appropriate key performance indicators (KPI) to demonstrate the effectiveness. A KPI is a measurable value chosen by the controller that demonstrates how effectively the controller achieves their data protection objective. KPIs may be quantitative, such as the percentage of false positives or false negatives, reduction of complaints, reduction of response time when data subjects exercise their rights; or qualitative, such as evaluations of performance, use of grading scales, or expert assessments.[25]

(2) Data protection by default

The second paragraph of Article 25 requires the controller to implement appropriate technical and organizational measures to ensure, by default, that only personal data necessary for the specific processing purposes are processed. This provision establishes an explicit connection with the principles of data minimization, storage limitation and purpose limitation.

One could argue that this clarification is redundant since the controller is already obliged, under paragraph 1, to adopt appropriate measures to ensure the effective adherence to the principles of proper processing, including data minimisation. However, although the principles of data protection by design and by default may look similar at first glance, there are considerable differences between them. First, "by design" is broader than "by default", since the focus of the latter principle is on ensuring data minimisation, storage limitation, purpose limitation and confidentiality. Whereas "by design" seems to have a focus on the stages of the development of the product, "by default" focusses more on the end-result: are the settings configured in such a way that data minimisation and confidentiality are ensured?[26] Second, the underlying concept of the principle of data protection by default is that not only should the tool be designed to comply with the Regulation, but it should also be configured in practice to default settings that ensure the adherence to those principles.[27] In other words, unless the user decides otherwise, the default settings shall be the most privacy-friendly. This is particularly significant, considering the prevailing tendency to accumulate personal data beyond reasonable necessity, especially in the realm of the Internet and mobile applications.[28]

Example: A company that produces an operating system for a computer has, inter alia, to consider that a customer might want to change their settings in such a way that they can amend their data protection settings themselves, as follows from Article 25(1). However, when this computer is delivered to the customer, the default settings within the software must already be set in such a way that the data protection principles of data minimisation and confidentiality are already ensured, since this follows from Article 25(2).

The controller

The addressee of the provision is the controller. See the commentary under paragraph 1 for more details on this point.

Shall implement appropriate technical and organisational measures

To ensure the highest "default" data protection standard, the controller must implement appropriate organisational and technical measures. With regard to the meaning of "appropriate" we refer to the analysis in paragraph (1). Although the measures should be implemented to ensure compliance with every data protection principle, and are therefore to be understood the same way as in Article 25(1), the measures in the context of Article 25(2) apply especially to the principles of data minimisation, storage limitation, purpose limitation and confidentiality.[29]

By default, only personal data which are necessary for each specific purpose of the processing are processed

The word "default" comes from computer science, and means so much as the pre-existing or pre-selected value of a configurable setting. The principle of data protection by default means that a product or service should have the most data protection-friendly settings configured when the product or service is first turned on or used.[12] Hence, the "factory presets", in case of electronic products, should conform to the highest data protection standard.[30]

In cases where the controller utilizes third-party or off-the-shelf software, it is crucial to conduct a risk assessment of the product. Any functions within the software that lack a legal basis or are incompatible with the intended purposes of processing must be deactivated or disabled.[31] Similar considerations extend to the organisational measures which should be designed to initially handle only the minimum necessary amount of personal data required for the specific operations. This becomes particularly significant when granting access to data to emploees with diverse roles and different access necessities.[32]

These choices have an impact on the amount of personal data collected; the extent of their processing; the period of their storage and the accessibility.

Amount of personal data collected

Controllers should conduct a sound analysis of the volume, types, categories, and level of detail of personal data that is necessary for their processing activities. It is important to compare the risks arising from the envisaged processing with the risks that may be posed by the collection of smaller amounts or less detailed information about data subjects. Regardless of the specific circumstances, the default settings should not allow for the collection of personal data that is unnecessary for the intended processing purpose. This means that if certain categories of personal data are determined to be unnecessary or if less detailed information is sufficient instead of highly granular data, excessive shall not be collected in the first place.[33]

Extent of their processing

Processing activities involving personal data must adhere to the principle of necessity. While multiple processing operations may contribute to a specific purpose, it does not imply that all types and frequencies of processing can be conducted on the data. Controllers should exercise caution to ensure that they do not exceed the boundaries of "compatible purposes" as outlined in Article 6(4) and consider what processing activities would be within the reasonable expectations of data subjects. It is important to remember that the mere necessity of certain personal data for fulfilling a purpose does not justify unrestricted or excessive processing operations.[34]

The period of their storage

The controller is required to restrict the retention period of personal data to what is necessary for the specific purpose of processing. Once the personal data is no longer needed for its intended purpose, it should be either deleted or anonymized by default. The duration of the retention period will vary depending on the particular processing purpose. This obligation is directly connected to the principle of storage limitation stated in Article 5(1)(e) of the GDPR. By default, the controller should establish systematic procedures for data deletion or anonymization that are integrated into the processing operations.[35]

Their accessibility

Article 25(2) clarifies that, by default, only the minimum number of individuals within the controller's organization (or indirectly, the processor's organization), should have access to personal data. This entails the adoption of technical and organizational measures that restrict personnel access to databases. In line with this logic, the latter part of Article 25(2) further clarifies that the data subject should always be consulted before their personal data is made available to an indefinite number of individuals, or in other words, before it is made public.[36]

(3) Approved certification mechanism

The last paragraph of the provision is similar to Article 24(3). It states that an "approved certification mechanism pursuant to Article 42" may be used as an element to demonstrate compliance with the requirements set out in the first two paragraphs of the provision. Hence, just like in Article 24(3), it follows from the word "element" that such adherence only supports the assumption that the controller is compliant, and does not prove it.[37]

Decisions

→ You can find all related decisions in Category:Article 25 GDPR

References

  1. The Data Protection Directive did not contain a similar provision. Although Article 17 DPD Recital 46 had a similar thrust, the focus in those provisions revolved mostly around security. See, Bygrave, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 25 GDPR, p. 573 (Oxford University Press 2020). However, these concepts were not new: privacy by design -and default was originally conceptualized in the 1990s by the Canadian Information and Privacy Commissioner of Ontario. They held that, in order to be effective, data protection must be implemented ex ante. Hence, the controller must define the privacy requirements that need to be taken into account while engineering, and determine the default settings of the final product. See, Nolte, Werkmeister, in Gola, Datenschutz-Grundverordnung, Article 25 GDPR, margin number 1 (C.H. Beck 2018, 2nd Edition).
  2. Although the controller is responsible for adherence with these principles, Recital 78 stipulates that producers of applications, products, and services, are encouraged to consider the data protection obligations that controllers need to fulfil. Hence, the goal is to have developers and controllers embrace a culture of responsibility and systematically indicate processes which could infringe the GDPR, and to strengthen the data subject's trust in the processing systems. Martini, in Paal, Pauly, DS-GVO, Article 25, margin number 11 (C.H. Beck 2021, 3rd Edition), citing 'Cavoukian Privacy by Design - The 7 Foundational Principles', 2011, p. 1 (available here). See also, AEPD, Guía de Privacidad desde el Diseño, October 2019, pp. 6-7 (available here).
  3. Bygrave, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 25 GDPR, p. 576 (Oxford University Press 2020).
  4. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 25, margin number 10 (C.H. Beck 2020, 3rd Edition).
  5. Article 28(1) partially repeats the wording of Article 25(1): "processors providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that processing will meet the requirements of this Regulation and ensure the protection of the rights of the data subject".
  6. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), margin number 1 (available here).
  7. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 25 GDPR, margin numbers 13 (C.H. Beck 2020, 3rd Edition). The Author also highlishts the existance of an ongoing discussion regarding whether the delivery of software that does not prioritize data protection could be considered a defect that holds the manufacturer liable, even without a specific agreement. However, it is important to note that if there are no data protection-friendly technologies available on the market, and this represents the current state of the industry, manufacturers are not obligated to create new technologies. This aspect of the standard has received criticism due to potential interference with the economic freedom of manufacturers.
  8. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available here).
  9. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 25 GDPR, margin numbers 21 (C.H. Beck 2024, 4th Edition). The Author also points out that the concept also defines limit to the controller's responsibility. Authorities cannot require the controller to go beyond the "state of the art".
  10. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), margin number 20 (available here).
  11. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), margin number 21 (available here).
  12. 12.0 12.1 Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 25, margin number 22 (C.H. Beck 2024, 4th Edition).
  13. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 25, margin number 22 (C.H. Beck 2024, 4th Edition)
  14. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), pp. 9-10 (available here).
  15. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), pp. 9-10 (available here).
  16. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), margin number 34 (available here).
  17. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), marginal number 36 (available here).
  18. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), marginal number 38 (available here).
  19. Nolte, Werkmeister, in Gola, Heckmann, Datenschutz-Grundverordnung, Article 25 GDPR, margin number 14 (C.H. Beck 2022, 3rd Edition).
  20. EDPS, ‘Guidelines on assessing the proportionality of measures that limit the fundamental rights to privacy and to the protection of personal data’, 19 December 2019 (available here).
  21. While the wording of Article 25 seemingly distinguishes between the concepts of "technical and organizational measures" and "safeguards," in practice, drawing a clear distinction between them can be challenging, if not unnecessary. Baumgartner in Ehman, Selmayr, Datenschutz-Grundverordnung, Article 25 GDPR, margin number 11 (C.H. Beck 2018, 2nd Edition). Moreover, the EDPB itself appears to follow this approach, as the two concepts are used interchangeably in the frequently referenced guidelines.
  22. Although "pseudonymisation" is the only measure that is listed in the provision as an example, the training of personnel, limiting access to personal data, or any technical measure like anonymisation or advanced encryption, could all be effective measures. However, what differs these measures from measures under Article 24(1), is that these measures are already designed. For example: automatic erasure of certain personal data by the software to comply with the principle of storage limitation. Bygrave, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 25 GDPR, p. 577 (Oxford University Press 2020).
  23. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available here).
  24. Any method that implements the data protection principles "effectively" can be used. As the EDPB stipulates, the "appropriateness" requirement is closely related to the requirement of "effectiveness". EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available here).
  25. Alternatively to KPIs, controllers may be able to demonstrate the effective implementation of the principles by providing the rationale behind their assessment of the effectiveness of the chosen measures and safeguards. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 6 (available here).
  26. Bygrave, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 25 GDPR, p. 577 (Oxford University Press 2020).
  27. Although Article 25(1) mentions that the measures apply to both the development and processing stage, this also has to be assumed for Article 25(2), even though the paragraph does not state it explicitly. After all, a factory preset can only be set to the most data protection-friendly default setting when this end-result has already been envisaged during the development process.
  28. Hansen, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 25 GDPR, margin number 40 (C.H. Beck 2019, 1st Edition).
  29. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 12 (available here).
  30. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 11 (available here).
  31. If this is not possible, then there is a clear problem of data protection by design under Article 25(1) GDPR and the controller should refrain from using that software.
  32. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 12 (available here).
  33. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 12 (available here).
  34. EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 13 (available here).
  35. Anonymization of personal data is "an alternative to deletion, provided that all the relevant contextual elements are taken into account and the likelihood and severity of the risk, including the risk of reidentification, are regularly assessed." EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), p. 13 (available here).
  36. Making personal data "available to an indefinite number of persons may result in even further dissemination of the data than initially intended. This is particularly relevant in the context of the Internet and search engines. This means that controllers should by default give data subjects an opportunity to intervene before personal data is made available on the open Internet. This is particularly important when it comes to children and vulnerable groups." EDPB, 'Guidelines 4/2019 on Article 25 Data Protection by Design and by Default', 20 October 2020 (Version 2.0), pp. 13-14 (available here).
  37. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 25, margin numbers 25-26 (C.H. Beck 2020, 3rd Edition).