Record of Processing Activities (RoPA)

The heart of a data protection management system

For what purposes does your company process personal data? With which software? When is the data deleted again? A RoPA gives you and the authorities the overview they need.

What is a RoPA?

Under Art. 30 GDPR, most companies are required to create a so-called record of processing activities (RoPA). Such a record can serve as the heart of an internal data protection management system (DPMS), as many other GDPR requirements (carrying out data protection impact assessments, documentation of data processing agreements, or information on transfers to third countries) can be seamlessly linked to it. In principle, a RoPA must be in writing, but the content and the level of detail required in a specific case have not been conclusively clarified in law. The minimum required information can be summarised as follows:

Register with entries, magnifying glass and person: record of processing activities
  • names and contact details of the controllers and of any data protection officer
  • the specific purposes of each processing activity
  • categories of data subjects
  • categories of personal data
  • the categories of recipients to whom data is disclosed
  • information on transfers of data to a third country or an international organisation
  • a general description of the technical and organisational measures
Process steps lead into a verified record, with person and shield

The Concept of a Processing Activity

In fact, the "processing activity" as such is not explicitly defined in the GDPR. This creates some uncertainty for companies about the level of detail at which processing activities must be documented. All that is clear: a breakdown that is too fine-grained may result in an unmanageable number of processing activities, while one that is too coarse does not allow a meaningful review of data protection compliance. In small companies it may be sufficient to group all HR-related activities under the generic term "HR administration". In larger companies, however, a finer breakdown (e.g. "HR administration", "HR development", "HR planning", etc.) is almost unavoidable.

Involving the Data Protection Officer

For the reasons above, the final decision on the appropriate level of detail when grouping processing activities in each individual case should always be made in close cooperation with the company's own data protection officer. In addition to acting as your external data protection officer, we at SDG also offer our full support separately, in the form of legal review and assessment, analysis of your technical and organisational measures, and templates adapted to your situation and company.

Contact us and we will help you bring this important core of your company's DPMS to life and make it GDPR-compliant.

Related Topics

Contract with signature and padlock between two companies: commissioned data processing

Commissioned Data Processing

Do your company's cooperation partners process personal data on your behalf? Then it is probably necessary to regulate this processing on the basis of a so-called contract for commissioned data processing (data processing agreement or DPA).

Risk grid with warning sign and shield: risk assessment

Impact Assessment

If the processing of personal data poses high risks for data subjects (e.g. discrimination in the event of a data breach), the GDPR requires a risk assessment, the identification of measures to reduce risk and the drawing up of an action plan.

Server racks with shield: secured systems

Information Security

The protection goals of information security are confidentiality, availability and integrity. To this end, we gladly carry out internal audits for you, assess your technical and organisational measures and check the security of your online presence by means of penetration tests.