Skip to content

Run your DPIAs where the processing activity already lives

An internal assessment goes out on the same engine you already send questionnaires with, and when it comes back you relate it to the processing activity it concerns, with its ID on it. You write the questions yourself, so a DPIA can follow your own method rather than a template of ours.

Unlimited users  •  Free onboarding and support  •  No commitment

Illustration of a small figure holding a card, with a thin line looping out from it to a large panel of rows with three tabs and back to a smaller card with a green tick held against the panel's edge
+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 internal assessments overview in .legal with six assessments sent, one showing a 3 of 7 question counter, several in progress and one submitted, each with its template, responsible and assignee

DPIAs on the activity

Meridian's forecasting pilot got assessed, and the internal assessment is still findable a year later

Sofie Bruhn is the DPO for the whole of Meridian Nordic. When the group decided that its consumption-forecasting pilot had to be properly assessed before it went anywhere near live metering data, she had done that job before: in a document, on a shared drive, followed a year later by an afternoon spent working out which activity it had actually been about. This time she wrote the questions once, as an internal assessment, and sent it to the engineer who runs the platform with a colleague named as responsible for it. When it came back she related it to the processing activity from the activity's own tab, where it now sits with its ID next to it.

  • The questions are Meridian's own, in one template that gets reused rather than rewritten.
  • It goes to the colleague who actually knows the system, and the responsible party is emailed when it lands.
  • Once she relates it to the processing activity it stays there with its ID, so next year it is one click from the activity.
  • Sofie can see sent, opened and submitted, and on a template without branching how far through the recipient has got, without asking anyone how it is going.

  • It belongs to the activity

    You relate a submitted internal assessment to the processing activity it concerns, with its ID shown, and you reach it again from that activity's own audit tab.

  • Your questions, not ours

    You build the template, section by section. There is no GDPR logic inside it, which is exactly why it can follow the method you already use.

  • Answered by whoever knows

    Send it to a named contact person, or share a link the respondent signs themselves up on, with a note saying which project it covers.

  • Status without chasing

    Sent, opened and submitted, with the responsible party emailed when it comes back, and older internal assessments still filterable by year.

Illustration of three panels of rows standing together, a broken line that never reaches a lone card set apart on the right, and two faint outline copies stepped back behind that card

DPIAs on the activity

The DPIA nobody can find a year later

Doing the DPIA is rarely the hard part. Finding it afterwards, and showing that it belonged to the activity that actually went live, is where this work usually falls down.

  • A document on a shared drive has no relationship to the activity it was written about.
  • The colleague who answered the questions has changed team, and their answers were in an email thread.
  • A year on, nobody can say for certain whether the version running now is the version that was assessed.
The Create new template dialogue for an internal assessment, with the template name, a description, Data Protection as compliance area, Type set to Internal and scoring switched on

DPIAs on the activity

There is no DPIA module, and that is the honest starting point

We would rather put that in writing than let a demo deliver it. What the platform has is an internal assessment: a questionnaire template with its Type set to Internal, which is what .legal built this part of the engine for.

  • No DPIA object, no wizard, no DPIA-specific fields and no GDPR logic inside it.
  • The same engine sends supplier audits and knowledge checks. An internal assessment is a third job for it.
  • Because nothing in it is shaped around GDPR, it can carry your own method rather than ours.
A processing activity in .legal on its Audits tab, switched to internal assessments, with a submitted DPIA listed by name, ID, deadline, responsible and template

DPIAs on the activity

It belongs to the processing activity, not to a folder

This is the part that makes the difference. You relate the submitted internal assessment to the activity it concerns, and from then on it is documentation on that activity rather than a document in a folder.

  • Processing activities and assets each carry an internal assessments tab, and that is where you relate one, with its ID in parentheses.
  • On an activity, the audit tab toggles between the internal assessments and the external audits attached to it.
  • It is related to the activity and never merged into it, so nothing in an internal assessment rewrites the activity's own fields.
The Send assessment dialogue with the assessment name, a description, the DPIA template, an assignee, a responsible colleague and a deadline

DPIAs on the activity

Getting the answers out of the colleague who knows

The DPO rarely holds the facts. The engineer does, or the project manager, and neither of them wants an account in a compliance platform.

  • Send it to a named contact person, chosen from the contact persons on your group companies.
  • Or share a public link, where the respondent puts in their own name and email to get started.
  • A note travels with that link and shows as a tooltip in the overview, which is where people write which project it covers.
Illustration of a long rail carrying three identical envelope cards at even intervals, an upright marker post with an open gate beyond it, a card with a green tick arriving after the marker, and a small figure facing the rail

DPIAs on the activity

A date you record, and a cadence you do not choose

Two facts sit next to each other here, and they are easy to blur into a promise we cannot make. So, plainly.

  • The deadline is recorded and enforces nothing. Your recipient can still submit after it has passed.
  • Reminders go to anyone who has not answered after 7 days, 14 days and 21 days, and then keep going.
  • The cadence is not something you can change, so it is worth building your follow-up around it.
Illustration of a figure holding a blank card above an empty tray with three open slots, faint outline pages behind the tray, and an unmarked dial lying switched off to one side

DPIAs on the activity

The call is still yours to make

We build the plan, not the filling-in. On work like this, that line has three edges worth naming before you see a demo.

  • Nothing screens your activities and nothing tells you a DPIA is needed. That call is yours and your adviser's.
  • Scoring is optional on the template and generic when it is on. A number here is not a data protection verdict.
  • Nothing is monitored or detected. The platform holds what a person submitted, and when they submitted it.
.legal in practice

Features for running DPIAs

Internal assessments on the audit engine

An internal assessment is a template with its Type set to Internal, built and sent on the same engine as your supplier audits. One engine, pointed inwards at a colleague instead of outwards at a vendor.

A template you build and activate

Give it an internal name, a description and the compliance areas it belongs to, then write the sections and the questions. Templates are created by administrators, and an active template is locked, so a change goes into a new version of that same template.

Related to the processing activity

Processing activities and assets each carry an internal assessments tab, and that is where you relate a submitted internal assessment, with its ID in parentheses. The same tab toggles across to the external audits on that activity.

Recipient, responsible party and a date

Sending means choosing the template, the recipient, who is responsible for the internal assessment and a date. The recipient is emailed on assignment, and the responsible party is emailed the moment it is submitted.

A public link with a note on it

Where picking a named contact is awkward, a public link lets the respondent register with name and email. A user comment travels with the link and shows as a tooltip in the overview, naming the project the internal assessment covers.

Four states and a year filter

Sent, opened and submitted, with an X of X question counter on templates that do not use branching. Year filtering keeps this year's internal assessments apart from last year's, and the compliance dashboard's latest submissions widget switches between internal assessments and external audits.

DPIAs on the activity

Frameworks this covers

One regulation, and the documentation kept where the work already sits.

  • icon-framework-GDPR

    GDPR

    Your DPIAs are GDPR work, and so are the processing activities you relate them to. .legal keeps both as documentation you can find again, rather than as documents you have to remember where you put.

    Learn about GDPR
.legal compliance platform

Run your DPIAs with...

Do you need your DPIAs kept on the processing activities they concern? We recommend the following modules for that task.

GDPR / Data Protection

Document GDPR and keep the Article 30 record current. This is where the processing activities live, and where you relate a submitted internal assessment to the one it concerns.

Explore GDPR

Vendor Management

The subscription the audit engine comes with, which is what carries an internal assessment out to a colleague and back again. The same engine you would use for supplier audits.

Explore Vendor Management

Our Customers

+400

companies

+11.000

users

+79.000

contracts

+14.000

processing activities

Mikkel Friis

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.
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

22 use cases

DPO

Keep your records of processing always audit-ready

The Article 30 record 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.
See the record stay current
Legal counsel

Run due diligence on your vendors

Classify a vendor on your own criteria, get the answers and documents you need with no login for them, and move the approved ones straight into contracts.
See vendor due diligence
Compliance & GRC lead

Run awareness training that reaches every colleague

Send out training and policies, chase the stragglers automatically, and prove every colleague completed it. You bring the material, we run the rails.
See awareness training
Compliance & GRC lead

Manage compliance across a group of companies

Run every company in the group from one platform, document once at group level, and still report entity by entity. Delivered by the Group Companies add-on.
See group compliance
Compliance & GRC lead

Multi-framework compliance: do the work once

Do a control once and it counts across every framework it maps to, with a simulated score on the ones you haven't started yet.
See multi-framework compliance
CISO & IT security

Get NIS2-ready without starting from scratch

Build on the ISO 27001 work you've already done, switch NIS2 on, and let a simulated score show how far ahead you already are.
See NIS2 readiness
DPO

From twelve spreadsheets to one record of processing

Your GDPR documentation already exists, it just lives in spreadsheets. Export what you have and we structure it in .legal for you, typically inside two weeks.
See the move off spreadsheets
Compliance & GRC lead

Build one risk register for the whole organisation

One register across GDPR, NIS2, AI and information security, where each risk area keeps its own matrix, scale and appetite. Delivered by the Enterprise Risk Management add-on.
See the risk register

Frequently Asked Questions about DPIAs and internal assessments

Is there a DPIA module in .legal?

No. Better that you read it here than discover it halfway through a demo. What exists is an internal assessment: a questionnaire template with its Type set to Internal, built and sent on the same audit engine as everything else you send out. There is no DPIA object, no wizard and no GDPR logic inside it. What makes it useful for this job is the other half, which is that a submitted internal assessment can be related to the processing activity it concerns and then stays reachable from it.

So what do we actually build?

A template, and it is yours. It carries an internal name, a description and the compliance areas it belongs to, and underneath that the sections and the questions you decide on. Questions come in four types: one answer from a list, several answers from a list, free text, and a date. Where your own method asks for a document to be attached, put that question to a demo, because we document the four types and not a fifth one for uploads. Creating templates is an administrator job, and an active template is locked, so a change goes into a new version of that same template rather than a second template beside it.

Does the platform tell us when a DPIA is needed?

No. Nothing screens your processing activities and nothing flags one as needing a DPIA, and we are not going to pretend otherwise, because that judgement is legal work and it is yours. .legal is a documentation platform, not an adviser. Once you have decided that an activity needs assessing, this is where the internal assessment is run, recorded and found again.

Where does a finished internal assessment end up?

On the processing activity, once you relate it there from the activity's own audit tab, with the assessment ID shown in parentheses so there is no doubt which one it is. Assets carry the same tab, and on an activity that tab toggles between the internal assessments and the external audits sitting on it. One thing to be clear about: an internal assessment is related to the activity, it is not merged into it, so nothing you answer in it rewrites the activity's own fields. That is deliberate. The internal assessment records what was answered at the time, and the activity keeps its own fields.

Who can we send it to, and do they need a login?

There are two routes. Either a named contact person, who is picked from the contact persons on your group companies, or a public link where the respondent registers with name and email. Neither route asks the recipient to become a user of the platform, and the link can carry a note that shows as a tooltip in the overview, which is where people usually write which project the internal assessment belongs to. One setup detail that catches people out: the contact persons on group companies are a different list from the contacts on a legal entity, which is where external audits pick their recipients.

The same engine, pointed at a supplier

Can we set our own deadline and reminders?

You can record a date, and you should know what it does. It does not lock anything and it does not escalate: the recipient can still submit after it has passed, so the date is there for the formalities and for your own planning. After 7 days, 14 days and 21 days a reminder goes automatically to anyone who has not answered yet, and it keeps coming. The cadence is not yours to configure, so the sensible move is to build your own follow-up around it. We would rather write that down than let you discover it on the third round.

Does an internal assessment produce a risk score?

Only if you switch scoring on for the template, and it is worth being precise about what that number is. It is a generic questionnaire score, weighted the way you weighted the questions. It is not a data protection risk verdict, it does not decide anything, and it has no connection to the risk module. An unscored internal assessment is a supported setup rather than a misconfiguration, so leaving scoring off is a legitimate choice. The conclusion is something a person writes, not something the platform calculates.

Is an internal assessment the same as the classification we answer about a vendor?

They are two different objects, and they get confused often enough to be worth separating here. A vendor classification is a questionnaire you answer yourself about a supplier, and the result is a risk level for that supplier. An internal assessment is a questionnaire you send to somebody else, who answers it, and what comes back you relate to a processing activity or an asset. Different objects, different template families, different jobs. They share the machinery, and that is all they share.

How do we find last year's internal assessment again?

From the activity, or from the year. The processing activity keeps every internal assessment related to it, each with its own ID, so the natural route is to open the activity it was about. Across the whole overview you can filter internal assessments by year, which is what makes a second round on the same activity readable next to the first one rather than a hunt through a shared drive.

What do we need to have for this to work?

Two things, and they are worth naming plainly. The processing activities sit in GDPR / Data Protection, and that is where you relate a finished internal assessment. The audit engine that carries an internal assessment out and back comes with the Vendor Management subscription, which is the same engine you would use for supplier audits and knowledge checks. If you already run processor audits, you already have what this page describes.

What a data processor is

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