Difference between revisions of "Article 22 GDPR"
|Line 247:||Line 247:|
Article 22 has its roots in Articles 15 and 12(a) of the 95/46/EC Data Protection Directive (DPD). One of the main differences is that the GDPR a broader scope of application, since it applies to “automated processing, including profiling”. , the DPD provision was only applicable if a form of profiling was involved.<ref>Article 20 of GDPR proposal, COM(2012) 11 final <https://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=COM:2012:0011:FIN:EN:PDF</ref> difference can be noticed between the initial proposal of the Commission, in which was titled “Measures based on ,and the final wording of the GDPR which extends the scope to include automated decisions which are not based on profiling. contrast to the DPD, Article 22(4) GDPR also explicitly addresses the use of sensitive data by laying down a qualified prohibition of decisions based on categories of data listed under Article 9(1).
Article 22 has its roots in Articles 15 and 12(a) of the 95/46/EC Data Protection Directive (DPD). One of the main differences is that the GDPR
===Right or prohibition?===
===Right or prohibition?===
Revision as of 14:30, 19 July 2021
|← Article 22 - Automated individual decision-making, including profiling →|
Article 22 - Automated individual decision-making, including profiling
1. The data subject shall have the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her or similarly significantly affects him or her.
2. Paragraph 1 shall not apply if the decision:
(a) is necessary for entering into, or performance of, a contract between the data subject and a data controller;
(b) is authorised by Union or Member State law to which the controller is subject and which also lays down suitable measures to safeguard the data subject's rights and freedoms and legitimate interests; or
(c) is based on the data subject's explicit consent.
3. In the cases referred to in points (a) and (c) of paragraph 2, the data controller shall implement suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express his or her point of view and to contest the decision.
4. Decisions referred to in paragraph 2 shall not be based on special categories of personal data referred to in Article 9(1), unless point (a) or (g) of Article 9(2) applies and suitable measures to safeguard the data subject's rights and freedoms and legitimate interests are in place.
Commentary on Article 22
Article 22 has its roots in Articles 15 and 12(a) of the 95/46/EC Data Protection Directive (DPD). One of the main differences is that the GDPR has a broader scope of application, since it applies to “automated processing, including profiling”. In contrast, the DPD provision was only applicable if a form of profiling was involved. This difference in scope can be noticed between the initial proposal of the Commission, in which Article 22 was titled “Measures based on profiling," and the final wording of the GDPR which extends the scope of Article 22 to include automated decisions which are not based on profiling. In contrast to the DPD, Article 22(4) GDPR also explicitly addresses the use of sensitive data by laying down a qualified prohibition of decisions based on categories of data listed under Article 9(1).
Right or prohibition?
There have been conflicting arguments on whether Article 22(1) lays down a right or a general prohibition.
On the one hand, if the provision is interpreted as a right, then the data subject would have to actively exercise the right in order to be protected from the types of impactful decisions that Article 22 deals with. One of the arguments invoked by proponents of this approach is a strictly literal interpretation which looks at the use of the word ‘right’ in Article 22.
Another argument in favour of interpreting the provision as a right is related to the level of ex ante protection for data subjects. This line of reasoning recognises that interpreting Article 22 as a qualified prohibition would indeed offer data subjects a higher level of ex ante protections against automated decisions. However, this line of argumentation then proposes that such protections could theoretically also be offered in connection with the DPIA process. More specifically, some commentators point to the fact that if controllers, based on a self-assessment, are of the opinion that they cannot mitigate the high risk level of an automated decision system, they would have to consult the relevant DPA which could then ban the controller’s automated decision system. It is, however, questionable whether in practice this approach could attain a reliable and meaningful level of ex ante protection for data subjects.
On the other hand, Article 22(1) can be framed as a general prohibition of decisions subject to Article 22. This interpretation seems more in line with the purpose of the provision, which seeks to protect data subjects from a general possibility of being subject to decisions covered by Article 22. A confirmation may be found in the Article 29 Working Party Guidelines on Automated individual decision-making and Profiling, which state that:
“The term “right” in the provision does not mean that Article 22(1) applies only when actively invoked by the data subject. Article 22(1) establishes a general prohibition for decision-making based solely on automated processing. This prohibition applies whether or not the data subject takes an action regarding the processing of their personal data”.
The Article 29 Working Party supports this argument by relying on the principles of the GDPR and its aim to give data subjects control over their personal data. Furthermore, the WP29 makes a reference to Recital 71, which implies that decisions under Article 22(1) are generally not allowed, by contrasting these with decisions regulated by Article 22(2) which should, “however”, be allowed. The WP29’s view of reading Article 22 as a qualified prohibition has not been changed by the EDPB.
The title of Article 22 mentions automated “individual” decision making, which indicates that the scope of the provision is not extended to decisions or processing operations which produce effects for groups of data subjects. Following this reasoning, Article 22 would not be applicable if decisions affect multiple data subjects or groups of individuals connected by common characteristics, such as age, gender, or postal code. However, considering the realities of machine learning and Big Data, pertinent arguments have also been made supporting the view that Article 22 should apply to group decisions as well.
Decision based solely on automated processing
The first element required to trigger Article 22 is the presence of a ‘decision’, which can be interpreted in a broad sense. Examples of a decision can be official acts of public authorities such as decisions on tax returns, as well as automatic refusals of online credit applications or similar decisions in the context of e-recruiting practices. In a more general sense, decisions could also be seen as a particular attitude or position taken with regards to a person, if this position is at least likely to be acted upon. Although there does not seem to be a specific requirement for the decision to be formalised in a particular way, it should at least be distinguishable from other stages of the (decision-making) process.
This second element of Article 22(1) first of all depends on whether human intervention is even possible from a technical perspective, or the decision-making process is constructed in a solely algorithmic way with no room for human involvement.
If the process does at least technically allow for human intervention, then it must be assessed whether the action undertaken by a human is “meaningful” or merely a procedural “token gesture”. In order to meet this criterion, the intervention must be “carried out by someone who has the authority and competence to change the decision”. Furthermore, the human involved must not only have the power to change the decision, but actually exercise this competence by ”consider[ing] all the relevant data” and verifying the substance and correctness of the machine-generated decision.
The ‘automated processing’ criterion in Article 22(1) is related to the final stage of the processing, which results in a solely automated decision based on already existing data. By contrast, the methods of collecting the initial data sources must not necessarily be automated but can be semi-automated or even manual. Furthermore, the automated decision must not entirely be based on personal data related to the person affected by the decision. Instead, the data basis can also include non-personal data, or personal data related to other individuals.
Legal or similarly significant effect
A decision has legal effects on a data subject when it is binding and affects the person’s legal rights or interests. Examples can be the cancellation of a contract, the decision of a tax authority on an individual’s tax return, or the denial of a social benefit granted by law.
Similarly significant effects
In principle, satisfying this criterion means that the impacts of the decision must be sufficiently great despite not changing the legal position of the individual. While it can be difficult to establish this in practice, according to the WP29 some guiding criteria can be the potential of a decision to:
- significantly affect the circumstances, behaviour or choices of the individuals concerned
- have a prolonged or permanent impact on the data subject; or
- at its most extreme, lead to the exclusion or discrimination of individuals.
The WP29 further gives examples of decisions which can similarly significantly affect data subjects, when these:
- affect someone’s financial circumstances, such as their eligibility to credit;
- affect someone’s access to health services;
- deny someone an employment opportunity or put them at a serious disadvantage;
- affect someone’s access to education, for example university admissions.
In any case, the decision should have more than a trivial effect which impacts someone’s position in relation to other persons or to their access to a service or opportunity. For example, Recital 71 mentions the “automatic refusal of an online credit application or e-recruiting practices without human intervention”.
Decisions resulting in targeted advertisement based on profiling could also similarly significantly affect individuals, for example when someone is targeted with high interest loans because they are known to be in financial difficulties and are particularly susceptible to accept such offers. In this context, the WP29 lays down a non-exhaustive list of characteristics that can be decisive in the assessment of each case, such as:
- the intrusiveness of the profiling process, including the tracking of individuals across different websites, devices and services;
- the expectations and wishes of the individuals concerned;
- the way the advert is delivered; or
- using knowledge of the vulnerabilities of the data subjects targeted.
The first exception from the prohibition laid down in Article 22(1) is if the decision is necessary for entering into, or performance of, a contract between the data subject and the controller.
It is unclear how the ‘necessity’ criterion should be interpreted. A strictly textual interpretation would lead to most examples of solely automated decisions not being considered necessary. For example, while assessing an individual’s credit risk is necessary for a bank in order to protect its investments, algorithmic credit scoring is not in itself necessary since an assessment can also be carried by humans. As different arguments could be made for the threshold and meaning of the ‘necessity’ criterion, this aspect will need to be clarified by courts.
Furthermore, an analysis of Articles 6(1)(b) and 22(2)(a) seems to indicate a difference in the scope of the two provisions with regards to the necessity of the processing for entering into a contract. Whereas for Article 6(1)(b) the processing would have to be necessary in order to take steps at the request of the data subject, Article 22(2)(a) does not mention any request from the data subject. Therefore, the scope of application of Article 22(2)(a) seems to be wider in this regard.
In any case, the application of Article 22(2)(a) is always subjected to the presence of “suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express his or her point of view and to contest the decision”. [Article 22(3) GDPR.]
Authorised by law
The second exemption in Article 22(2) is also subject to the presence of “suitable measures to safeguard the data subject's rights and freedoms and legitimate interests”. However, it seems that such measures do not necessarily need to be the same as those foreseen by Article 22(3). Instead, Members States have discretion in this aspect.
The wording of Article 22(2)(c) (“explicit consent”) results in the same standard for this requirement as with Article 9(2)(a).
Where particular attention must be given to it being freely given in the context of entering into or performance of a contract. Indeed, discussions on whether consent is freely given, including in line with Articles 9(2) and 22(2(c), will lead to assessing the necessity element. In this context, it must be assessed whether the decision is necessary for the “performance of a contract, including the provision of a service” as mandated by Article 7(4). However, this provision does not mention entering into a contract, which would seem to exclude examples such as online credit applications where the algorithmic decision occurs in order to enter the contract and not to perform it.
Furthermore, issues could arise with decisions based on profiling, where a data subject might have given their consent to the profiling, for example by accepting a cookie, but not to the decision resulting from it. In this context, data subjects might not even be aware of the solely automated decision occurring, and in any case the consent to the profiling would not be considered as satisfying the requirements of Article 22(2)(c).
Finally, decisions based on explicit consent are also subjected to the safeguards laid down in Article 22(3).
A crucial point worth emphasizing is that Article 22(3) lays down a non-exhaustive list of safeguards, which should always be available to the data subjects. This leaves the door open for additional safeguards, such the heavily disputed potential ‘right to explanation’ mentioned in Recital 71.
However, clarifications will still be needed as to how the safeguards already mentioned by Article 22(3) can be operationalized and what their outcome will be. On the operational side it would be questionable how some systems would even allow for human intervention in practice, for example when the website or platform does not technically allow this. On the other hand, with regards to the legal consequences, it is not clear whether the data subject expressing their views or contesting a decision would lead to the decision being annulled.
Qualified prohibition of using special categories of data
Explicit consent in the context of Article 22(4) should be interpreted in a similar manner as for Article 22(2)(c). With regards to the “suitable measures to safeguard the data subject's rights and freedoms and legitimate interests”, these seem to have the same scope and interpretation as with Article 22(3).
→ You can find all related decisions in Category:Article 22 GDPR
- Article 20 of GDPR proposal, COM(2012) 11 final <https://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=COM:2012:0011:FIN:EN:PDF
- Lee A. Bygrave, ‘Article 22. Automated individual decision-making, including profiling’ Christopher Kuner, Lee A. Bygrave, Christopher Docksey, and and Laura Dreachsler (eds.), The EU General Data Protection Regulation (GDPR) – A Commentary (Oxford University Press), 531.
- Ibid, 531-532.
- WP29, Guidelines on Automated individual decision-making and Profiling for the purposes of Regulation 2016/679, adopted on 3 October 2017; as last revised and adopted on 6 February 2018, 17/EN, WP 251 rev.01, 19.
- See Michael Veale and Lilian Edwards, ‘Clarity, surprises, and further questions in the Article 29 Working Party draft guidance on automated decision-making and profiling’ (2018) 34 Computer Law & Security Review, 402; In addition, another example could be that of individuals classified by categories such as ‘man/woman’, ‘married/single/divorced’, or ‘high/low income’. Solely automated decisions could then be taken for all ‘divorced low-income women’ which would render Article 22 inapplicable, despite their potentially significant effects. In such situations, the decisions could be seen as a bundle of individual decisions, which would make it more difficult to circumvent Article 22, and thereby better protect the fundamental rights of data subjects. However, in the absence of any CJEU decisions on this matter so far, it is still disputed whether Article 22(1) should apply to group decisions or not.
- Bygrave (n 2) 532.
- Maja Brkan, ‘Do algorithms rule the world? Algorithmic decision-making and data protection in the framework of the GDPR and beyond’ (2019) 27 International Journal of Law and Information Technology 2, 102.
- Recital 71 GDPR
- Isak Mendoza and Lee A. Bygrave, ‘The Right not to be Subject to Automated Decisions based on Profiling’ (2017) University of Oslo Faculty of Law Legal Studies Research Paper Series No.2017-20, 10-11.
- WP29 (n 4) 21.
- Ibid 8; Bygrave (n 2) 533.
- Bygrave (n 2) 533.
- WP29 (n 4) 21, Brkan (n 7) 102.
- See also Articles 4(11) and 7(4), as well as Recital 43.
- Brkan (n 7) 106.
- Brkan (n7) 108.