Article 30 GDPR: Difference between revisions
Line 223: | Line 223: | ||
==Commentary on Article 30== | ==Commentary on Article 30== | ||
Article 30 GDPR | Under Article 30 GDPR controllers and processors have to maintain a record of each processing activity. set forth in [[Article 4 GDPR|Article 4(2) GDPR]]. Only when a record of processing activities exists, principles such as transparency, purpose, data minimization, accuracy, storage limitation and accountability etc., can be realized.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 30 GDPR, margin number 11 (Beck 2020, 3rd ed.) (accessed 19 August 2021).</ref> It serves as a self-control mechanism to assess what kind of processing activities are at stake. Moreover, Data Protection Impact Assessments (“DPIA”) are included in these records to legitimize the respective processing activity, in particular if there is a high risk for personal data. Therefore, technical and organizational measures also have to be mentioned in the record. | ||
Another reason for maintaining records has to do with accountability. When either a data subjects enforces its rights ([[Article 12 GDPR]]) or a data protection authority requests information about processing ([[Article 13 GDPR|Articles 13]] and [[Article 14 GDPR|14 GDPR]]), all activities can easily be explained. A record of data processing activities is useful and eases the process of giving a data subject the information that have been asked for. The record can also help in drafting and keeping the privacy policy up to date. The record of processing activities also supports the controller in assessing its own processing as well as the one carried out by possible external processors. | Another reason for maintaining records has to do with accountability.<ref>Cf. ''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 30 GDPR, margin number 12 (Beck 2020, 3rd ed.) (accessed 19 August 2021).</ref> When either a data subjects enforces its rights ([[Article 12 GDPR]]) or a data protection authority requests information about processing ([[Article 13 GDPR|Articles 13]] and [[Article 14 GDPR|14 GDPR]]), all activities can easily be explained. A record of data processing activities is useful and eases the process of giving a data subject the information that have been asked for. The record can also help in drafting and keeping the privacy policy up to date. The record of processing activities also supports the controller in assessing its own processing as well as the one carried out by possible external processors. | ||
=== (1) Record of Processing Activities === | === (1) Record of Processing Activities === |
Revision as of 07:25, 20 February 2022
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 have to maintain a record of each processing activity. set forth in Article 4(2) GDPR. Only when a record of processing activities exists, principles such as transparency, purpose, data minimization, accuracy, storage limitation and accountability etc., can be realized.[1] It serves as a self-control mechanism to assess what kind of processing activities are at stake. Moreover, Data Protection Impact Assessments (“DPIA”) are included in these records to legitimize the respective processing activity, in particular if there is a high risk for personal data. Therefore, technical and organizational measures also have to be mentioned in the record.
Another reason for maintaining records has to do with accountability.[2] When either a data subjects enforces its rights (Article 12 GDPR) or a data protection authority requests information about processing (Articles 13 and 14 GDPR), all activities can easily be explained. A record of data processing activities is useful and eases the process of giving a data subject the information that have been asked for. The record can also help in drafting and keeping the privacy policy up to date. The record of processing activities also supports the controller in assessing its own processing as well as the one carried out by possible external processors.
(1) Record of Processing Activities
The obligation to record processing activities lays with the controller and not with the data protection officer.
Activities which have to be included in the non-exhaustive list are the following: (1) The name and contact details of the controller and related parties; (2) The purposes of the processing; (3) A description of the categories of data subjects and of the categories of personal data; (4) The categories of recipients; (5) 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; (6) A data deletion concept; (7) A 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.[3]
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.[4]
(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, Article 30 GDPR, margin number 11 (Beck 2020, 3rd ed.) (accessed 19 August 2021).
- ↑ Cf. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 30 GDPR, margin number 12 (Beck 2020, 3rd ed.) (accessed 19 August 2021).
- ↑ 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.