Legitimate interests can be a lawful basis for an AI agent's processing under GDPR, but only after a three-part assessment: is the interest legitimate, is the processing necessary for it, and do people's interests and rights override it? For an agent, the balance turns on what it reads, infers and does. Record it before launch.
What does the legitimate interests basis require?
Article 6 allows processing that is necessary for the legitimate interests of the controller or a third party, except where those interests are overridden by the interests or fundamental rights and freedoms of the person, in particular where the person is a child. Public authorities cannot rely on it for processing in the performance of their tasks.
Regulators read this as three tests, applied in order:
- Purpose test. Is there a legitimate interest? Commercial interests, fraud prevention, network and information security, and internal administration can all qualify. The interest must be real, present and lawful.
- Necessity test. Is the processing necessary for that interest? It must be a targeted and proportionate way to achieve it. If the same aim can be met with less data or less intrusive processing, the processing is not necessary.
- Balancing test. Do the person's interests, rights and freedoms override the interest? Consider the nature of the data, the reasonable expectations of the person, the likely impact, and the safeguards in place.
People have the right to object to processing based on legitimate interests. The controller must then stop unless it shows compelling legitimate grounds that override the person's interests, or the processing is for legal claims. Objection to direct marketing is absolute.
Who can rely on it?
Private sector controllers, for purposes that pass the three tests. It is often a good fit for agents that support internal efficiency, quality assurance, fraud detection or security monitoring. It is a poor fit where processing is intrusive, unexpected or involves special category data, which needs a separate condition in any case.
How do the three tests apply to an agent?
Purpose. Name the specific interest each capability serves. "Using AI" is not an interest. "Reducing the time customers wait for a reply to routine queries" is. "Detecting payments to accounts linked to known fraud" is.
Necessity. Agents test this hard, because they tend to process more than they need. Ask, per capability: does the agent need to read the whole record, or two fields? Does it need history beyond the current case? Does it need to infer anything new about the person? Each extra item weakens the necessity argument. Field-level access is the strongest support; see GDPR data minimisation for AI agents.
Balancing. Four agent-specific factors weigh in the balance:
- Expectations. Do customers expect an AI agent to read their messages and account history? Clear information shifts expectations; silence does not.
- Inference. Agents create new data, such as risk flags or vulnerability assessments. New inferences about people weigh against the controller, especially if they affect treatment. Profiling raises the stakes further; see GDPR profiling and AI agents.
- Action. An agent that only drafts for a person is less intrusive than one that acts. Depth matters to the balance.
- Safeguards. Bounds on what the agent can do, human approval before consequential actions, and short retention all tip the balance towards the controller.
If the processing feeds decisions with significant effects, Article 22 also applies; see whether GDPR allows AI agents to make automated decisions.
How do you run and record the assessment?
| Requirement | Control | Evidence it leaves |
|---|---|---|
| Identify the interest | Specific interest named per capability | Assessment section 1 |
| Necessity | Field-level access justified; less intrusive alternatives considered and rejected with reasons | Assessment section 2; access map |
| Reasonable expectations | Privacy information describes the agent's role in plain terms | Privacy notice; channel disclosures |
| Impact on people | Inferences listed; effects on treatment assessed | Assessment section 3 |
| Safeguards | Hold before consequential actions; bounds per capability; retention limits | Bound settings; approval records; schedule |
| Children and vulnerable people | Extra weight given; vulnerability triggers hand-over | Assessment notes; routing records |
| Right to object | Objection route; agent stops processing for that person unless compelling grounds documented | Objection log; refusal records |
| Review on change | New capability, source or inference triggers re-assessment | Change records |
The objection row deserves testing. Lodge an objection for a test customer and confirm the agent stops using their data for that purpose, everywhere it could.
What will a supervisor or auditor ask?
- Show us the legitimate interests assessment for this agent.
- Why is this processing necessary, rather than useful?
- What do customers know about the agent's use of their data?
- What does the agent infer about people, and how does that affect them?
- What happens when someone objects?
What does legitimate interests not cover?
It does not cover special category data on its own. It does not allow solely automated decisions with significant effects; Article 22 sets the rules for those. It is unavailable to public authorities for their tasks. And it does not displace other principles: processing can pass the balancing test and still breach minimisation or storage limitation. For the full map, see AI agent regulation, mapped to controls.
This is an explanation of the rules, not legal advice; confirm how they apply to you with counsel.
Where Pryme fits
Depth is part of the balancing test. In Pryme, each capability's depth is earned through Attest on the firm's own cases, and actions above it are held for a named person. An assessment can point to that design as a safeguard, and to the filed record of verdicts as proof it operates.
Questions people ask
Is improving efficiency a legitimate interest for using agents?
It can be. The processing must still be necessary for that aim and not overridden by people's interests. Efficiency alone rarely justifies intrusive processing or new inferences about people.
Do we need a separate assessment for each agent?
You need one for each purpose relying on legitimate interests. Agents serving the same purpose with the same data can share an assessment; agents with different capabilities usually cannot.
Can a customer object to an agent handling their query?
They can object to processing based on legitimate interests. If the processing is instead necessary for their contract, the objection right does not apply in the same way. Be clear which basis you use for which purpose.