Keep your records of processing always audit-ready

The record of processing is a report drawn from your processing activities, not a document you rebuild before an inspection. Correct an activity and the record says so immediately, with red markers on whatever is still missing.

Unlimited users  •  Free onboarding and support  •  No commitment

Illustration of a person working on three small activity cards, with lines flowing from them into a large spreadsheet-like table panel that fills itself in
+400 companies use .legal
Region Sjælland
Aarhus Universitet
aj_vaccines_logo
Realdania
Right People
IO Gates
PLO
Finans Danmark
geia-food
Evida
Klasselotteriet
NRGI1
BLUE WATER SHIPPING
Karnov
Ingvard Christensen
VP Securities
AH Industries
Lægeforeningen
InMobile
AK Nygart
DEIF
DMJX
Axel logo
qUINT Logo
KAUFMANN (1)
SMILfonden-logo
kurhotel_skodsborg
nemlig.com
Molecule Consultancy
Novicell
The record of processing in .legal, drawn for one group company with the company selector open, read-only and laid out like a spreadsheet across the Article 30 columns: purposes, categories of personal data, categories of data subjects, deletion periods and security measures

Always audit-ready Meridian's record is ready on a Tuesday, not after a fortnight of tidying

Sofie Bruhn is group DPO at Meridian Nordic, three legal entities and around 1,200 vendors between them. Her record of processing used to be true on the day it was written and slightly less true every week after that, and she found out how much less every time a customer sent an audit questionnaire. Now the record is a report drawn from the processing activities themselves. She edits the activity, the record says so immediately, and the red markers tell her where it has gone thin before anyone else asks.

  • The record is drawn per legal entity, with that company's own details on the export.
  • A correction on a processing activity is in the record straight away, with no save step.
  • Red markers point at exactly the fields that are missing, per activity and in total.
  • Every action on an activity is in a change log, so three people can work in it safely.

  • Ready when asked

    The record is a live view over your processing activities, so there is nothing to assemble the week an auditor writes.

  • One record per entity

    The record is drawn per legal entity, because that is the unit the law asks for, and the company's own details follow the export.

  • Red markers, not a pass mark

    Every activity shows how far it has got and marks exactly which fields are missing. Nothing is blocked, and nothing is hidden either.

  • Every change on record

    Every single action on a processing activity is written to a full change log, so several colleagues can work in the same record safely.

Illustration of a record panel whose lower rows have faded to empty outlines, with ghost pages drifting behind it and a solid block standing beside a dashed empty outline where its replacement should be

Always audit-ready A record is only true until something changes

Documentation goes out of date quietly. The activity was described correctly, and then payroll moved to a new provider and nobody thought to mention it to the DPO.

  • The facts sit with system owners and the business, so every update starts as a chase.
  • Nothing in a spreadsheet tells you when it stopped being accurate.
  • Rebuilding the record before an inspection is the same work twice, done badly under time pressure.
A processing activity open in its stepped flow in .legal, on the categories of personal data step, where each category is ticked on a card — the activity is what you edit, not the record

Always audit-ready The record is a report, not a document you maintain

This is the part people have to see once before it clicks. The record in .legal is a read-only view, laid out like a spreadsheet, drawn from your processing activities.

  • You edit the processing activity. The record has nothing to edit, so it cannot drift from the source.
  • There is no save button, so the change takes effect wherever it is used immediately.
  • It is drawn per legal entity, because that is the unit the regulation asks for, and the company's details travel out with the export.
Illustration of two record panels side by side, the taller one carrying extra rows picked out and bracketed, linked by a thin arc, with a filter chip resting in front of it

Always audit-ready Two records, and the second one answers the follow-up question

Article 30 sets a minimum, and a real audit conversation rarely stops there. So the same view is drawn two ways.

  • One holds the Article 30 requirements one to one, for when somebody asks for the statutory record.
  • The other adds further relevant information, the legal basis and the systems in use for example.
  • Either can be filtered down and drawn for a subset, one department rather than the whole company.
The transfer step of a processing activity in .legal, with the step heading and the disclosures counter marked in red because that part of the record is not filled in yet

Always audit-ready Red markers instead of a green light

The platform does not tell you that you are compliant. It tells you how much of the record is filled in, and where the holes are.

  • Each activity carries a progress bar towards the record requirements, with red markers on the missing fields.
  • The dashboard carries the same figure for the whole organisation. A demo environment stood at 84% documented, which is an illustration of what the platform shows, not a benchmark.
  • Nothing is blocked while an activity is incomplete. Being fully documented at all times is not realistic, and we would rather show status than pretend.
Illustration of a record panel, a server carrying a document and a company building linked in a triangle, with a confirmation card holding a toggle and a tick in the middle

Always audit-ready Correct it once, and the record follows

Processing activity, system and vendor are mapped to each other, so the same fact does not have to be maintained in three places.

  • A data processing agreement is uploaded once on the system and is then in every activity that system is attached to.
  • Add a sub-processor to a vendor and the platform offers to apply it everywhere that vendor is used, then fills it in once you accept. A prompt, never a silent update.
  • An intra-group sharing is registered once and appears on both records, the controller's Article 30(1) and the processing company's Article 30(2).
A recurring task in .legal for validating the record of processing, with its subtask checklist at nought per cent, somewhere to attach documentation, and a comment and history log beneath

Always audit-ready What keeps it current when nobody is looking

Somebody still has to notice that a system changed. What the platform does is make sure the noticing is planned, owned and logged.

  • The recurring reviews sit in the annual wheel as tasks with named owners, deadlines and notifications.
  • When .legal invalidates a legal basis centrally, the affected places go red, the completion percentage falls, and you get the list. We do not change your documentation on your behalf.
  • Every single action on a processing activity is written to a full change log, which is what makes several colleagues in the same record safe rather than risky.
.legal in practice

Features for an audit-ready record

The record as a report view

A read-only, spreadsheet-like view drawn from your processing activities. You edit the activity, never the record, so the record and its source can never disagree.

Article 30 one to one, or fuller

One record holds the Article 30 requirements one to one. The other adds further relevant information, the legal basis and the systems in use for example, for the questions that come after the statutory minimum.

Progress bar with red markers

Each activity computes how far it is towards meeting the record requirements and marks the fields that are missing, so you chase the gaps instead of re-reading everything.

Full change log

Every single action on a processing activity is recorded. When someone asks who changed the retention period and when, the answer is in the platform, not in an email thread.

Excel export, per entity or per department

Export the record as Excel with the selected company's details on it, or filter it down to a subset first, one department for instance.

Annual wheel tasks and notifications

The recurring review work becomes planned tasks with named owners, and when .legal invalidates a legal basis centrally you get a notification listing every affected place.

Always audit-ready Frameworks this covers

One record, kept to the requirement it exists for.

  • icon-framework-GDPR

    GDPR

    Article 30 is the obligation this page is about: a record for each legal entity, in the controller role and the processor role, kept current rather than reconstructed.

    Learn about GDPR
.legal compliance platform

Keep your records audit-ready with...

Do you need your records of processing to stay audit-ready? We recommend the following module for that task.

GDPR / Data Protection

Document GDPR, keep Article 30 records current and stay audit-ready, with the processing activities, assets, vendors and annual wheel that sit around the record.

Explore GDPR

Our Customers

+400

companies

+10.000

users

+79.000

contracts

+14.000

processing activities

Bech Bruun

Bech-Bruun

Mikkel Friis Rossa (Partner)

.legal's team has consistently demonstrated a commitment to innovation while being responsive to the needs of our mutual clients.

Rasmus-boutrup-fenerum

Fenerum

Rasmus Boutrup (Financial Controller)

Case Study
With .legal, we've gained a simpler and more manageable solution that better suits our needs
Michael Berner 1

Lægeforeningen

Michael Berner (Lawyer)

.legal has been the right choice for us. .legal are professional and welcoming with skilled employees.
Nanna Rodian Christensen

Molecule Consultancy

Nanna Rodian Christensen (HR & Operational Manager)

Case Study
Firstly, it means that not all the work is in one place (me), and secondly, that the understanding of GDPR is implemented throughout the organisation.
ulrikdueholmbeckmann

Plum Safety

Ulrik Dueholm Beckmann (QC, CM og ESG Lead)

Case Study
From .legal, we experience an incredibly high degree of flexibility and willingness to adapt features to our local needs.
Bech Bruun

Bech-Bruun

Mikkel Friis Rossa (Partner)

.legal's team has consistently demonstrated a commitment to innovation while being responsive to the needs of our mutual clients.

Rasmus-boutrup-fenerum

Fenerum

Rasmus Boutrup (Financial Controller)

Case Study
With .legal, we've gained a simpler and more manageable solution that better suits our needs
Michael Berner 1

Lægeforeningen

Michael Berner (Lawyer)

.legal has been the right choice for us. .legal are professional and welcoming with skilled employees.
Nanna Rodian Christensen

Molecule Consultancy

Nanna Rodian Christensen (HR & Operational Manager)

Case Study
Firstly, it means that not all the work is in one place (me), and secondly, that the understanding of GDPR is implemented throughout the organisation.
ulrikdueholmbeckmann

Plum Safety

Ulrik Dueholm Beckmann (QC, CM og ESG Lead)

Case Study
From .legal, we experience an incredibly high degree of flexibility and willingness to adapt features to our local needs.
julie-oxenvad-novicell

Novicell

Julie Oxenvad (Legal Consultant)

Case Study
We are satisfied with the switch to .legal – it has strengthened our compliance work, made processes easier to manage and more transparent, and improved cross-team collaboration
Tinna Schultz

Min By Media

Tinna Schultz (HR Manager)

Case Study
It just works! It is so easy and user-friendly, and the overview of processing activities is brilliant.
ansat_Kaspar_Rochholz_005

DMJX

Kaspar Rochholz (GDPR Coordinator)

Case Study
.legal has really understood what it means to create a user-friendly and efficient solution. Privacy is an attractive product compared to price and functionality.
Profile-picture1

Axel Kaufmann ApS

Julie Lundkvist Andreasen (Lawyer and Head of Costumer Service)

Case Study
.legal continuously update the platform to ensure their customers always remain compliant. In our view, any other choice would be a downgrade.

NRGi

Mette Mühlendorph (Compliance Specialist)

Case Study
The implementation of .legal has made a difference in the way we handle compliance. The system has created structure and overview, which has had concrete benefits.
julie-oxenvad-novicell

Novicell

Julie Oxenvad (Legal Consultant)

Case Study
We are satisfied with the switch to .legal – it has strengthened our compliance work, made processes easier to manage and more transparent, and improved cross-team collaboration
Tinna Schultz

Min By Media

Tinna Schultz (HR Manager)

Case Study
It just works! It is so easy and user-friendly, and the overview of processing activities is brilliant.
ansat_Kaspar_Rochholz_005

DMJX

Kaspar Rochholz (GDPR Coordinator)

Case Study
.legal has really understood what it means to create a user-friendly and efficient solution. Privacy is an attractive product compared to price and functionality.
Profile-picture1

Axel Kaufmann ApS

Julie Lundkvist Andreasen (Lawyer and Head of Costumer Service)

Case Study
.legal continuously update the platform to ensure their customers always remain compliant. In our view, any other choice would be a downgrade.

NRGi

Mette Mühlendorph (Compliance Specialist)

Case Study
The implementation of .legal has made a difference in the way we handle compliance. The system has created structure and overview, which has had concrete benefits.
Use cases

Find the job you need done

Every use case is a real piece of compliance work, told the way it actually runs in the platform. Filter by who you are, what you work with, and which frameworks you answer to.

Book demo

6 use cases

Frequently Asked Questions about records of processing

What is the record of processing in .legal, exactly?

A reporting view, laid out like a spreadsheet and read-only. It is drawn from your processing activities and always for one legal entity at a time, because that is the unit the regulation asks for. All editing happens on the processing activity itself, and there is no save button, so a correction is in the record as soon as you make it.

Which of the two records do we get?

Two are available. One holds the Article 30 requirements one to one, which is what you hand over when someone asks for the statutory record. The other adds further relevant information, for example the legal basis and the systems in use, which is usually what a customer or an auditor asks about next.

How do we know what is still missing?

Every processing activity carries a progress bar towards the record requirements, with red markers on exactly the fields that are not filled in, and the dashboard carries the same figure for the whole organisation. In a demo environment it stood at 84% documented, which is an illustration of what the platform shows rather than a benchmark. Nothing is blocked while it is incomplete, because being 100% documented at all times is not realistic and we would rather show status than pretend.

Can we hand the record to an auditor, a customer or the authority?

Yes. The record exports as Excel, and the details of the company you selected travel out with the file. You can also filter it first and draw it for a subset, one department for instance. The rule behind it is that anything you could be asked to show a third party can be exported in the format that suits its shape, and the record's shape is a list, so the record goes out as Excel.

Who the Danish Data Protection Agency is

Can we see who changed what, and when?

Yes. Every single action on a processing activity is written to a full change log. That is what makes it safe for several colleagues to work in the same record, and it is the answer when an auditor asks how a field came to say what it says.

What happens when a legal basis stops being valid?

The Article 6 and Article 9 bases are master data .legal maintains centrally, so when one is invalidated we do it once for every customer. Every place it was used is marked red, the affected activity's completion percentage falls, and you get a notification with the list of affected places. We will not go in and change your documentation on your behalf, and that is deliberate.

What happens when one of our data processors adds a sub-processor?

You register the sub-processor on the vendor, and the platform offers to apply it everywhere that vendor is already used, then fills those places in once you accept. It is a prompt you approve, never a silent update, which is the way this reader usually wants it.

Run due diligence and supervision of your processors

We are a group with several entities. Is that one record or several?

Several, one per legal entity, and reporting on top of them can be consolidated across the group or filtered to a single company. An intra-group sharing is registered once and appears on both sides, on the controller's Article 30(1) record and on the processing company's Article 30(2) record.

Does the record keep itself current?

No, and we would rather say that plainly. Somebody still has to notice that a system changed. What the platform does is make sure the work is planned, owned and visible: the recurring reviews sit in the annual wheel as tasks with named owners, changes land in the record with no save step, and the red markers show where the record has quietly gone thin.

Can we do a DPIA in the platform?

You can, and we do not push our own template at you. A DPIA has to fit the specific case, so if you already have a document that works, keep using it. That is our own recommendation, not a limitation we are apologising for.

What a data protection impact assessment involves

Still unsure?

Ask Johannes directly, he runs most demos personally

Book him here
+400 companies use .legal
Region Sjælland
Aarhus Universitet
aj_vaccines_logo
Realdania
Right People
IO Gates
PLO
Finans Danmark
geia-food
Evida
Klasselotteriet
NRGI1
BLUE WATER SHIPPING
Karnov
Ingvard Christensen
VP Securities
AH Industries
Lægeforeningen
InMobile
AK Nygart
DEIF
DMJX
Axel logo
qUINT Logo
KAUFMANN (1)
SMILfonden-logo
kurhotel_skodsborg
nemlig.com
Molecule Consultancy
Novicell