Article 11 GDPR: Difference between revisions

From GDPRhub
No edit summary
 
(29 intermediate revisions by 9 users not shown)
Line 184: Line 184:
|}
|}


==Legal Text==
== Legal Text ==
<center>'''Article 11: Processing which does not require identification'''</center><span id="1"> 1. If the purposes for which a controller processes personal data do not or do no longer require the identification of a data subject by the controller, the controller shall not be obliged to maintain, acquire or process additional information in order to identify the data subject for the sole purpose of complying with this Regulation.</span>
<br /><center>'''Article 11: Processing which does not require identification'''</center>
 
<span id="1"> 1. If the purposes for which a controller processes personal data do not or do no longer require the identification of a data subject by the controller, the controller shall not be obliged to maintain, acquire or process additional information in order to identify the data subject for the sole purpose of complying with this Regulation.</span>


<span id="1"> 2. Where, in cases referred to in paragraph 1 of this Article, the controller is able to demonstrate that it is not in a position to identify the data subject, the controller shall inform the data subject accordingly, if possible. In such cases, Articles 15 to 20 shall not apply except where the data subject, for the purpose of exercising his or her rights under those articles, provides additional information enabling his or her identification.</span>
<span id="1"> 2. Where, in cases referred to in paragraph 1 of this Article, the controller is able to demonstrate that it is not in a position to identify the data subject, the controller shall inform the data subject accordingly, if possible. In such cases, Articles 15 to 20 shall not apply except where the data subject, for the purpose of exercising his or her rights under those articles, provides additional information enabling his or her identification.</span>
==Relevant Recitals==
==Relevant Recitals==
'''Recital 57:''' Processing which does not require identification
{{Recital/26 GDPR}}{{Recital/57 GDPR}}{{Recital/64 GDPR}}


If the personal data processed by a controller do not permit the controller to identify a natural person, the data controller should not be obliged to acquire additional information in order to identify the data subject for the sole purpose of complying with any provision of this Regulation.
However, th<span id="r57">[[Category:GDPR Articles]]e controller should not refuse to take additional information provided by the data subject in order to support the exercise of his or her rights.
Identification should include the digital identification of a data subject, for example through authentication mechanism such as the same credentials, used by the data subject to log-in to the on-line service offered by the data controller.
'''Recital 64:''' Verification of the data subject's identity
The controller should use all reasonable measures to verify the identity of a data subject who requests access, in particular in the context of online services and online identifiers.
A controller should not retain personal data for the sole purpose of being able to react to potential requests.
<span id="r57">
==Commentary==
==Commentary==


==Article 11(1) Processing which does not require identification==
Article 11 regulates the processing of personal data that does not require the identification of the data subject.<blockquote><u>Example:</u> A controller wants to analyze the performance of one of its shops. This requires the collection of the aggregate purchases of customers, but not their identification.</blockquote>In such cases, the controller is not obliged to acquire additional information in order to identify the data subject for the sole purpose of complying with the GDPR.


This also follows from the principles of minimization and necessity. These principles require controllers to de-identify personal data (through deletion, anonymisation, pseudo-anonymisation, etc.) as far as possible for their respective purposes.  
The data minimisation principle in [[Article 5 GDPR|Article 5(1)(c) GDPR]] limits controllers in their processing operations, as it specifically requires them to only process data which is necessary for the fulfilment of specific purposes. During the legislative process there were worries, that the GDPR could be interpreted to require processing more personal data, just to comply with certain requirements and rights of the data subjects - which would be counterproductive. Article 11 GDPR is meant to address this matter.


==Article 11(2) Legal consequences of the impossibility to identify the data subject==
Under Article 11(1) GDPR, when a processing operation does not or no longer requires the identification of the data subject, then the controller should act accordingly, deleting or otherwise hiding the identifying reference to the data subject. When this happens, the controller is not obliged to process additional information about the data subject for the sole purpose of GDPR compliance.  
Under [[Article 12 GDPR#2|Article 11(2)]], if identification is not possible, Articles 15 to 20 do not apply, except where the data subject, for the purpose of exercising their rights under those articles, provides additional information enabling their identification.


===='''GDPR still applies in part'''====
Article 11(2) GDPR provides for an important exception to the above-mentioned rule. If a data subject wants to exercise their GDPR rights and to that extent provides further information allowing their (re)identification, the controller shall consider that information and, if possible, address the request.
Under the conditions of Article 11(1), Article 11(2) excludes the applicability of Articles 15 to 20. It follows that all other requirements of the GDPR that are not expressly excluded should remain applicable, including, but not limited to, security of processing ([https://gdprhub.eu/index.php?title=Article_32_GDPR Article 32(1)]) and the general principles of processing set out in [https://gdprhub.eu/index.php?title=Article_5_GDPR Article 5].


===='''Burden of proof'''====
Article 11 GDPR only address the use of personal data. There are many other duties under the GDPR which regularly require the keeping of records, proof or evidence. They are not affected by Article 11 GDPR.
The controller must be able to demonstrate the impossibility of identifying the data subject.  


<span id="r57">The demonstration should provide a fair explanation of the reasons why the controller is unable to identify the data subject.
==== (1) If the data subject is not identified, the GDPR applies in part ====
Article 11 GDPR applies when “''personal data do not or do no longer require the identification of a data subject''”. One could think that this refers to an anonymisation scenario, but this conclusion would make little sense. First, the GDPR does not apply to anonymous data. Second, under Article 11(2) GDPR, it would be impossible to inform a data subject who is not identifiable.<ref>''Georgieva'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 11 GDPR, p. 395 (Oxford University Press 2020).


<span id="r57">Due to the fairness and transparency principle ([https://gdprhub.eu/index.php?title=Article_5_GDPR#.28a.29_Lawfulness.2C_fairness_and_transparency Article 5(1)(a)]), generic or circular arguments ("''Our systems are unable to identify your data''") are too broad to meet the requirement of a proper demonstration.
</ref>


===='''Obligation to inform'''====
Under Article 4(1) GDPR, personal data means any information relating to an “''identified''” or “''identifiable”'' natural person'''''.''''' Looking attentively at the wording of Article 11(1) GDPR, it is clear that the provision only covers situations in which the data subject is not or no longer “''identified''”,<ref>Indeed, certain processing operations require the collection of personal data, but not necessarily the (ongoing) identification,of the data subject. It can be assumed that in general business transactions only a few use cases under Article 11(1) exist because the business purpose usually requires identification of the business partner, for example to carry out deliveries, to assess creditworthiness or to maintain business correspondence.</ref> but clearly excludes cases where they are still “''identifiable''. In other words, the provision applies in case of pseudonymisation which, according to Recital 26, refers to information about an identifiable person. In the case of pseudonymisation, regardless whether it was implemented from the beginning (“''does not require''”) or at a later stage (“''does no longer require''”) of the processing operation, the GDPR grants the controller a privilege which reflects the favour towards data minimisation, storage limitation and data security. In particular, the controller shall not be obliged to retain, obtain or process further information about the individual if such information is needed to identify them and comply with one or more part of the GDPR.  
[[Article 12 GDPR#2|Article 12(2)]] provides for a peculiar informative obligation ("''Where [...] the controller is able to demonstrate that it is not in a position to identify the data subject, the controller shall inform the data subject accordingly, if possible''").


Such an information, which is clearly different from the one received under Articles 13 - 22 GDPR, seems particularly important as it allows the data subject to assess the allegedly non-identifying processing and, where the case, provide additional information enabling the identification.
This privilege is not absolute but refers exclusively to those parts of the GDPR that require the identification of the data subject.<ref>''Kampert,'' in Sydow, Europäische Datenschutzgrundverordnung, Article 11 GDPR, margin number 7 (C.H. Beck 2018, 2<sup>nd</sup> Edition).</ref> Some examples are possible. Take the case of the Google Street View. This process undoubtedly involves the collection of some personal data of inhabitants and their homes. However, it is argued, Google would probably not be obliged to collect the contact details of individual inhabitants in order to inform them of the processing under Articles 13 or 14 GDPR. This can be drawn from the final sentence of Article 11(1) GDPR.<ref>For this and other examles, see Gola, Datenschutz-Grund-verordnung, Article 11 GDPR, margin number 2 (C.H. Beck 2018, 2<sup>nd</sup> Edition).</ref>


For this reason, the controller should provide information tailored to the specific case and, in particular, explain why the identification is not possible. Furthermore, in application of the principle of fairness in the processing of personal data, the controller should indicate in advance which data the data subject should provide for its (re)identification.
It must be assessed with the utmost attention whether GDPR provisions require the identification of the data subject,  and under no circumstances should Article 11(1) GDPR be regarded as a carte blanche for the transgression of data protection regulations. <span lang="EN-GB">The data minimisation principle limits controllers in their processing operations, as it specifically requires them to only process data which is necessary for the fulfilment of specific purposes. Under Article 11(1) GDPR, when a processing operation does not or no longer requires the identification of the data subject, then the controller should act accordingly, deleting or otherwise hiding the identifying reference to the data subject. When this happens, the controller is not obliged to obtain additional information about the data subject for the sole purpose of GDPR compliance. Article 11(2) GDPR provides for an important exception to the above-mentioned rule. If a data subject wants to exercise their GDPR rights and to that extent provides further information allowing their (re)identification, the controller shall consider that information and, if possible, address the request. </span><ref>''Kampert,'' in Sydow, Europäische Datenschutzgrundverordnung, Article 11 GDPR, margin number 7 (C.H. Beck 2018, 2<sup>nd</sup> Edition).</ref> In particular, all other GDPR requirements that do not require the data subject’s identification remain applicable, including, but not limited to, security of processing ([[Article 32 GDPR|Article 32(1) GDPR]]) and the general principles of processing set out in [[Article 5 GDPR]].
==== (2) If the data subject exercises their rights, the controller must try the identification ====
In confirming the above interpretation, Paragraph 2 sets out a specific framework for the case that a data subject exercises their rights under Articles 15 to 20 GDPR. By definition, this situation requires the identification of the data subject, as a right only exists insofar as it is given to a specific person and they exercise it. In such circumstances, if, after pseudonymisation ("''In cases referred to in paragraph 1 of this Article''"), the controller receives a request to exercise the data subject’s right, but for technical reasons is unable to identify them, the controller must (i) prove this impossibility and (ii) inform the data subject of the reasons which render the request impossible. This will suffice to stay the claim ("''In such cases, Articles 15 to 20 shall not apply''") unless the data subject provides additional information allowing their identification. If their identification is possible following the receipt of the additional information, the exception will not apply and the controller shall comply with the data subject’s request.


===='''Obligation to accept and assess the additional information'''====
===== Burden of Proof =====
If the data subject provides further information, the controller must receive it and, under [[Article 12 GDPR#2|Article 12(2)]], try its best to identify the data subject. The controller should also provide the data subject with a pre-defined description of what kind of additional information is needed to (re)identify the data subject.  
The controller must be able to demonstrate that identifying the data subject is impossible. This demonstration should provide a transparent explanation of the reasons why the controller is unable to do so. Generic or circular arguments (e.g. "''Our systems are unable to identify your data''") do not meet the requirement of a proper demonstration under the fairness and transparency principle ([[Article 5 GDPR|Article 5(1)(a) GDPR]]).


In this regard, the Working Party 29 has already invited stakeholders "''to elaborate, precisely with reference to Article 11 calls for proposals from the C-ITS WG on the concept of ‘additional information’ that can be provided in the context of this new service to make this provision effective''".<ref>WP29, Opinion 3/2017 on processing personal data in the context of Cooperative Intelligent Transport Systems, p. 7.</ref>
===== Obligation to Inform =====
Article 11(2) GDPR provides for a peculiar informative obligation ("''Where [...] the controller is able to demonstrate that it is not in a position to identify the data subject, the controller shall inform the data subject accordingly, if possible''"). Such information is clearly different from that received under Articles 13 or 14 GDPR, and is particularly important as it allows the data subject to evaluate the allegedly non-identifying processing, as well as provide additional information to enable their identification. The controller should therefore provide tailored information and explain why identification is not possible. Furthermore, to comply with the principle of fairness the controller should indicate in advance which data the data subject should provide for their (re)identification.<ref>In this regard, the WP29 has already invited stakeholders "''to elaborate, precisely with reference to Article 11 calls for proposals from the C-ITS WG on the concept of ‘additional information’ that can be provided in the context of this new service to make this provision effective''". WP29, Opinion 3/2017 on processing personal data in the context of Cooperative Intelligent Transport Systems, p. 7.</ref>


==Decisions==
==Decisions==
Line 241: Line 229:
==References==
==References==
<references />
<references />
[[Category:GDPR Articles]]

Latest revision as of 16:32, 8 March 2024

Article 11: Processing which does not require identification
Gdpricon.png
Chapter 10: Delegated and implementing acts

Legal Text


Article 11: Processing which does not require identification

1. If the purposes for which a controller processes personal data do not or do no longer require the identification of a data subject by the controller, the controller shall not be obliged to maintain, acquire or process additional information in order to identify the data subject for the sole purpose of complying with this Regulation.

2. Where, in cases referred to in paragraph 1 of this Article, the controller is able to demonstrate that it is not in a position to identify the data subject, the controller shall inform the data subject accordingly, if possible. In such cases, Articles 15 to 20 shall not apply except where the data subject, for the purpose of exercising his or her rights under those articles, provides additional information enabling his or her identification.

Relevant Recitals

Recital 26: Applicable to Pseudonymous Data, Not Applicable to Anonymous Data
The principles of data protection should apply to any information concerning an identified or identifiable natural person. Personal data which have undergone pseudonymisation, which could be attributed to a natural person by the use of additional information should be considered to be information on an identifiable natural person. To determine whether a natural person is identifiable, account should be taken of all the means reasonably likely to be used, such as singling out, either by the controller or by another person to identify the natural person directly or indirectly. To ascertain whether means are reasonably likely to be used to identify the natural person, account should be taken of all objective factors, such as the costs of and the amount of time required for identification, taking into consideration the available technology at the time of the processing and technological developments. The principles of data protection should therefore not apply to anonymous information, namely information which does not relate to an identified or identifiable natural person or to personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable. This Regulation does not therefore concern the processing of such anonymous information, including for statistical or research purposes.

Recital 57: Additional Information for Identification
If the personal data processed by a controller do not permit the controller to identify a natural person, the data controller should not be obliged to acquire additional information in order to identify the data subject for the sole purpose of complying with any provision of this Regulation. However, the controller should not refuse to take additional information provided by the data subject in order to support the exercise of his or her rights. Identification should include the digital identification of a data subject, for example through authentication mechanism such as the same credentials, used by the data subject to log-in to the on-line service offered by the data controller.

Recital 64: Identity Verification
The controller should use all reasonable measures to verify the identity of a data subject who requests access, in particular in the context of online services and online identifiers. A controller should not retain personal data for the sole purpose of being able to react to potential requests.

Commentary

The data minimisation principle in Article 5(1)(c) GDPR limits controllers in their processing operations, as it specifically requires them to only process data which is necessary for the fulfilment of specific purposes. During the legislative process there were worries, that the GDPR could be interpreted to require processing more personal data, just to comply with certain requirements and rights of the data subjects - which would be counterproductive. Article 11 GDPR is meant to address this matter.

Under Article 11(1) GDPR, when a processing operation does not or no longer requires the identification of the data subject, then the controller should act accordingly, deleting or otherwise hiding the identifying reference to the data subject. When this happens, the controller is not obliged to process additional information about the data subject for the sole purpose of GDPR compliance.

Article 11(2) GDPR provides for an important exception to the above-mentioned rule. If a data subject wants to exercise their GDPR rights and to that extent provides further information allowing their (re)identification, the controller shall consider that information and, if possible, address the request.

Article 11 GDPR only address the use of personal data. There are many other duties under the GDPR which regularly require the keeping of records, proof or evidence. They are not affected by Article 11 GDPR.

(1) If the data subject is not identified, the GDPR applies in part

Article 11 GDPR applies when “personal data do not or do no longer require the identification of a data subject”. One could think that this refers to an anonymisation scenario, but this conclusion would make little sense. First, the GDPR does not apply to anonymous data. Second, under Article 11(2) GDPR, it would be impossible to inform a data subject who is not identifiable.[1]

Under Article 4(1) GDPR, personal data means any information relating to an “identified” or “identifiable” natural person. Looking attentively at the wording of Article 11(1) GDPR, it is clear that the provision only covers situations in which the data subject is not or no longer “identified”,[2] but clearly excludes cases where they are still “identifiable”. In other words, the provision applies in case of pseudonymisation which, according to Recital 26, refers to information about an identifiable person. In the case of pseudonymisation, regardless whether it was implemented from the beginning (“does not require”) or at a later stage (“does no longer require”) of the processing operation, the GDPR grants the controller a privilege which reflects the favour towards data minimisation, storage limitation and data security. In particular, the controller shall not be obliged to retain, obtain or process further information about the individual if such information is needed to identify them and comply with one or more part of the GDPR.

This privilege is not absolute but refers exclusively to those parts of the GDPR that require the identification of the data subject.[3] Some examples are possible. Take the case of the Google Street View. This process undoubtedly involves the collection of some personal data of inhabitants and their homes. However, it is argued, Google would probably not be obliged to collect the contact details of individual inhabitants in order to inform them of the processing under Articles 13 or 14 GDPR. This can be drawn from the final sentence of Article 11(1) GDPR.[4]

It must be assessed with the utmost attention whether GDPR provisions require the identification of the data subject,  and under no circumstances should Article 11(1) GDPR be regarded as a carte blanche for the transgression of data protection regulations. The data minimisation principle limits controllers in their processing operations, as it specifically requires them to only process data which is necessary for the fulfilment of specific purposes. Under Article 11(1) GDPR, when a processing operation does not or no longer requires the identification of the data subject, then the controller should act accordingly, deleting or otherwise hiding the identifying reference to the data subject. When this happens, the controller is not obliged to obtain additional information about the data subject for the sole purpose of GDPR compliance. Article 11(2) GDPR provides for an important exception to the above-mentioned rule. If a data subject wants to exercise their GDPR rights and to that extent provides further information allowing their (re)identification, the controller shall consider that information and, if possible, address the request. [5] In particular, all other GDPR requirements that do not require the data subject’s identification remain applicable, including, but not limited to, security of processing (Article 32(1) GDPR) and the general principles of processing set out in Article 5 GDPR.

(2) If the data subject exercises their rights, the controller must try the identification

In confirming the above interpretation, Paragraph 2 sets out a specific framework for the case that a data subject exercises their rights under Articles 15 to 20 GDPR. By definition, this situation requires the identification of the data subject, as a right only exists insofar as it is given to a specific person and they exercise it. In such circumstances, if, after pseudonymisation ("In cases referred to in paragraph 1 of this Article"), the controller receives a request to exercise the data subject’s right, but for technical reasons is unable to identify them, the controller must (i) prove this impossibility and (ii) inform the data subject of the reasons which render the request impossible. This will suffice to stay the claim ("In such cases, Articles 15 to 20 shall not apply") unless the data subject provides additional information allowing their identification. If their identification is possible following the receipt of the additional information, the exception will not apply and the controller shall comply with the data subject’s request.

Burden of Proof

The controller must be able to demonstrate that identifying the data subject is impossible. This demonstration should provide a transparent explanation of the reasons why the controller is unable to do so. Generic or circular arguments (e.g. "Our systems are unable to identify your data") do not meet the requirement of a proper demonstration under the fairness and transparency principle (Article 5(1)(a) GDPR).

Obligation to Inform

Article 11(2) GDPR provides for a peculiar informative obligation ("Where [...] the controller is able to demonstrate that it is not in a position to identify the data subject, the controller shall inform the data subject accordingly, if possible"). Such information is clearly different from that received under Articles 13 or 14 GDPR, and is particularly important as it allows the data subject to evaluate the allegedly non-identifying processing, as well as provide additional information to enable their identification. The controller should therefore provide tailored information and explain why identification is not possible. Furthermore, to comply with the principle of fairness the controller should indicate in advance which data the data subject should provide for their (re)identification.[6]

Decisions

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

References

  1. Georgieva, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 11 GDPR, p. 395 (Oxford University Press 2020).
  2. Indeed, certain processing operations require the collection of personal data, but not necessarily the (ongoing) identification,of the data subject. It can be assumed that in general business transactions only a few use cases under Article 11(1) exist because the business purpose usually requires identification of the business partner, for example to carry out deliveries, to assess creditworthiness or to maintain business correspondence.
  3. Kampert, in Sydow, Europäische Datenschutzgrundverordnung, Article 11 GDPR, margin number 7 (C.H. Beck 2018, 2nd Edition).
  4. For this and other examles, see Gola, Datenschutz-Grund-verordnung, Article 11 GDPR, margin number 2 (C.H. Beck 2018, 2nd Edition).
  5. Kampert, in Sydow, Europäische Datenschutzgrundverordnung, Article 11 GDPR, margin number 7 (C.H. Beck 2018, 2nd Edition).
  6. In this regard, the WP29 has already invited stakeholders "to elaborate, precisely with reference to Article 11 calls for proposals from the C-ITS WG on the concept of ‘additional information’ that can be provided in the context of this new service to make this provision effective". WP29, Opinion 3/2017 on processing personal data in the context of Cooperative Intelligent Transport Systems, p. 7.