Brass scales of justice beside a laptop on a desk

Legitimate interest gets its final rulebook: what the EDPB's new guidelines mean for CDOs

Legitimate interest is the legal basis behind a lot of everyday data work: analytics, fraud prevention, security monitoring, some marketing and plenty of internal admin. For two years the main European guidance on it was a consultation draft. That has now changed. The European Data Protection Board (EDPB) adopted the final version of its Guidelines 1/2024 on Article 6(1)(f) GDPR on 10 November 2026, and published it alongside a new flowchart for the legitimate interest assessment and a report on the consultation.

For Chief Data Officers this is the text that EU data protection authorities will now work from. It is worth an hour of your time, and probably a review of your processing register.

What has been published

The new Version 2.0 replaces the draft adopted on 8 October 2024. The public consultation on that draft ran from 9 October to 20 November 2024 and drew 80 responses, most of them from business associations and companies.

The EDPB is open about how it handled the feedback. Many responses said the draft was too restrictive. The board's view is that most of those comments rested on misunderstandings of the GDPR or of the guidelines, so they "have not led to significant changes". It did add clarifications and examples, and it declined requests for sector-specific guidance or an "allowlist" of approved activities, saying these fall outside the scope of general guidelines.

So if you were waiting for the final version to be softer, it isn't. The structure is the same, with clearer wording in places.

The three tests, in plain terms

To rely on legitimate interest, all three of these conditions have to be met, and the EDPB says you should assess and document them before the processing starts:

  • A legitimate interest. The interest has to be lawful, clearly articulated, and present and effective. A vague or hypothetical interest does not count.
  • Necessity. If the interest can reasonably be achieved just as effectively by other means that are less intrusive for people, legitimate interest is not available. The guidelines tie this to data minimisation and talk about processing that is "strictly necessary".
  • Balancing. The interests, rights and freedoms of the people affected must not override the interest being pursued.

The board also repeats a line from the draft that is worth pinning to the wall: legitimate interest should not be treated as a "last resort", and it should not be chosen automatically because it seems less demanding than other legal bases.

What is new or clearer in the final version

A few changes stand out for data teams.

Positive effects count. The balancing test should consider how people can be affected both positively and negatively. The aim is to avoid a disproportionate impact, not to avoid any impact at all.

Expectations are about context, not just your sector. When judging what people reasonably expect, the final text says you should consider what can justifiably be expected in that context, not only what is common in your industry. "Everyone in our sector does this" is not enough on its own.

Mitigating measures need to show their working. If the balance looks unfavourable, you can add measures that go beyond what the law requires, such as extra transparency or easier ways to exercise rights. But you need to be able to show how those measures change the outcome of the test.

Transparency about the balancing test. As a matter of best practice, the EDPB says it is advisable to tell people that they can get information on the balancing test on request.

Fraud prevention needs specifics. The final text recognises fraud prevention as a legitimate interest that can matter to a wider community, but asks controllers to be specific about the type of fraud they are trying to prevent and the data they really need.

AI is covered by reference. Rather than a full AI section, the guidelines point to the EDPB's Opinion 28/2024 on AI models. They give examples of interests that may be legitimate, such as building a conversational agent to help users, an AI system to detect fraudulent content or behaviour, or better threat detection in an information system.

The DPO should be involved properly and in good time. Where you have a data protection officer, the guidelines say they should be involved properly and in a timely manner in the assessment.

The UK picture

The EDPB guidelines apply to the EU GDPR, so they matter directly if you handle personal data about people in the EU. In the UK, the Data (Use and Access) Act 2025 added a separate lawful basis called "recognised legitimate interest". The ICO's guidance, published in March 2026, explains that it covers a short list of public interest purposes set out in Annex 1 of the UK GDPR, such as crime prevention, national security, emergencies, safeguarding and responding to requests from organisations with public tasks.

For those purposes you don't need a balancing test, because the law has already done it, but you still have to show the processing is necessary. The ICO also says you don't have to change lawful basis if you already use legitimate interests for one of these purposes. For everything else, including most commercial uses, the ordinary legitimate interests basis and its three-part test still apply in the UK too.

What CDOs can do now

  • List every activity that relies on legitimate interest. Pull them from your record of processing and check each one has a written assessment made before the processing began.
  • Check each assessment covers all three steps. Many older assessments describe the interest in detail and skip quickly over necessity and balancing. The final guidelines expect all three.
  • Test necessity properly. For each activity, write down the less intrusive options you considered and why they would not work just as well. This is where data minimisation decisions should be recorded.
  • Use the flowchart as a template. The EDPB's annex gives a simple sequence for the assessment. Mapping your existing template against it is a quick way to spot gaps.
  • Record your mitigating measures and their effect. If pseudonymisation, shorter retention or an easy opt-out is what tips the balance, say so, and say why.
  • Look again at fraud and security use cases. Make sure each one names the specific risk, the data used and how long it is kept.
  • Update privacy notices. Name the legitimate interests you rely on and consider adding a line that people can ask for information about your balancing test.
  • Keep one process with UK and EU settings. If you work across both, flag where recognised legitimate interest might apply in the UK, and keep the full three-step assessment as the default everywhere else.

Legitimate interest is flexible, and the EDPB still sees it as a normal legal basis. What the final guidelines make clear is that the flexibility comes with paperwork. The organisations that can produce a clear, dated assessment for each use will be in a much better position when a regulator, or a customer, asks why.

Sources

Image: Katrin Bolovtsova on Pexels (Pexels License).