Free builder · About 10 to 20 minutes · Instant record

GDPR Record of Processing Activities Builder

Build an Article 30 record of processing activities, with every required field, from the auditors who review them.

Start from templates for common activities like payroll, marketing emails and customer support, then adjust them to fit. You describe categories of data, never actual personal data. Watch the record build as you type, with review notes on anything an assessor would question. It’s free, and there’s no obligation.

What you’ll get
1Every Article 30 fieldPurposes, data subjects, data categories, recipients, transfers, retention and security, for controllers and processors.
2Templates to start fromNine common activities pre-filled with typical answers you can edit.
3Review notes as you goFlags for missing retention periods, transfer safeguards, Article 9 conditions and possible high-risk processing.
4Ready to useCopy it, download it for Word or save it as a PDF.

Takes about 10 to 20 minutes

Build Your Record of Processing Activities

Add one entry for each purpose you use personal data for. Your work saves in this browser as you go, so you can come back to it.

Know what you process

A Self-Built Record vs. a GDPR Assessment

A record shows what you do with personal data. An assessment checks that the safeguards, notices and contracts behind it hold up.

Free, about 15 minutes

Record of processing builder
  • ✓Based on what you enter.
  • ✓Every Article 30 field, for controllers and processors.
  • ✓Review notes on common gaps.
  • ✓Not legal advice or an audit.
Independent assessment

GDPR assessment by Audit Peak
  • ✓Our assessors test your records against how you really process data.
  • ✓Covers lawful bases, notices, transfers and vendor contracts.
  • ✓Findings with practical recommendations.
  • ✓A report you can share with customers and partners.

Questions about records of processing

GDPR Record of Processing Activities FAQs

It’s a written inventory of how your organization uses personal data, required by Article 30 of the GDPR. For each activity, controllers record the purposes, the people and data involved, who receives it, transfers outside the EU, retention periods and security measures. Processors record similar details for each customer they process data for.

Usually, yes. Under current law, organizations with fewer than 250 employees are exempt only if their processing is occasional, unlikely to result in a risk, and excludes special category and criminal data. Payroll and HR are not occasional, so most small businesses still need a record.

It may. The EU has provisionally agreed to raise it to 1,000 employees, while still requiring records for activities likely to be high risk and for core activities that require a data protection officer. It isn’t law until Parliament and the Council formally adopt it, so the current rule still applies. The UK GDPR keeps its own Article 30 requirements.

No. You describe categories, such as “employee contact details” or “customer billing data.” Never enter real names, records or identifiers.

When someone asks what data you hold about them, your record tells you which systems and vendors to search. See our guide to handling GDPR data subject access requests.

Review it at least once a year and whenever you add a process, a vendor or a system. Regulators can ask to see it at any time, so an outdated record is a finding in itself. For the rest of your program, see our GDPR compliance checklist.

We store your contact details and a short summary of the record, such as activity names and counts, to send it to you and follow up. We don’t store the details you typed. We never sell your information, and you can opt in or out of occasional insights separately. See our privacy policy for details.

Let’s Talk About Your GDPR Program.

We Will Take Your Compliance To The Peak!

Name(Required)