Article 30 GDPR: Difference between revisions
No edit summary |
|||
Line 223: | Line 223: | ||
==Commentary== | ==Commentary== | ||
Article 30 GDPR requires controllers and processors to maintain a record of processing activities (Article 4(2) GDPR). This obligation represents the expression of several data processing principles. On the one hand, it promotes accountability by allowing the controller to keep track of its processing and amend it where necessary. On the other hand, it increases the overall transparency of the processing and makes it easier for data subjects to exercise their rights. In practice, the record of processing activities is | Article 30 GDPR requires controllers and processors to maintain a "''record of processing activities''" (Article 4(2) GDPR).<ref>This obligation, which replaces the old notification obligation where data processing activities had to be notified to DPAs (Articles 18-19 Directive 95/46/EC), represents the expression of several data processing principles. On the one hand, it promotes accountability by allowing the controller to keep track of its processing and amend it where necessary. On the other hand, it increases the overall transparency of the processing and makes it easier for data subjects to exercise their rights. In practice, the record of processing activities is an updated written account of the main elements of the processing.</ref> Paragraph 1 specifies the information that the controller must include in the record. Paragraph 2 serves the same purpose, but it is addressed to the processor. Paragraph 3 clarifies that the record must be in written form, possibly also in electronic form. The following paragraph, paragraph 4, states that the record must be provided to supervisory authorities when they request it. Finally, the last paragraph establishes exceptions to the obligation to keep the record for controllers and processors with fewer than 250 employees, unless additional conditions are met. | ||
=== (1) Record of | === (1) Record of processing activities by the controller === | ||
Article 30(1) GDPR provides a | Article 30(1) GDPR provides a list of the elements that must be contained in the record of processing activities carried out by the controller. If the controller is located outside the EU, then its representative in the EU under Article 27 GDPR is subject to this obligation. | ||
Article 30(1)(a) states it should contain the name and contact details of the controller and, where applicable, the joint controller(s), the controller's representative and the data protection officer. This information is intended to enable an unambiguous identification of the controller(s) and whoever else is responsible under the GDPR. The notion of 'contact details' is not limited to a simple email address. It must contain all the elements (physical address, telephone number, contact person)<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 30, margin number 17 (C.H.Beck 2020, 3rd Edition).</ref> | ==== (a) Contact details ==== | ||
Article 30(1)(a) states it should contain the name and contact details of the controller and, where applicable, the joint controller(s),<ref>In case of joint controllership, it is necessary to list the names and contact details of all joint controllers (Article 26(1) GDPR). ''Petri'', in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 30 GDPR, margin number 14 (C.H. Beck 2019).</ref> the controller's representative and the data protection officer. This information is intended to enable an unambiguous identification of the controller(s) and whoever else is responsible under the GDPR. The notion of 'contact details' is not limited to a simple email address. It must contain all the elements (physical address, telephone number, contact person) that make it possible to contact a particular person or, where appropriate, reach them for an inspection.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 30, margin number 17 (C.H.Beck 2020, 3rd Edition).</ref> | |||
Article 30(1)(b) requires the controller to provide a description of the purposes of the processing. | ==== (b) Purposes of the processing ==== | ||
Article 30(1)(b) requires the controller to provide a description of the purposes of the processing. In accordance with Article 5(2)(b), purposes must be determined prior to the data collection and, in principle, subsequent processing is only allowed for such pre-specified purposes, which must be clear and transparent to enable the supervisory authority to assess the adequacy of safeguards implemented and the lawfulness of the processing during potential audits.<ref>''Bertermann'', in Ehmann, Selmayr, Datenschutz-Grundverordnung, Article 30 GDPR, margin number 10 (C.H. Beck 2018, 2nd Edition).</ref> | |||
Speaking of lawfulness, the provision does not require to mention the legal basis upon which a certain purpose relies. This gap should be filled by interpreting the text in line with the principle of accountability. If a controller must demonstrate compliance with the GDPR, then it must have a "''firm and reasoned notion about the legal basis of processing before it starts any operation, and this notion should be verifiable by means of its records. Thus, in order for the keeping of records to be meaningful, it will be necessary for the controller to be able to demonstrate on which legal basis it relies in its processing''".<ref>''Kotschy'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 30 GDPR, p. 620 (Oxford University Press 2020).</ref> | |||
Article 30(1)(d) prescribes that controllers should describe the categories of recipients to whom personal data have been or will be disclosed. The wording of the provision suggests that only the categories of addressees have to be indicated, such as "''suppliers''", "''accountants''", "''marketing consultants''", or "''legal advisors''". However, this ambiguity does not seem advisable, as other provisions of the GDPR require the controller to keep track of individual recipients. For example, Article 15(1)(c) GDPR and Article 19 GDPR require the disclosure of “''recipients or categories of recipients''” and specific recipients “''if the data subject requests it''” respectively. As such, it would go against its aim of increasing accountability to not specify the recipients in the record of processing activities.<ref>In a broadly similar sense, ''Kotschy'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 30 GDPR, p. 620 (Oxford University Press 2020).</ref> | ==== (c) Categories of data subjects and of personal data ==== | ||
Article 30(1)(c) GDPR establishes that the record of processing activities shall describe the categories of data subjects and the categories of personal data. Examples of categories of data subjects are "''website visitors''", "''clinic patients''", "''employees''". Categories of personal data may be "''website clicks''", "''diagnosis''", "''holiday leave''", as well as "''union affiliations''". Scholars have highlighted that each category of personal data should be tied to the category of data subject it belongs to. For example, the record of processing activities should clearly show that the two categories "''holiday leave''" and "''union affiliations''" are processed with regard to the "''employees''" category.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 30, margin number 19 (C.H.Beck 2020, 3rd Edition).</ref> | |||
==== (d) Categories of recipients ==== | |||
Article 30(1)(d) prescribes that controllers should describe the categories of recipients to whom personal data have been or will be disclosed. The wording of the provision suggests that only the categories of addressees have to be indicated, such as "''suppliers''", "''accountants''", "''marketing consultants''", or "''legal advisors''". However, this ambiguity does not seem advisable, as other provisions of the GDPR require the controller to keep track of individual recipients. For example, Article 15(1)(c) GDPR and Article 19 GDPR require the disclosure of “''recipients or categories of recipients''” and specific recipients “''if the data subject requests it''” respectively. Based on the same logical and legal premises, the European Court of Justice has recently clarified that, if requested by the data subject, the controller is obliged to provide a specific list of recipients.<ref>CJEU, C-154/21, ''RW v Österreichische Post'', 12 January 2023, among the others, margin number 24 (available [[CJEU - C-154/21 - RW v Österreichische Post|here]]).</ref> As such, it would go against its aim of increasing accountability to not specify the recipients in the record of processing activities.<ref>In a broadly similar sense, ''Kotschy'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 30 GDPR, p. 620 (Oxford University Press 2020).</ref> | |||
(e) | |||
In accordance with Article 30(1)(e), the controller shall provide information regarding the transfers of personal data to a third country or an international organisation and, in the case of the applicability of [[Article 49 GDPR|Article 49(1) GDPR]], the documentation of suitable safeguards. There is no obligation to name the means by which the controller intends to "''ensure an adequate level of protection on the part of the foreign recipient of the data. Additional information is needed only if a data transfer shall, exceptionally, be based on Article 49(1), second subparagraph, which pertains to occasional ('non-repetitive') transfers of data about a limited number of data subjects and for compelling legitimate interests''".<ref>''Kotschy'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 30 GDPR, p. 622 (Oxford University Press 2020).</ref> | In accordance with Article 30(1)(e), the controller shall provide information regarding the transfers of personal data to a third country or an international organisation and, in the case of the applicability of [[Article 49 GDPR|Article 49(1) GDPR]], the documentation of suitable safeguards. There is no obligation to name the means by which the controller intends to "''ensure an adequate level of protection on the part of the foreign recipient of the data. Additional information is needed only if a data transfer shall, exceptionally, be based on Article 49(1), second subparagraph, which pertains to occasional ('non-repetitive') transfers of data about a limited number of data subjects and for compelling legitimate interests''".<ref>''Kotschy'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 30 GDPR, p. 622 (Oxford University Press 2020).</ref> |
Revision as of 08:57, 5 June 2023
Legal Text
1. Each controller and, where applicable, the controller's representative, shall maintain a record of processing activities under its responsibility. That record shall contain all of the following information:
- (a) the name and contact details of the controller and, where applicable, the joint controller, the controller's representative and the data protection officer;
- (b) the purposes of the processing;
- (c) a description of the categories of data subjects and of the categories of personal data;
- (d) the categories of recipients to whom the personal data have been or will be disclosed including recipients in third countries or international organisations;
- (e) where applicable, transfers of personal data to a third country or an international organisation, including the identification of that third country or international organisation and, in the case of transfers referred to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
- (f) where possible, the envisaged time limits for erasure of the different categories of data;
- (g) where possible, a general description of the technical and organisational security measures referred to in Article 32(1).
2. Each processor and, where applicable, the processor's representative shall maintain a record of all categories of processing activities carried out on behalf of a controller, containing:
- (a) the name and contact details of the processor or processors and of each controller on behalf of which the processor is acting, and, where applicable, of the controller's or the processor's representative, and the data protection officer;
- (b) the categories of processing carried out on behalf of each controller;
- (c) where applicable, transfers of personal data to a third country or an international organisation, including the identification of that third country or international organisation and, in the case of transfers referred to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
- (d) where possible, a general description of the technical and organisational security measures referred to in Article 32(1).
3. The records referred to in paragraphs 1 and 2 shall be in writing, including in electronic form.
4. The controller or the processor and, where applicable, the controller's or the processor's representative, shall make the record available to the supervisory authority on request.
5. The obligations referred to in paragraphs 1 and 2 shall not apply to an enterprise or an organisation employing fewer than 250 persons unless the processing it carries out is likely to result in a risk to the rights and freedoms of data subjects, the processing is not occasional, or the processing includes special categories of data as referred to in Article 9(1) or personal data relating to criminal convictions and offences referred to in Article 10.
Relevant Recitals
Commentary
Article 30 GDPR requires controllers and processors to maintain a "record of processing activities" (Article 4(2) GDPR).[1] Paragraph 1 specifies the information that the controller must include in the record. Paragraph 2 serves the same purpose, but it is addressed to the processor. Paragraph 3 clarifies that the record must be in written form, possibly also in electronic form. The following paragraph, paragraph 4, states that the record must be provided to supervisory authorities when they request it. Finally, the last paragraph establishes exceptions to the obligation to keep the record for controllers and processors with fewer than 250 employees, unless additional conditions are met.
(1) Record of processing activities by the controller
Article 30(1) GDPR provides a list of the elements that must be contained in the record of processing activities carried out by the controller. If the controller is located outside the EU, then its representative in the EU under Article 27 GDPR is subject to this obligation.
(a) Contact details
Article 30(1)(a) states it should contain the name and contact details of the controller and, where applicable, the joint controller(s),[2] the controller's representative and the data protection officer. This information is intended to enable an unambiguous identification of the controller(s) and whoever else is responsible under the GDPR. The notion of 'contact details' is not limited to a simple email address. It must contain all the elements (physical address, telephone number, contact person) that make it possible to contact a particular person or, where appropriate, reach them for an inspection.[3]
(b) Purposes of the processing
Article 30(1)(b) requires the controller to provide a description of the purposes of the processing. In accordance with Article 5(2)(b), purposes must be determined prior to the data collection and, in principle, subsequent processing is only allowed for such pre-specified purposes, which must be clear and transparent to enable the supervisory authority to assess the adequacy of safeguards implemented and the lawfulness of the processing during potential audits.[4]
Speaking of lawfulness, the provision does not require to mention the legal basis upon which a certain purpose relies. This gap should be filled by interpreting the text in line with the principle of accountability. If a controller must demonstrate compliance with the GDPR, then it must have a "firm and reasoned notion about the legal basis of processing before it starts any operation, and this notion should be verifiable by means of its records. Thus, in order for the keeping of records to be meaningful, it will be necessary for the controller to be able to demonstrate on which legal basis it relies in its processing".[5]
(c) Categories of data subjects and of personal data
Article 30(1)(c) GDPR establishes that the record of processing activities shall describe the categories of data subjects and the categories of personal data. Examples of categories of data subjects are "website visitors", "clinic patients", "employees". Categories of personal data may be "website clicks", "diagnosis", "holiday leave", as well as "union affiliations". Scholars have highlighted that each category of personal data should be tied to the category of data subject it belongs to. For example, the record of processing activities should clearly show that the two categories "holiday leave" and "union affiliations" are processed with regard to the "employees" category.[6]
(d) Categories of recipients
Article 30(1)(d) prescribes that controllers should describe the categories of recipients to whom personal data have been or will be disclosed. The wording of the provision suggests that only the categories of addressees have to be indicated, such as "suppliers", "accountants", "marketing consultants", or "legal advisors". However, this ambiguity does not seem advisable, as other provisions of the GDPR require the controller to keep track of individual recipients. For example, Article 15(1)(c) GDPR and Article 19 GDPR require the disclosure of “recipients or categories of recipients” and specific recipients “if the data subject requests it” respectively. Based on the same logical and legal premises, the European Court of Justice has recently clarified that, if requested by the data subject, the controller is obliged to provide a specific list of recipients.[7] As such, it would go against its aim of increasing accountability to not specify the recipients in the record of processing activities.[8]
(e)
In accordance with Article 30(1)(e), the controller shall provide information regarding the transfers of personal data to a third country or an international organisation and, in the case of the applicability of Article 49(1) GDPR, the documentation of suitable safeguards. There is no obligation to name the means by which the controller intends to "ensure an adequate level of protection on the part of the foreign recipient of the data. Additional information is needed only if a data transfer shall, exceptionally, be based on Article 49(1), second subparagraph, which pertains to occasional ('non-repetitive') transfers of data about a limited number of data subjects and for compelling legitimate interests".[9]
Finally, Article 30(1)(f) and (g) GDPR respectively require controllers to clarify the envisaged time limits for erasure of different categories of data and, where possible, provide general description of the technical and organisational security measures referred to in Article 32(1) GDPR.
(2) Record of Processing Activities by the Processor
Article 30(2) GDPR sets out the rules governing the maintenance of records of processing activities by the processor. These rules, which partly overlap with those established by Article 30(1) GDPR, notably provide for an obligation on the processor to record: the name and contact details of the controller on behalf of which the processor is acting as well as the name and contact details of other processors (Article 30(2)(a) GDPR);[10] the categories of processing carried out on behalf of each controller (Article 30(2)(b) GDPR); where applicable, information on the transfers of personal data to a third country or an international organisation and, in the case of the applicability of Article 49(1) GDPR, the documentation of suitable safeguards (Article 30(2)(c) GDPR); a general description of the technical and organisational security measures referred to in Article 32(1) GDPR (Article 30(2)(d) GDPR).
(3) Written Form
The records of processing activities shall be in writing, including in electronic form, and kept up to date. This enables controllers to provide DPAs with the records when requested under Article 30(4) GDPR and to comply with, inter alia, the principles of accountability and transparency.[11] Any changes to the processing operation have to be transparent and traceable (e.g. who has been the controller, processor or data protection officer – and when). Moreover, “in order to be able to track changes to the entries in the directory (e.g. who was responsible when, data protection officer, etc.), the changes should be documented with a storage period of one year.”[12]
(4) Provision to Supervisory Authority
Supervisory authorities can investigate controllers and processor as general control measure, but also where data breaches have occurred and data subjects have filed complaints. Records of processing activities therefore have to be available at any time to be provided to DPAs upon request.
(5) Exceptions
EDPB Guidelines: On this provision there is the Working Party 29 Position Paper on the derogations from the obligation to maintain records of processing activities pursuant to Article 30(5) GDPR.
An enterprise or an organisation employing less than 250 persons is not obliged to maintain records of processing. However, this exception does not apply if an organisation carries out processing that is likely to result in a risk to the rights and freedoms of data subjects, the processing is not occasional, or the processing includes special categories of data (Article 9(1) GDPR) or personal data relating to criminal convictions and offences referred to in Article 10 GDPR.
Decisions
→ You can find all related decisions in Category:Article 30 GDPR
References
- ↑ This obligation, which replaces the old notification obligation where data processing activities had to be notified to DPAs (Articles 18-19 Directive 95/46/EC), represents the expression of several data processing principles. On the one hand, it promotes accountability by allowing the controller to keep track of its processing and amend it where necessary. On the other hand, it increases the overall transparency of the processing and makes it easier for data subjects to exercise their rights. In practice, the record of processing activities is an updated written account of the main elements of the processing.
- ↑ In case of joint controllership, it is necessary to list the names and contact details of all joint controllers (Article 26(1) GDPR). Petri, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 30 GDPR, margin number 14 (C.H. Beck 2019).
- ↑ Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 30, margin number 17 (C.H.Beck 2020, 3rd Edition).
- ↑ Bertermann, in Ehmann, Selmayr, Datenschutz-Grundverordnung, Article 30 GDPR, margin number 10 (C.H. Beck 2018, 2nd Edition).
- ↑ Kotschy, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 30 GDPR, p. 620 (Oxford University Press 2020).
- ↑ Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 30, margin number 19 (C.H.Beck 2020, 3rd Edition).
- ↑ CJEU, C-154/21, RW v Österreichische Post, 12 January 2023, among the others, margin number 24 (available here).
- ↑ In a broadly similar sense, Kotschy, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 30 GDPR, p. 620 (Oxford University Press 2020).
- ↑ Kotschy, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 30 GDPR, p. 622 (Oxford University Press 2020).
- ↑ "Which kind of processors should be included is not explained: they could be involved either by having delegated processing tasks to the documenting processor or by being sub-processors of the documenting processor. In both cases there would have to exist a contract between the documenting processor and the orher processor or processors, in which case their identity must be known and recorded anyway by the documenting processor, which is also the case with regard to the names of the representative (Article 27) and data protection officer (Article 37) both of which are also required under Article 30(2)(a)." See Kotschy, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 30 GDPR, p. 623 (Oxford University Press 2020).
- ↑ Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 30, margin number 31 (C.H.Beck 2020, 3rd Edition).
- ↑ DSK, Datenschutzkonferenz, ‘Hinweise zum Verzeichnis von Verarbeitungstätigkeiten’, Art. 30 DS-GVO, February 2018, p. 3 (available here).