Record of Processing Activities (GDPR Art. 30) Builder
Creates a record of processing activities (ROPA) table from one line per activity and flags the Art. 30(1) fields you left empty.
Use the tool
Why this tool exists
Article 30 of the GDPR asks many controllers to keep a written record of processing: who the controller is, what each activity is for, whose data and which data, who receives it, transfers abroad, how long it is kept and how it is secured.
Paste one activity per line and the tool builds the table and lists the missing fields with the article point they relate to. It does not know your processing, so the content is yours. Processors keep a separate record under Art. 30(2), and some small organisations are partly exempt.
How to use it
- Write one activity per line, fields separated by | in the order shown.
- Enter the controller and DPO details.
- Run the tool and read the review list.
- Copy the table into your document and keep it up to date.
Frequently asked questions
Who needs a record?
Controllers and processors, with a partial exemption for organisations under 250 staff that only process occasionally and not risky data. Check Art. 30(5).
Is legal basis required?
Not by Art. 30, but many authorities expect it. It is included as a useful column.
Does it store my data?
No. Everything stays in your browser.