Montro
A processor entry in the Article 30 record with its agreement, sub-processors and countries of processing

An Article 30 record that moves when your processors do

A RoPA (Record of Processing Activities) is the record GDPR Article 30 requires controllers and processors to keep: what personal data is processed, why, who receives it, where it is transferred and how long it is kept. UK GDPR asks for the same record. Article 28 adds a contract with every processor, and your authorisation before a processor brings in a sub-processor.

Montro keeps the processor side of that record current. It reads your sign-in, directory and finance systems to propose the suppliers that handle personal data, then raises changes, such as a new sub-processor or processing moved to another country, with their source. The supplier confirms, your team decides, and the record of processing is updated.

Framework

What GDPR asks of the record

Article 30 requires a written record of processing: what personal data is processed, why, by whom and where it goes, including every processor and sub-processor. Three parts of the regulation shape the record of processing and the suppliers behind it.

Record

Article 30: record of processing

Processors keep their own record too, and both are made available to the supervisory authority on request.

Processors

Article 28: processor guarantees

Processors must offer sufficient guarantees, and the contract sets out what they may do with the data.

Transfers

Chapter V: data leaving the EU and UK

Personal data sent abroad needs an adequacy decision or another recognised safeguard.

Discovery

Processor records that stay true

Montro keeps each processor’s entry linked to the processing it supports, so your team reviews one record instead of rebuilding it each year.

Shadow AI detection and risk classification

Processing linked to processors

Each activity in the record shows which processors handle the data and who owns the relationship.

Agreements kept with the entry

The processing agreement sits with the processor’s entry, so a missing or expired agreement is easy to spot.

Processors that go quiet

When a processor stops being used, Montro raises it. Your team re-tiers the entry, and its history stays.

Book a conversation

What you get

Questions the record can answer

Three answers your team won’t need to chase.

Accountability

A trail behind each change

Each update keeps its source, the supplier’s reply and your team’s call, so you can show how the record was kept.

Transfers

Where each processor’s data goes

Each entry records the countries where processing takes place, so a transfer question has a ready answer.

Sub-processors

The chain behind each processor

Sub-processors sit under the processor that uses them, so you can see who handles your data further down the line.

In numbers

What regulators are seeing

Breach notifications keep rising, and the EDPB expects controllers to see past their direct processors.

443

personal data breaches notified per day

Average across 16 European countries, January 2025 to January 2026.

22%

year-on-year rise in breach notifications

Up from an average of 363 a day the year before.

Oct 2024

EDPB opinion on processing chains

Controllers should have ready access to details of all sub-processors in the chain, not only their direct processors.

FAQs

What the record holds, how Montro keeps it current, and where your data sits.

It is the written record that GDPR Article 30 asks each controller to keep. For every processing activity, it sets out the purpose, the categories of people and data involved, who receives the data, any transfers outside the EU or UK, how long data is kept and, where possible, the security measures in place.

Every controller and processor. Organisations with fewer than 250 employees are exempt only if their processing is occasional, unlikely to put people’s rights at risk, and doesn’t include special category data or data about criminal convictions. Most firms process employee and customer data regularly, so in practice the exemption rarely applies.

GDPR does not set a schedule. The record should match your processing as it is, so it needs updating whenever that changes: a new processor or sub-processor, processing moved to another country, or a processor you no longer use. Montro raises these changes for your team to review.

Suppliers Montro finds arrive as candidates, not entries, and your team decides which ones belong in the record. Each change Montro raises is then closed in one of four ways: actioned, accepted with a reason, rejected, or marked as not a finding.

No. The legal basis is a judgement for your team and your DPO. Montro keeps it with the activity in the record, but does not set it.

Montro is hosted in Frankfurt, on AWS in the EU. Connections are read-only by default. The optional browser extension stays off unless you turn it on, and it collects metadata only.

Keep reading

Other registers your processors belong in

The suppliers in your Article 30 record often answer to other rules as well. Read how each one applies.

EU AI Act

AI systems that use personal data fall under both laws, so your AI inventory and your record should agree.

Read more

DORA

For financial entities, many processors are also ICT third-party providers in the register of information.

Read more

NIS2

Processors behind your network and information systems also belong in your NIS2 supply-chain record.

Read more

Third-party records are becoming decision logs. The firms that get this right will be the ones that can show who decided, on what evidence, and when.

  • Pen-test summary on request
  • Frankfurt hosting
  • Sample register
  • Expert Series guests
  • Cyber Ireland member

See it on your own suppliers

A read-only connection, about an hour to set up, and a named person who can say yes to a decision.

Priced to scope — never per seat, never per supplier. Upgrade only when the evidence earns it.

Montro AI discovery audit dashboard