Article 30 GDPR
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 on Article 30
Under Article 30 GDPR controllers and processors must maintain a record of each processing activity (Article 4(2) GDPR). This obligation represents the expression of several data processing principles. On the one hand, it achieves accountability, as it allows the controller to keep track of its processing and amend it where necessary. On the other hand, it increases the overall transparency of the operations and makes it easier for the data subject to respond to requests to exercise his rights. In concrete terms, as we shall see, the register is nothing more than an updated written account of the main elements of the processing.
(1) Record of Processing Activities
Article 30(1) GDPR provides a non-exhaustive list of the elements that constitute the record of processing activities.
First, the (a) 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. Rather, it must contain all the elements that make it possible to contact a particular person or, where appropriate, reach him or her for an inspection. Thus, in addition to the email address, also the physical address, telephone number and contact person.[1]
Then, under Article 30(1)(b), the controller must provide a description of the purposes of the processing. Interestingly, this provision does not demand a description of the legal basis for the processing operations. However, this gap should be filled by interpreting the text in line with the principles of fair processing. In particular, in the light of the principle of accountability, according to which the controller must be able to demonstrate compliance with the Regulation, the same 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".[2]
The record of processing activities shall also provide a description of the categories of data subjects and of the categories of personal data (Article 30(1)(c) GDPR). A category is a uniform group to which someone or something belongs. Examples of categories in this case are, "website visitors", "clinic patients", "employees". Same goes for the categories of personal data, "website clicks", "diagnosis", "holiday leave", "union affiliations". Scholars correctly note that each category of personal data should be tied to the category of data subject it belongs to. For example, the record should clearly show that the two categories "holiday leave" and "union affiliations" are processed with regard to the "employees" category.[3]
Under letter Article 30(1)(d), the controller should describe the categories of recipients to whom the personal data have been or will be disclosed. The literal wording of the provision suggests that, in this case, only the categories of addressees have to be indicated: "suppliers", "accountants", "marketing consultants", "legal advisors". Such vagueness, however, does not seem advisable. Other provisions of the GDPR require the controller to keep track of individual recipients. Examples include Article 15(1)(c), which requires disclosure of 'recipients or categories of recipients', or Article 19, which requires disclosure of specific recipients 'if the data subject requests it'. Accordingly, in view of the accountability function of the record of processing activities, it would make little sense to not specify the recipients.[4]
(e) 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; (f) the envisaged time limits for erasure of different categories of data and, where possible, a (g) general description of the technical and organisational security measures referred to in Article 32(1) GDPR.
(2) Categories of Processing Activities
The processor has the obligations to record (1) the name and contact details of the controller on behalf of which the processor is acting; (2) The categories of processing carried out on behalf of each controller; (3) 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; (4) A general description of the technical and organisational security measures referred to in Article 32(1) GDPR.
(3) Written Form
The records shall be in writing; this includes as well electronic formats. Chambers of Commerce as well as supervisory authorities in the EU provide for templates in PDF and Microsoft Word formats. In general, these records shall include processing activities, applications, responsible persons (“owners of data”) which is connected with the organisational structure of the respective company/organisation.
The obligation to keep the record up to date is not expressly regulated in the GDPR. However, if the record is not kept up to date, it is not possible to comply with the principles of transparency etc. and to provide the data protection authority with such records when requested.[5]
In addition, this leads to the question, whether the record needs to be electronically or has at least to provide for a timestamp, which is easier to trace in an electronic format. This means changes that have been made to the record need to be available to show ongoing compliance. Due to the principle of accountability (Article 5(2) GDPR), changes have to be transparent and traceable, e.g. who has been the controller/processor or data protection officer etc. at a certain point in time. This kind of documentation of changes should be kept for a certain amount of time.[6]
(4) Provision to Supervisory Authority
The supervisory authorities can assess controllers and processor as general control measure, but also in case of data breaches and complaints of data subjects. This is why a records of processing activities needs to be available at any time to provide the supervisory authority with it upon request.
(5) Exceptions
An enterprise or an organisation employing less than 250 persons is not obliged to implement the record of processing. However, the exception is not applicable if such 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
- ↑ Hartung, in Kühling & Buchner, DS-GVO BDSG, Art. 30, para 17 (C.H.Beck 2020, 3rd Ed.).
- ↑ Kotschy, in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 30 GDPR, p. 620 (Oxford University Press 2020).
- ↑ Hartung, in Kühling & Buchner, DS-GVO BDSG, Art. 30, para 17 (C.H.Beck 2020, 3rd Ed.) who also points out that special categories of data should be highlighted, also in order to ease the lawfulness check.
- ↑ In a broadly similar sense, Kotschy, in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 30 GDPR, p. 621 (Oxford University Press 2020).
- ↑ Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 30 GDPR, margin number 31 (Beck 2020, 3rd ed.) (accessed 19 August 2021).
- ↑ DSK, Datenschutzkonferenz, Hinweise zum Verzeichnis von Verarbeitungstätigkeiten, Art. 30 DS-GVO, February 2018, p. 3.