Personal data in prompts: legal basis and information

The legal basis for personal data in a prompt is the one that already carries the matter: the employment contract, the contract with the customer or a documented legitimate interests assessment. Consent rarely works. The data subjects must be told that the tool is used, and one sentence in existing notices does that. The checklist answers whether the tool may be used. This guide picks up from there, when the lawyer enters a dismissal, a dispute with a customer or a contract with a named contact person.

Updated by Nils-Erik Jansson

What is processed when a lawyer writes a prompt

Much legal work is about people: employees in HR matters, contact persons and authorised signatories in contracts, customers in complaints and disputes, clients and opposing parties in law firm matters. When text about them goes into an AI tool, personal data is processed by a processor. That processing needs a legal basis under Article 6 and information under Article 13 or 14 [1]. This is not new. The same applied when the text was written in a document in the cloud. What is new is that the question gets asked, because the tool is visible in a way the document system is not.

The basis follows the purpose, by category

The legal basis for the processing in the tool is the same as for the matter. The overview of the six legal bases from IMY (the Swedish Authority for Privacy Protection) [4] goes a long way when it is applied by category.

Category Legal basis Comment
Employees The employment contract when the processing is needed to perform it, for example pay and time reporting. Legal obligation when law or a collective agreement (an agreement with a trade union on terms of employment) requires it. Legitimate interests for the rest, for example investigating misconduct or preparing a negotiation. IMY writes that an employer cannot normally rely on consent for employee data, because employees as a rule cannot consent freely [3]. That applies in the tool too.
Counterparties and contact persons in contracts Legitimate interests, weighing the company's interest in entering into and managing contracts against the contact person's expectations. A contact person in a supplier contract expects their name to be processed in contract management. That carries weight in the assessment.
Customers The contract with the customer when the processing is needed to perform it; legitimate interests for disputes and complaints. The company is protecting its rights in disputes and complaints.
Clients and opposing parties in law firm matters The engagement agreement and legitimate interests. The firm processes as controller for its own business. The professional secrecy that binds an advokat (a member of the Swedish Bar Association) sits as a layer on top. The Swedish Bar Association's GDPR guidance covers the firm's role and legal bases [5]. What its guidance on generative AI requires beyond that is in the guide on legal privilege and AI.

The legitimate interests assessment is written down

Where processing rests on legitimate interests, IMY requires that the interest is clearly stated, that the processing is necessary in the sense that the same result cannot be reached in a less intrusive way, and that it is weighed against what the data subject can reasonably expect. The assessment must be documented [2].

For an AI tool the necessity question becomes concrete: does the person's name need to be in the prompt for the answer to be right? It does not always. A dismissal can be assessed with "the employee" in place of the name, a complaint with "the customer". That is the subject of the guide on anonymising before prompting, and it is also part of the assessment: if you remove what is not needed, the assessment is easier to document.

Write the documentation by category of matter, one page per category. Keep it with the impact assessment, see the guide on DPIA for generative AI, and update it when the purposes change.

Information to the data subjects

Article 13 applies when the data is collected from the person, Article 14 when it comes from someone else. Both require, among other things, the purpose, the legal basis, the recipients or categories of recipients, transfers to third countries and the retention period. Under Article 14 the information must be given within a reasonable period and at the latest within one month [1].

Start from the information you already have: the staff handbook or the privacy notice for employees, the privacy policy for customers, the terms of engagement for clients. What needs adding is a sentence saying that the company uses AI tools from external vendors as processors for legal and administrative work, which category of vendor is involved, and that transfers to third countries rely on standard contractual clauses where that is the case. Counterparties' contact persons are seldom informed directly. One solution is to have the information in the privacy notice you refer to in the contract and on the website. Then you should not need to rely on the Article 14 exemption for disproportionate effort, since the information is easy to provide.

What is needed is one sentence in three existing texts and a date for when it was added.

What this does not solve

The third country transfer, which is an assessment of its own, see transfer impact assessment. Special category data under Article 9, which needs an exception in addition to the basis in Article 6. And the matters where the legal basis question is hard in itself, whatever the tool. The tool does not make doubtful processing lawful, and it does not make lawful processing doubtful.

The basis per category, the documented legitimate interests assessment and the additions to the privacy notices are part of the data protection package, as part of the impact assessment and the guideline. For Claude they are part of the setup. What else should be in place before the first matter goes in is in the checklist.

Frequently asked questions

Do we need a new legal basis to use AI?
No. The tool is a way of processing data you already process for a purpose you already have. The legal basis follows the purpose: performing the employment contract, managing a contract with a customer, protecting the company's rights in a dispute. What needs doing is to check that the basis covers the new processing, document that, and make sure the information to the data subjects mentions that tools of this kind are used.
Can we ask employees to consent to their data being processed in the tool?
Not normally. IMY, the Swedish Authority for Privacy Protection, writes that an employer cannot normally rely on consent as the legal basis for employee data, because employees are in a position of dependence and as a rule cannot give consent freely [3]. The basis is instead the employment contract, a legal obligation or a documented legitimate interests assessment. Consent as a basis also means the processing must stop when consent is withdrawn, which is rarely possible in an ongoing matter.
Do we have to update the privacy policy?
Yes, by one sentence. The information to employees, customers and counterparties must state the purpose, legal basis, recipients and transfers to third countries. An AI tool from a US vendor is a new category of recipient and often a new transfer, so that sentence is needed in the existing texts. You do not need a new policy.

Sources

  1. [1]Regulation (EU) 2016/679 (GDPR), Articles 6, 13 and 14 and Recital 26, EUR-Lex (Swedish language version)
  2. [2]Intresseavvägning, IMY (in Swedish)
  3. [3]Rättslig grund i arbetslivet, IMY (in Swedish)
  4. [4]Rättslig grund, IMY (in Swedish)
  5. [5]GDPR-vägledningen, Sveriges advokatsamfund (Swedish Bar Association), 10 September 2026 (in Swedish)

Back to AI for legal

More under AI for legal