Which Software Is Right for a Record of Processing Activities (RoPA)?
Three questions decide which software fits your record of processing activities (RoPA): how many companies in your group need their own record, whether the software detects your systems itself or only structures what people type in, and who maintains the record. A company with one legal entity, a handful of processing activities, and one responsible person can often work from a supervisory authority's template. Groups with their own privacy team or legal department usually run multi-entity privacy tools such as otris privacy or caralegal. Without an in-house data protection officer (DPO), a platform whose vendor provides the DPO tends to fit better, for example heyData, Kertos, Proliance 360, or secjur. Enterprise platforms such as OneTrust cover programs that span several jurisdictions.
Key takeaways
- Under Art. 30 GDPR, every controller keeps a record with seven mandatory items and every processor keeps a separate record. Both make it available to the supervisory authority on request.
- The exemption for organizations with fewer than 250 employees rarely applies. It falls away as soon as processing is more than occasional, and the German data protection conference (DSK) names regular processing of customer or employee data as an example.
- The GDPR has no group privilege. Every company that acts as a controller keeps its own record; software can hold all of them centrally, but the duty stays with each company.
- The planned extension of the exemption to companies with fewer than 750 employees (Omnibus IV) is not in force as of November 19, 2026. The European Parliament's plenary vote is scheduled for November 23, 2026.
Which vendors offer RoPA software?
Four models split the market. They differ less in whether a record gets produced than in how many companies they can map and who maintains the record. The vendors named are examples of each model, not a ranking.
| Model | Fits if | Examples |
|---|---|---|
| Multi-entity privacy tool | You run several companies and have your own privacy team or legal department | caralegal, otris privacy |
| Enterprise privacy platform | Your privacy program spans several jurisdictions and a privacy team operates the platform | OneTrust |
| Platform with experts or an external DPO | You have no DPO of your own, or the role sits on someone's desk as a side job | DataGuard, heyData, Kertos, Proliance 360, secjur |
| Template or spreadsheet | You have one legal entity, few processing activities, and one responsible person | Supervisory authority templates |
What each vendor states about the record on its own website, in alphabetical order:
| Vendor | Model | What the vendor states about the RoPA |
|---|---|---|
| caralegal | Privacy tool | Business units record processing activities in a guided workflow across all companies and locations, with an approval process and resubmission dates. Syncs with DPIAs, TOMs, and service providers; exports to PDF, Word, or Excel |
| DataGuard | Platform with experts | Data mapping and RoPA in a guided flow, migration from spreadsheets and CSV files, a risk dashboard, and reports |
| heyData | Platform with external DPO | Structured recording under Art. 30 GDPR with templates and exportable documentation, labeled as an export for the authority |
| Kertos | Platform with certified experts and external DPO | RoPA, DPIA, TOMs, and transfer impact assessments on one platform, detection of systems and vendors, multi-entity management for several companies |
| OneTrust | Enterprise privacy platform | Continuous detection of data assets through identity and access management, cloud providers, and CMDBs; mapping of data flows |
| otris privacy | Privacy tool for groups | Companies, locations, roles, and responsibilities in a multi-tenant platform, decentralized updates through a processing portal, custom reports and cockpits, SaaS or on-premises operation |
| Proliance 360 | Platform with external DPO | Industry-specific templates under Art. 30 GDPR, automatic completeness checks, and multi-entity management in one view |
| secjur | Platform with expert service and external DPO | A dedicated expert builds the data protection management system, and secjur states it takes over around 80 percent of privacy tasks. The RoPA, TOMs, and DPAs sit in its "Digital Compliance Office" |
How we compared
Kertos is a vendor in this market and publishes this comparison. Every statement about another vendor therefore comes from that vendor's own public website, checked on November 19, 2026. The table reflects what a vendor describes; a feature missing from its site does not mean the feature does not exist. We left out review portals, prices from sales calls, and third-party claims. The order is alphabetical. The German vendor sites were read in German and are paraphrased here.
What does Art. 30 GDPR require from the record?
Art. 30 sets out the content, form, and disclosure of the record. You can read the text in Regulation (EU) 2016/679, checked on November 19, 2026.
| Rule | Provision | What it means |
|---|---|---|
| Controller's record | Art. 30(1) | All processing activities under its responsibility, each with names and contact details (including any joint controller and the DPO), purposes, categories of data subjects and personal data, categories of recipients, and transfers to third countries; where possible, erasure time limits and a general description of the TOMs |
| Processor's record | Art. 30(2) | A separate record of the processing carried out on behalf of each controller, with every controller, the categories of processing, third-country transfers, and, where possible, the TOMs |
| Form | Art. 30(3) | In writing, including in electronic form |
| Disclosure to the authority | Art. 30(4), Recital 82 | On request of the supervisory authority, so that it can monitor processing operations on the basis of the record |
| Exemption | Art. 30(5) | Applies below 250 employees, but only if the processing is unlikely to result in a risk, is occasional, and includes no special categories under Art. 9 or criminal offense data under Art. 10 |
The exemption is narrower than its threshold suggests. According to short paper no. 1 by the German data protection conference (in German), the duty applies as soon as one of the three conditions is met. A company that runs payroll or keeps a customer database processes more than occasionally and needs a record for those activities, even with ten employees.
The Commission proposal COM(2025) 501 would extend the exemption to companies with fewer than 750 employees and remove it only for processing likely to result in a high risk. Council and Parliament agreed on a text on June 26, 2026, and the Legislative Observatory lists November 23, 2026, as the indicative plenary date. Until publication in the Official Journal, the 250 threshold applies. For groups, the change matters less when individual companies process high-risk or special-category data. The record is one obligation among several; our data privacy software comparison covers the wider picture.
How do groups and multi-entity companies keep the RoPA?
Company by company. The GDPR defines a group of undertakings in Art. 4(19), but it treats every company as its own controller, and Art. 30(1) addresses "each controller". Recital 48 only recognizes that companies in a group may have a legitimate interest in transferring data for internal administrative purposes. That helps with the legal basis and exempts no one from keeping a record.
| Setup | Legal basis | Consequence for the record |
|---|---|---|
| Each company processes for its own purposes | Art. 30(1) | One record per company |
| A central IT or HR company processes for its sister companies | Art. 28, Art. 30(2) | The service company also keeps a processor's record, with a contract for each controller |
| Two companies jointly determine purposes and means | Art. 26, Art. 30(1)(a) | Each lists the activity in its own record and names the joint controller there; their arrangement sets out who fulfills which obligation |
| The group appoints a single DPO | Art. 37(2) | Allowed if the DPO is easily accessible from each establishment. The records stay separate |
For software, this means it has to assign processing activities to a company, reuse shared master data such as systems and vendors, and produce a record per company that the authority can request. A group-wide report for management on top of that is an extra that not every tool provides. Our page on ISMS and privacy management tools for groups covers the wider setup.
What changes for cross-border controllers with a lead supervisory authority?
It changes who supervises, not who keeps the record. Under Art. 56(1) GDPR, the supervisory authority of the controller's main or single establishment leads on cross-border processing. According to the European Data Protection Board's Guidelines 8/2022, in a group headquartered in the EEA the establishment of the controlling undertaking counts as the main establishment, unless another establishment takes the decisions on the processing. Joint controllers cannot designate a common main establishment.
The Board names effective records of processing as a help in identifying the lead authority. So record, for each processing activity, which company decides on purposes and means. That entry answers the competence question if it is ever disputed.
How do you recognize good RoPA software?
Six criteria separate the vendors. Ask the test question in the demo rather than relying on words like "automated" or "multi-tenant".
| Criterion | Test question for the demo | Why it matters |
|---|---|---|
| Templates and structure | Does the template cover every item in Art. 30(1) and keep the controller's record separate from the processor's record? | The two records require different items |
| Links | Do TOMs, vendors with DPAs, DPIAs, and data subject requests attach to the same processing activity? | The recipients an Art. 15 access response must name sit in the record |
| Staying current | How does the record learn about a new tool: through an integration, detection, a review reminder, or not at all? | The authority asks for today's state, not the state of the last survey |
| Several companies | Can you assign processing activities to a company and report and export per company? | Every controller keeps its own record |
| Export for the authority | Does the software produce a readable record per controller, for example as PDF, Word, or Excel? | Disclosure on request under Art. 30(4) |
| Who maintains it | Who assesses purpose and legal basis: your team, the vendor's DPO, or a third party? | Software finds systems; the legal assessment stays expert work |
The link to data subject requests is where a maintained record pays off day to day. Our DSAR software comparison shows how vendors handle requests, and our article on data discovery for GDPR explains why the record is only as good as the inventory behind it.
When is a template or spreadsheet enough for the RoPA?
When you have one legal entity, few processing activities, rarely add tools, and one person who maintains the record. A spreadsheet is then the appropriate tool, not a compromise. Art. 30(3) only requires written form, which can be electronic. Supervisory authorities publish templates, for example the simplified register template of the French authority CNIL (in French).
The spreadsheet reaches its limits once a second company joins, teams regularly bring in new tools, or you have to answer data subject requests from the record. At that point you lack links to TOMs, vendors, and requests, and you have no version history and no export per company. Any one of these triggers is a good moment to switch; before that, the effort of introducing software is rarely justified.
When is Kertos a fit, and when is it not?
Kertos is a European compliance platform with certified experts in-house. What that means for the record:
- RoPA: You create the RoPA, DPIAs, TOMs, and transfer impact assessments on one platform, with IT integration and automated documentation.
- Data discovery: Kertos detects the systems and vendors in your IT and the categories of personal data each system can hold.
- Links: Processing activities connect to TOMs, DPIAs, and data subject requests. GDPR evidence comes from more than 300 integrations.
- Several companies: Multi-entity management lets you run several legal entities from one account. Each company has its own master data and its own roles, such as the DPO; you can assign processing activities, systems, and vendors to one company or the whole group and filter by them.
- External DPO: as a mandate, with certified experts in-house, working in the same system where the record lives.
- Headquarters and hosting: Munich. According to our sub-processor list, hosting runs on Amazon Web Services EMEA Sàrl in Luxembourg, an EU company of the US-based Amazon group.
More than 500,000 data subject requests have been resolved through the platform. On G2, Kertos holds 4.8 out of 5 stars from 65 reviews (as of November 19, 2026). See how your systems and companies would look in the record on our RoPA, DPIA, and TOMs page, or book a demo.
Kertos is not a fit if your group needs separate tenants with data isolation, its own administrators per company, or a consolidated dashboard across all companies. Multi-entity privacy tools and enterprise platforms are built for that; otris privacy also offers on-premises operation. Kertos is not a fit either if a template covers your size, or if your fully staffed privacy team only wants a documentation tool without support. If what you mainly need is a named person, our comparison of external DPO provider models is the better starting point.
Frequently asked questions
Who has to keep a record of processing activities?
Every controller and every processor, and where applicable their representative in the EU (Art. 30(1) and (2) GDPR). Organizations with fewer than 250 employees are exempt only if their processing is unlikely to result in a risk, is occasional, and involves no special categories or criminal offense data. A company that regularly processes customer or employee data does not meet that condition and needs a record for those activities.
Does every subsidiary need its own RoPA?
Yes, as far as it acts as a controller. The GDPR has no group privilege, and Art. 30(1) obliges each controller individually. The records can sit in shared software and share master data such as systems and vendors. A subsidiary that provides services to other group companies also keeps a processor's record.
How often does the RoPA have to be updated?
Art. 30 GDPR sets no interval. Because the supervisory authority can request the record at any time, it has to show the current state of your processing. The French authority CNIL says the register must be updated regularly as processing changes functionally and technically. In practice, that means updating it with every new tool, new vendor, new purpose, and changed retention period.
What is the difference between a RoPA and a DPIA?
The record under Art. 30 GDPR documents all processing activities. A data protection impact assessment under Art. 35 assesses only processing likely to result in a high risk to the rights and freedoms of data subjects, and it does so before the processing starts. The record is usually the starting point for checking which activities need a DPIA.
As of November 19, 2026. All statements about other vendors come from their own public websites and were checked on that date. Check the status of the Omnibus IV procedure again before you decide.
Discover our Resources
Find useful whitepapers, videos, and practical tools to help you efficiently achieve your compliance goals.


