, Nils-Erik Jansson
DPIA for generative AI: when it is required and how
A data protection impact assessment (DPIA) is required when at least two of the nine criteria on the list of IMY, the Swedish Authority for Privacy Protection, are met. A generative AI tool in legal work meets the new technology criterion, and in employment matters a second one too. The assessment should be done before first use, because the answer decides which matters can be entered. This guide covers the criteria, what the assessment must contain at a minimum, and how a department of one to ten lawyers can do it without a long document.
Updated by Nils-Erik Jansson
When it is required
Article 35 GDPR requires an impact assessment before a type of processing that is likely to result in a high risk to the rights and freedoms of natural persons, in particular when new technology is used [2]. IMY's list under Article 35(4) has nine criteria, and the rule of thumb is that an assessment is required when at least two are met, and in individual cases when only one is [1]. The criteria are: evaluation or scoring of people, automated decisions with legal effects, systematic monitoring, sensitive personal data, processing on a large scale, combining data from several processing operations, people in a weak or dependent position, new technology or new organisational solutions, and processing that prevents access to a service or a contract [1].
Put a generative AI tool used in legal work next to the list. New technology: yes, almost always. Sensitive data: yes in employment matters, in disputes about health or trade union membership, and in many law firm matters. Dependent position: yes when the data concerns employees. Large scale: yes if the archive is connected to the tool. Combining processing operations: yes when the contract archive, email and matter management system are connected to the same tool. Two criteria are easily met. The conclusion is that an impact assessment is required for the matter types where two criteria are met, and that it is simpler to do one for the tool, with limits per matter type, than to try to avoid it.
What it must contain
The minimum under Article 35(7), as IMY sets it out: a systematic description of the processing and its purposes, an assessment of necessity and proportionality, an assessment of the risks to the rights and freedoms of data subjects, and the measures planned to address those risks. The data protection officer must be consulted, the views of data subjects sought where appropriate, and the assessment reviewed [2].
For an AI tool, the four parts look like this.
The description. Which tool, which plan, which connections, which matter types, which categories of data subjects (employees, customers, counterparties, clients) and data, where the processing takes place and at which sub-processors. Here you reuse step one of the transfer assessment; see the guide on transfer impact assessments.
Necessity and proportionality. Why the tool is needed for the purpose, whether the same thing could be done with less data, and which legal basis the processing relies on for each matter type. This is where the department has to answer whether every matter type really needs to go in, and where the list of matters kept out gets its justification.
The risks. To the data subjects, not to the company: unauthorised access, reuse for training, incorrect output leading to incorrect decisions about a person, disclosure following an authority request, and retention longer than necessary. Likelihood and severity for each risk, briefly.
The measures. The agreement and its addenda, the retention periods, the permissions, the list of matters kept out, the review rule in the policy, and the training. And the residual risk after the measures, described honestly.
How to keep it short
One assessment per tool, with a table per matter type, is the format that works. The table has four columns: matter type, data involved, criteria met, and conclusion (entered, entered with conditions, kept out). The description and the measures are written once and apply to every row. The table is the part of the document used in day-to-day work. This is what the rows look like when filled in from the criteria above.
| Matter type | Data involved | Criteria met | Conclusion |
|---|---|---|---|
| Employment matters | Data about employees, sensitive data | New technology, sensitive data, dependent position | Decided per tool |
| Disputes about health or trade union membership | Sensitive data | New technology, sensitive data | Decided per tool |
| Many law firm matters | Sensitive data | New technology, sensitive data | Decided per tool |
| Archive connected to the tool | Data across the whole archive | New technology, large scale | Decided per tool |
| Contract archive, email and matter system connected to the same tool | Data from several processing operations | New technology, combined processing | Decided per tool |
In the conclusion column, you choose between entered, entered with conditions and kept out.
The assessment can be reused. The next tool gets the same structure, and half the content is the same. The next matter type is one more row. The GDPR guidance of the Swedish Bar Association (Sveriges advokatsamfund) treats the impact assessment as part of a firm's ordinary data protection work, not as a one-off project [3].
The data protection officer and IMY
The data protection officer must be consulted, and the document must show what the officer said. If the company has no data protection officer, record who held that role in the assessment.
Prior consultation with IMY is requested only if the assessment shows a high risk despite the measures [2]. If a legal department ends up there, it should consider moving a matter type to the kept out list, since the need for consultation then disappears.
How HOVR Legal works with this
HOVR Legal carries out the impact assessment where one is needed, as one of five parts of the data protection package, in your template and with a review with your data protection officer. For Claude, it is part of the setup, with the description of the processing already written from Anthropic's documentation. What else needs to be in place before the first matter is entered is in the checklist.
Frequently asked questions
- Is a DPIA required for every AI tool?
- No, only for processing that is likely to result in a high risk. IMY's rule of thumb is that an assessment is required when at least two of the nine criteria on its list are met, and in individual cases when only one is [1]. A generative tool almost always meets the new technology criterion. If it is also used for sensitive data, for data about employees or on a large scale, two criteria are met. The answer is yes for the matter types where two criteria are met.
- Can we use the vendor's own DPIA?
- As input, not as your assessment. The vendor can describe the processing on its side, but only you can assess necessity, proportionality and the risks to your data subjects, because only you know what data you enter and why. Article 35 places the responsibility on the controller.
- Do we have to consult IMY?
- Only if the assessment shows a high risk despite the measures you plan [1]. With the right contract, retention periods and a list of matters kept out of the tool, a legal department's use should not end up there. If it does, that is a sign that the use should be narrowed, not that prior consultation should be requested.
Sources
- [1]När ska en konsekvensbedömning genomföras, IMY, in Swedish; IMY's list under Article 35(4) with nine criteria
- [2]Konsekvensbedömningar och förhandssamråd, IMY, in Swedish; IMY on impact assessments and prior consultation
- [3]GDPR-vägledningen, Sveriges advokatsamfund, 10 september 2026, in Swedish; Swedish Bar Association GDPR guidance
Insights on the topic
Back to AI for legal
More under AI for legal
- Data protection package for AI tools in legal work
Fixed-scope engagement: transfer impact assessment, impact assessment where needed, draft addendum, policy and training. For the AI tool you use or consider.
- AI operating model for the legal department
Fixed-scope engagement for legal departments. You get an operating model for how AI is used, governed and followed up, whatever the tool.
- AI literacy training for lawyers: two hours
Two hours of training for your legal department or firm on your own tools and documents, documented as a measure under Article 4 of the AI Act.
- Data protection checklist for generative AI in legal work
A checklist for law firms and legal departments: five questions to answer before the first client data goes into an AI tool, and what counts as a pass.
- AI policy for the legal department: what it should contain
Outline of an AI policy for a legal department or law firm: permitted tools, what may be entered, review, responsibility, excluded matters and training.
- AI policy template for the legal department
An editable AI policy template for a legal department or law firm in nine sections, with comments on what to adapt and why.
- The EU AI Act for in-house counsel: what applies to users
What the EU AI Act requires of a legal department that uses generative AI: AI literacy since 2025, transparency since 2026 and when the high-risk rules apply.
- Transfer impact assessment for AI tools, step by step
The six steps of a transfer impact assessment for a US AI tool: map, choose a transfer tool, assess the country, supplement, document, review.
- Personal data in prompts: legal basis and information
When a lawyer writes about an employee, a counterparty or a customer in an AI tool, personal data is processed.
- AI incident response for legal teams
What a legal department does within 72 hours when a member of staff has entered data into an AI tool that should not have gone in.
- Anonymise before prompting: what works
How a lawyer removes personal data before text goes into an AI tool, and the difference between anonymisation and pseudonymisation.
- Swedish MBL and AI tools: must you negotiate first?
Swedish law: when an AI tool triggers the duty to negotiate under section 11 MBL, when informing under section 19 is enough, and with no collective agreement.
- Shadow AI in the legal department: one week of work
Staff use ChatGPT and Claude on private accounts for work. The legal department's week: map it, stop the worst, offer an approved tool, write the rule.
- Legal privilege and AI: the Swedish Bar guidance
What the Swedish Bar Association's guidance on generative AI requires for confidentiality: tools that do not train on client data, and terms read in full.
- Contracts with AI vendors: asking beyond standard terms
What a legal department or law firm asks of an AI vendor beyond the standard terms: authority requests, sub-processors, deletion, anonymisation, exit.
- On-premise or cloud AI for legal work
When a legal department or law firm should run AI locally and when the cloud is right: what local operation solves, what it costs, what it leaves open.
- Reviewing an AI answer in ten minutes: five steps
How a lawyer reviews an answer from Claude, Legora or ChatGPT before using it: sources, case law and statutes, figures, what is missing, and tone.
- AI literacy training for the legal department
What a two-hour training for lawyers using generative AI covers: what the tool does and does not do, your rules, practice on your own documents.
- AI guidance for lawyers in the EU and the UK
What the CCBE, the SRA, the Law Society, the Bar Council and the Swedish Bar Association require of lawyers using generative AI, and where they differ.
- The general counsel's AI report to the board: two pages
What the board needs to know about the company's AI use once a year, and what the general counsel can answer for.