DPIAs and Records of Processing
Your Article 30 record of processing set up and kept current, and data protection impact assessments under Article 35 carried out before a risky project starts.
- By
- By Bart Lieben, Attorney-at-Law
- Published
- Updated
The question
You are about to launch something new: a camera system, an app that tracks drivers, a scoring tool for job applicants, a customer analytics platform. Someone asks whether you need a DPIA. And when you look for the processing in your record, it turns out the record was last updated two years ago.
Two GDPR documents carry most of the weight here. The record of processing activities under Article 30 is the inventory: for each processing activity, the purposes, the categories of data subjects and personal data, the recipients, transfers to third countries, the envisaged time limits for erasure and a general description of security measures. It has to be available to the supervisory authority on request.
The data protection impact assessment under Article 35 is the deeper check for one processing. It is required where processing is likely to result in a high risk to the rights and freedoms of individuals. Article 35(3) names three cases in particular: systematic and extensive evaluation of people based on automated processing, including profiling, with legal or similarly significant effects; large-scale processing of special categories of data or data on criminal convictions; and systematic monitoring of a publicly accessible area on a large scale. Supervisory authorities publish lists of processing that always needs a DPIA (Article 35(4)), and the Belgian Data Protection Authority has adopted such a list. Processing that is not on the list can still need one.
Our approach
We start with the record, because a DPIA builds on it. If you have a spreadsheet, we import it into our register, which shows per entry which required elements are missing. If you have nothing, we build the record from short interviews with the people who run each process. Your team completes and maintains the entries in the client portal, with an explanation next to each field that names the article behind it. The lawyer reviews and approves every entry, and each approved version is dated. What a record of processing must contain gives the background.
For a new or changed processing, we first screen. A short questionnaire records the data, the scale, profiling, monitoring, vulnerable individuals and new technology, and checks them against Article 35(3) and the Belgian list. The outcome, with the criteria that triggered it, is confirmed by the lawyer. If no DPIA is needed, the reasoning is stored, because that choice should be documented as well.
When a DPIA is needed, we carry it out with your project team in our DPIA function, as a working record. It follows the minimum content of Article 35(7): a description of the processing and its purposes, an assessment of necessity and proportionality, an assessment of the risks to individuals, and the measures to address them. The description starts from the register entry, so the same facts are not written twice. We focus on harm to people, such as discrimination, loss of control over data or exposure of sensitive information.
If a high risk remains after the measures, Article 36 requires you to consult the supervisory authority before the processing starts. We prepare that consultation and the file that goes with it.
We work on our own technology, with our own AI, and a lawyer reviews every entry and every assessment before it is final. Where an AI system is involved, the DPIA also feeds the work under the AI Act (AI Act meets GDPR), and where the project is a website or app, we often start with a website technology audit.
What you get
- A record of processing activities, approved by a lawyer, exportable as HTML or PDF and ready to hand to the authority.
- A list of open points: entries without a retention period, transfers without a recorded safeguard, missing elements.
- A documented screening for each new or changed processing.
- A completed DPIA as a dated record, with risks, measures with owners and the residual risk.
- Where needed, a prior consultation file for the supervisory authority.
- Review dates, so register and DPIA are revisited when the processing changes.
Limits apply. A DPIA records how risks were assessed and reduced. It does not make the decision to go ahead for you, and it cannot remove a risk that the design of the project creates. If the honest conclusion is that a project needs to change, we will say so.
Next step
Send us a short description of the project or processing you are planning, and your current record if you have one. We will tell you whether a DPIA is needed and what the record is missing.
In short
- Record of processing with every element Article 30(1) lists
- Screening that shows whether a DPIA is needed, and why
- DPIAs with risks, measures and residual risk documented
- Prior consultation with the authority prepared where needed
- Register and assessments linked, so facts are written once
- Reviewed by a lawyer