Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

Glossary. ROPA.

What is a record of processing activities (ROPA)?

A ROPA is the record of processing that GDPR and UK GDPR Article 30 require. It says why data is processed, so it has to agree with where the data really is.

By Dipal Panchal, co-founder and CEO · Updated November 8, 2026

Why data is processed, one activity at a time

A record of processing activities (ROPA) is the written record GDPR Article 30 requires of each processing activity: its purpose, the data and people involved, recipients, transfers, retention and security. Unlike a data inventory, which lists where data sits, a ROPA records why it is processed, so the two have to agree. A record written from interviews and never checked against the systems tends to describe the estate people remember.

This entry covers GDPR and UK GDPR, which share Article 30 in substance. India’s DPDP Act has no equivalent record.

One activity, field by field

The payroll activity of a UK company, Example Ltd, written against each point of Article 30(1).

One activity, field by field
Article 30(1)What it asks forPayroll, as recorded
(a)Controller, joint controller, representative and DPO contactsExample Ltd, London; DPO at dpo@example.com
(b)Purposes of the processingPaying staff, and meeting tax and pension duties
(c)Categories of data subjects and of personal dataEmployees and leavers; name, address, bank account, salary, tax code, National Insurance number, sickness absence
(d)Categories of recipientsHM Revenue and Customs, the pension provider, the payroll bureau (a processor)
(e)Transfers to third countries, with safeguards where Article 49(1) is relied onThe bureau’s support team in India, under the UK International Data Transfer Addendum
(f)Envisaged time limits for erasure, where possibleSix years after employment ends, per the retention schedule
(g)General description of Article 32(1) security measures, where possibleAccess limited to the payroll team; data encrypted at rest, with keys held by IT

The same activity, as the systems hold it

One generic scan of the estate, not IRIS output, compared with the record above. The Why column says whether the record already covers each location.

Records
SourceLocationDetected typeWhySensitivityDecision
Payroll system (SaaS)employees.bank_detailsBank account, salaryIn the record under (c)RestrictedMatches
HR databasehr.absence.reason_textHealth: sickness reasonsIn the record; the Article 9 condition isn’t written downRestrictedAdd the Article 9(2)(b) condition to the entry
Finance file sharefinance/payroll/2025_export.xlsxBank account, salary, National Insurance numberNot in the record: a monthly export the payroll team savesRestrictedAdd the share to the entry, or stop the exports
Data warehouseanalytics.headcount_costsSalary by employee IDNot in the record: workforce analytics, a second purposeConfidentialRecord a separate activity with its own purpose
Payroll bureau, IndiaThe bureau’s own systemEvery payroll categoryA recipient under (d); the bureau keeps its own Article 30(2) recordRestrictedOutside this scan; covered by the processor contract
Old payroll databaselegacy_payrollNoneStill named in the record; decommissioned in 2024 and gone from the estateNoneExcluded from the scan; remove it from the entry

What the two tables disagree on

Rows 3 and 4 are data the record doesn’t know about: an export saved every month, and a warehouse table serving a purpose nobody wrote down. Row 6 is the reverse, a system the record still names after it was switched off.

Copies don’t carry the purpose with them. The record names a purpose once, for the processing; the copies in the warehouse, analytics and CRM don’t say which purpose or consent covers them. Dipal Panchal, Sylox’s co-founder and CEO, has not seen a company record it against each copy.

Who has to keep one

Controllers keep a record under Article 30(1), and processors keep their own, shorter one under Article 30(2). Article 30(5) exempts organizations with fewer than 250 employees, unless the processing is likely to result in a risk to people, isn’t occasional, or includes special category or criminal offence data.

Payroll is never occasional, so even a small company keeps this entry. The record is in writing, electronic form included, and goes to the supervisory authority on request (Article 30(3) and (4)).

Check the record against a scan

Our rule: reconcile the record with a scan of the estate at least once a year, and whenever a system is added or retired. Two tests decide it: every system the record names holds the data it claims, and every system holding the data is named in the record.

Fix the record in both directions. Add what the scan found, and remove what it no longer finds, so the record a regulator asks for describes the estate as it is.

What a scan can’t fill in

A scan answers where. It can’t supply the purpose, the lawful basis, the recipients or the transfer safeguards, which come from the people who run the activity. Points (b), (d) and (e) stay with the business.

It also covers only the systems it reads. The bureau’s system in row 5 sits outside the scan, so the record leans on the processor contract and the bureau’s own record.

With IRIS

IRIS finds where each category of personal data sits in the sources you connect, so the Article 30 entry can be checked against the estate. Capabilities vary by edition.

Where each category of personal data sits: IRIS produces part of this, in the sources you connect.

Owner, purpose and retention beside each discovered table or file: IRIS produces part of this, as your stewards record them in the IRIS catalog.

The Article 30 entry itself: purposes, lawful basis, recipients and transfers: Not produced by IRIS.

Explore the data catalog

Reconcile one activity this quarter

Pick the activity with the most sensitive data, such as payroll or customer support, and list every system its entry names. Scan those systems and the shares and warehouses around them; the check passes when both tests above hold for that activity.

The record leans on a sensitive data inventory for the where. For the full comparison across activities, see the guide on Article 30 records against the data estate.

FAQ

Questions DPOs ask about the record

Protect your brand. Start with your data.

Bring one entry from your record. We’ll show you where IRIS finds that activity’s data across your sources.