For the complete documentation index, see llms.txt. This page is also available as Markdown.

Record of processing activities (ROPA)

Learn what a record of processing activities is.

Definition

The record of processing activities is the structured mapping of all personal data processing carried out within your organization. It is the starting point for any inspection by a data protection authority and a central tool for compliance governance.

The record is required by Article 30 of the GDPR. It gives substance to the principle of accountability, or demonstrated responsibility.

It lists precisely:

  • The stakeholders involved (controller, processor, joint controllers, representatives)

  • The categories of data collected

  • The purposes of the processing

  • The recipients and transfers

  • The retention periods

  • The security measures implemented


Reasons to keep a record

The record is mandatory (Article 30 of the GDPR), subject to the derogation described below. But beyond the regulatory obligation, it becomes a genuine management tool, enabling you to:

  • Document your processing activities to prove your compliance,

  • Identify and prioritize risks,

  • Optimize your retention periods,

  • Rationalize your processing and delete unnecessary data,

  • Prepare your GDPR audits and DPIAs.


Organizations concerned

All organizations subject to the GDPR are concerned. However, a derogation exists for organizations with fewer than 250 people (Article 30, paragraph 5).

SMEs must nevertheless include in their record all processing that is:

  • non-occasional (e.g. HR management, payroll, customers, suppliers),

  • likely to pose risks to individuals (CCTV, geolocation, etc.),

  • or involving sensitive data (health, criminal offences, political opinions).

In practice, most organizations are affected. The CNIL, the French supervisory authority, recommends keeping a record in all cases.


Two records to distinguish

Depending on your role, you must maintain:

  1. a data controller record,

  2. a data processor record.

The same organization may hold both: for example, a SaaS company managing its own HR data (controller) and its clients' data (processor).


The data controller record (in Dastra)

For each processing activity, the record must contain at minimum:

  1. The name and contact details of the controller or joint controller

  2. The purposes of the processing

  3. The categories of data subjects (customers, prospects, employees, etc.)

  4. The categories of data (identity, finances, location, etc.)

  5. The recipients (internal, processors, partners)

  6. Transfers outside the EEA, with the associated safeguards (SCCs, BCRs, etc.)

  7. The retention periods or criteria for determining them

  8. A general description of security measures

Stakeholders

  • Data controller

  • DPO or compliance contact

  • Representative if applicable

  • Joint controllers or partners

Purposes

All purposes linked to an activity (e.g. contract management, recruitment tracking, marketing, etc.).

  • Performance of a contract

  • Legal obligation

  • Legitimate interests

  • Public interest

  • Consent

  • Protection of vital interests

Data and data subjects

  • Type of data subjects (customers, employees, visitors…)

  • Categories of data collected

  • Retention periods or applicable rules

Recipients and transfers outside the EEA

  • Internal departments concerned

  • Processors, service providers or external partners

  • Joint controllers

  • International transfers: identification of countries and legal tools (SCCs, BCRs, adequacy decision…)

Security measures

  • Technical measures (encryption, pseudonymization, backups)

  • Organizational measures (access management, training, internal policy)


The data processor record

Processors must also maintain a record, more concise, listing:

  • The contact details of the processor, DPO and representative if applicable

  • The contact details of the data controller clients

  • The categories of processing carried out on behalf of each controller

  • Transfers outside the EEA and associated safeguards

  • The security measures applied

The AI systems register

The AI Act, in force since 2024, also requires organizations to document their artificial intelligence systems according to their risk level. In the Dastra AI systems register, you can:

  • Link each AI system to its processing activities,

  • Describe the purposes, models used and training data,

  • Assess risks and control measures,

  • Track AI Act and GDPR compliance in a single space.


Go further

Record of processing activitiesEstablish your record

Last updated

Was this helpful?