What is a Record of Processing Activities (ROPA)?
Direct answer
A Record of Processing Activities (ROPA) is the internal register required by GDPR Article 30 that documents how your organisation processes personal data: purpose, data categories, recipients, transfers outside the EU or EEA, retention periods, and security measures. Controllers and processors must keep one in writing and produce it to a supervisory authority on request.
It is the source of truth that a DPIA, a DSAR, a breach assessment, and a transfer assessment all read from.
What exactly must a ROPA contain?
Article 30(1) lists the minimum content of a controller’s record:
- the name and contact details of the controller and, where applicable, the joint controller, the controller’s representative and the data protection officer;
- the purposes of the processing;
- a description of the categories of data subjects and of the categories of personal data;
- the categories of recipients, including recipients in third countries or international organisations;
- where applicable, transfers to a third country or international organisation, identified by name, and for transfers under the second subparagraph of Article 49(1), the documentation of suitable safeguards;
- where possible, the envisaged time limits for erasure of each category of data;
- where possible, a general description of the technical and organisational security measures of Article 32(1).
A processor keeps a shorter record (Article 30(2)): its own details and those of each controller it acts for, the categories of processing carried out for each controller, transfers and their safeguards, and a general description of its security measures. Both records must be in writing, which includes electronic form (Article 30(3)).
Does the under-250 exemption apply to you?
Probably not in full. Article 30(5) exempts an enterprise or 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, is not occasional, or includes special categories of data (Article 9(1)) or data on criminal convictions and offences (Article 10).
The Article 29 Working Party, in a position paper endorsed by the EDPB, reads those three conditions as alternatives: any one of them is enough to trigger the obligation. The risk does not have to be high. Processing is occasional only if it is not carried out regularly and falls outside the normal course of business, so a small company that regularly processes employee data must record that processing.
The exemption is not all or nothing either. A small organisation only has to record the types of processing caught by Article 30(5), and can leave out activities that are genuinely occasional, unlikely to result in a risk and free of special-category or criminal data.
How does the Swiss FADP record of processing differ?
The revised Swiss FADP, in force since 1 September 2023, also requires controllers and processors to keep a record of their processing activities (Article 12). The exemption is narrower in wording: under Article 24 of the Data Protection Ordinance, companies with fewer than 250 employees are exempt unless they process sensitive data on a large scale or carry out high-risk profiling.
Private companies do not file their register with the FDPIC. Since the revised FADP took effect, only federal bodies report their processing activities to the FDPIC, which publishes them in its public register. A company subject to both laws can keep one register that meets both, with the legal basis for each law recorded on each activity. See the Swiss FADP guide and does the GDPR apply to Swiss companies?
What are the common mistakes when building a ROPA?
- Listing systems instead of activities. The record is organised by processing activity and purpose, such as payroll or customer support. The FDPIC makes the same point for its federal register: entries describe activities, not a list of systems. Systems and vendors belong in the record as the means and recipients of each activity.
- Forgetting the processor record. A company that processes personal data on behalf of its customers needs a processor record for that work, in addition to the controller record for its own activities.
- Leaving the optional-sounding fields empty. Retention periods and security measures are required where possible, and they are exactly what a DPIA, a breach assessment or a transfer impact assessment needs.
- Writing it once. A record that no longer matches reality fails its purpose. The Working Party describes the record as a means to analyse the implications of any processing, existing or planned, which only works if new activities are added before they start.
How Acuna GRC handles it
In Data Privacy in Acuna GRC, each processing activity is a record linked to the assets and third parties it uses, and business owners can complete their own activity through a questionnaire link, so the people closest to the data keep the register current.
- Module
Data Privacy
Processing activities, data inventory and flows, DPIAs, DPAs, TIAs, data subject requests and breaches, with a public privacy portal.
- Solution
GDPR
Meet GDPR accountability: keep the Art. 30 record current, assess high-risk processing under Art. 35 and prove each request and breach met its deadline.
- Service
DPO as a service
An external DPO from Swiss experts: your record of processing, DPIAs, data subject requests and breaches, run in Acuna GRC for the GDPR and the Swiss FADP.
Sources
- Regulation (EU) 2016/679 (GDPR), Article 30
- Article 29 Working Party, position paper on the derogations from the obligation to maintain records of processing activities (Article 30(5)), endorsed by the EDPB
- FDPIC, DataReg register of processing activities of federal bodies
This page explains the rules in general terms and is not legal advice.
Frequently asked
Is there a mandatory template for a ROPA?
No. The GDPR prescribes the content, not the format, and the record can be electronic. The Article 29 Working Party encouraged supervisory authorities to offer simplified models to help SMEs keep the processing that the exemption does not cover.
Do we have to send our ROPA to the supervisory authority?
No. Under Article 30(4) you make it available to the supervisory authority on request. Under the Swiss FADP, private companies no longer report their register to the FDPIC; only federal bodies do.
Who should own the ROPA?
The controller is accountable for it. In practice, the DPO or privacy lead runs the register, and the business owner of each activity provides and confirms the facts, because they know the purpose, data and recipients best.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

