, Nils-Erik Jansson
Shadow AI in the legal department: one week of work
In one week the legal department can map shadow AI, stop the worst, offer an approved alternative and write the rule. Shadow AI means staff using AI tools on their own accounts at work, with no contract, no settings and nobody knowing what has gone in. Here is the order of work, and what a week cannot do.
Updated by Nils-Erik Jansson
Why it is the legal department's question
Shadow AI ends up with the lawyer for two reasons. The first is that it is a contract and data protection question. A private account means that the employee has accepted the terms, the company has not, and the company has no data processing agreement with the vendor. Commitments that apply under commercial agreements, such as content not being used for training, do not apply to private accounts [1]. The guidance from the Swedish Bar Association (Sveriges advokatsamfund) expressly distinguishes between tools where the user accepts the terms as a private individual and tools the firm has contracted for in its business [2].
The second reason is that the legal department uses the tools itself. Whoever writes the rule for the company therefore starts with their own private accounts.
The week in a table, with the details under the headings below.
| Day | What | Who |
|---|---|---|
| Day one | Find out the position: which tools, how many users, for what | The lawyer, with the department heads and IT's logs |
| Day two | Stop the two or three risky uses until an approved tool is available | The lawyer, in the teams where those uses are |
| Days three and four | Offer an approved alternative: company contract, data processing agreement, settings and login through the company's identity system | The lawyer, with the company as contracting party |
| Day five | Write the rule on one page and announce it on the day the approved tool opens | The legal department |
| The week after | Two-hour training, a new look at the logs after a month | The legal department |
Day one: find out the position
Ask, without threatening. Three questions to the department heads are enough: which tools are used, by roughly how many people, and for what. Add IT's logs of traffic to the most common services if they exist. The aim is a picture of the position, and of which uses are harmless, such as rewording emails, summarising long texts and translating.
What you are looking for are the two or three uses that are not harmless: HR matters, customer data in volume, ongoing disputes, and anything involving clients if you are a law firm.
Day two: stop only the worst
Go to the teams where the risky uses are and ask them to stop just those until an approved tool is available. Say why: no contract, no control over retention, and for law firms no basis for disclosing client information. Say at the same time that an approved tool is coming, and when. A ban with no date for the alternative is hard to maintain.
If something has already gone in that should not have: assess whether it is a personal data breach (see the FAQ), ask the employee to delete the conversation, and note that deletion at the vendor takes time and does not reach everything.
Days three and four: offer an approved alternative
The alternative is what makes shadow AI go away. A company agreement with a vendor, with a data processing agreement, retention settings and login through the company's identity system, is what makes staff switch. Which vendor depends on what the company already has. If you have Microsoft 365, Copilot is the quickest to put in place. If the legal department wants a tool that can be configured with its own rules and contracts, Claude Team or Enterprise is an option, see Claude for Legal. The choice between them is a question of technology selection. For the step out of the shadow, it is enough that there is a contract and that logging in is easy.
The five data protection questions should be answered before the first matter goes into the new tool, see the checklist. Until then the rule from day two applies.
Day five: write the rule
One page. Which tools are approved and under which contract, what may be entered, which matters are kept out even in the approved tool, and whom to contact. The structure is in the guide on AI policy for the legal department. Announce the rule on the day the approved tool opens. Announced earlier, the rule is only a ban, with no way to do the right thing.
The week after: follow up
Two hours of training for those who use the tool, documented as a measure under Article 4 of the AI Act, see the guide on the AI Act for in-house counsel. Look at the logs again after a month. If traffic to private services has not gone down, the alternative is too cumbersome, and it is the alternative that needs fixing.
What a week cannot do
Get a full picture of everything already entered. Get the vendor to delete it. Replace tools the business has already built routines around. That is work for the coming months, and it only works if the approved alternative is there first.
How HOVR Legal works with this
HOVR Legal produces the five answers for the tool you choose in the data protection package, and the guideline and the training are included. If the department also needs an operating model for how AI is used in daily work, see AI operating model for the legal department.
Frequently asked questions
- Is it a personal data breach when an employee has pasted customer data into a private AI account?
- It can be. The data has gone to a recipient with no data processing agreement and to a third country with no transfer basis. Assess whether it is a personal data breach. If it is, it must be notified to IMY (the Swedish Authority for Privacy Protection) within 72 hours, unless it is unlikely to result in a risk to the data subjects. Document the assessment, even when the conclusion is that no notification is needed.
- Can we just block ChatGPT and Claude in the firewall?
- You can, but use then moves to mobile phones and to tools you do not know about. Blocking works when there is an approved alternative that is just as easy to reach. Without an alternative, blocking creates more shadow use.
- Is it enough to tell everyone not to enter personal data?
- No. The rule cannot be followed in practice, because so much text about work contains personal data: names of counterparties, employees, contact persons. The rule has to say which tool may be used, under which contract, and which matters are kept out even there.
Statements about Anthropic's terms and products were read on Anthropic's pages on 9 November 2026 and are checked at the start of every engagement.
Sources
- [1]Commercial Terms of Service, Anthropic
- [2]Vägledning om användning av generativ AI i advokatverksamhet, Sveriges advokatsamfund (Swedish Bar Association), 12 June 2025 (in Swedish), section 1 on open tools with private user terms
- [3]GDPR-vägledningen, Sveriges advokatsamfund (Swedish Bar Association), 10 September 2026 (in Swedish)
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.
- DPIA for generative AI: when it is required and how
When a legal department or law firm must carry out a DPIA under Article 35 GDPR for an AI tool, using the Swedish regulator IMY's nine criteria.
- 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.
- 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.