Legitimate interest vs consent under the GDPR comes down to control. Use consent when you want to give people a genuine choice and the law expects one, as it does for non-essential cookies, most marketing emails and special category data. Use legitimate interests when the processing is something people would reasonably expect, has a minimal privacy impact or serves a compelling purpose, and you can show your interests aren't overridden by theirs. Neither is "better": choosing the wrong one, or switching later because consent was refused, is what gets organisations into trouble.

For webmasters the short version is: consent for cookies, tracking and email marketing; legitimate interests for security, fraud prevention, server logs and responding to enquiries. The UK's new "recognised legitimate interests" basis doesn't change that for marketing. This guide explains why and shows how to run a legitimate interests assessment.

General information, not legal advice.

GDPR Article 6: the six lawful bases

Article 6 lists six lawful bases. You need one for every processing purpose, decided before you start and recorded in your privacy notice.

BasisWhen webmasters use it
ConsentNewsletters, tracking and advertising cookies, special category data
ContractDelivering a membership, subscription or purchase the user signed up for
Legal obligationKeeping tax records, responding to lawful orders
Vital interestsRare: emergencies
Public taskPublic bodies; almost never relevant to private sites
Legitimate interestsSecurity, fraud prevention, server logs, B2B contact, some analytics

The UK GDPR now has a seventh: recognised legitimate interests, covered below.

Consent is the right basis when

  • Another law requires consent anyway, for example the ePrivacy Directive or PECR for non-essential cookies and most marketing emails and texts.
  • You process special category data, such as information revealing sex life or sexual orientation, and no other Article 9 condition fits. Explicit consent is then usually the only realistic option.
  • The processing is intrusive or unexpected, such as profiling people for personalised advertising.
  • You can genuinely offer a choice and accept "no".

Legitimate interests is the right basis when

  • People would expect it: logging IPs for security, preventing fraud or bot traffic, replying to messages.
  • The impact on privacy is minimal and you can add safeguards.
  • Asking for consent would be meaningless or impractical, or refusing would undermine the purpose (you can't let fraudsters opt out of fraud checks).

Don't swap bases. If you ask for consent and the person refuses, you can't then process the same data for the same purpose on legitimate interests. Pick the right basis at the start.

How to run a legitimate interests assessment

The ICO and EU regulators describe a three-part test. Write it down: a legitimate interests assessment (LIA) is your evidence.

  1. Purpose test. Are you pursuing a legitimate interest? Commercial interests can qualify; the CJEU confirmed in October 2024 (C-621/22, KNLTB) that a purely commercial interest can be legitimate if it is lawful.
  2. Necessity test. Is the processing necessary for that purpose, or is there a less intrusive way to achieve it?
  3. Balancing test. Do the individual's interests, rights and freedoms override yours? Consider their reasonable expectations, the sensitivity of the data, the impact, whether they are vulnerable and what safeguards you apply.

Worked example (hypothetical)

An adult review site wants to keep server logs with full IP addresses for 30 days to detect click fraud and attacks.

  • Purpose: protecting the site and its affiliate revenue from fraud and abuse. Legitimate.
  • Necessity: IP addresses are needed to spot patterns; aggregated data wouldn't work. Thirty days covers typical investigation windows.
  • Balancing: visitors expect sites to keep security logs; logs are access-restricted, not used for marketing and deleted automatically. Page paths are retained but not linked to any identity. Outcome: legitimate interests is appropriate, with the safeguards recorded.

Now compare: the same site wants to build interest profiles from browsing to sell ad audiences. The data reveals sexual interests, visitors wouldn't expect it and the impact could be serious. That fails the balancing test, and special category rules point to explicit consent.

Lawful basis for marketing

The GDPR's recitals say direct marketing may be a legitimate interest, and since February 2026 the UK GDPR itself names direct marketing as an example. That doesn't mean you can email people without consent. Two layers apply:

  • PECR or ePrivacy decides whether you may send electronic marketing at all. For individuals, that generally means consent, or the soft opt-in for existing customers. See email marketing consent and the soft opt-in.
  • The GDPR then needs a lawful basis for the processing. Where PECR requires consent, consent is the natural GDPR basis too.

Legitimate interests is more realistic for postal marketing, some B2B emails to corporate addresses (where PECR permits) and analysing your own customer list. For personalised advertising, regulators are sceptical: the CJEU in Meta v Bundeskartellamt (C-252/21, July 2023) cast doubt on relying on legitimate interests for extensive tracking for ads, and the IAB's TCF v2.2 removed legitimate interests as an option for ad and content personalisation purposes.

Recognised legitimate interests in the UK

The Data (Use and Access) Act 2025 added a new lawful basis to the UK GDPR, in force since 5 February 2026. For a fixed list of purposes you don't need a balancing test, though the processing must still be necessary. The ICO lists five conditions:

  1. Responding to disclosure requests from bodies performing a public task.
  2. National security, public security and defence.
  3. Emergencies.
  4. Detecting, investigating or preventing crime.
  5. Safeguarding vulnerable individuals.

For a webmaster, the crime and safeguarding conditions can matter, for example when sharing information with police about suspected illegal content or protecting a child at risk. Marketing, analytics, affiliate tracking and advertising are not on the list, so they still need consent or an ordinary legitimate interests assessment. The EU has no equivalent, so for EU users you still need to balance in every case. More on the divergence in UK GDPR vs EU GDPR.

Special category data: a separate hurdle

For data revealing sex life, sexual orientation, health and other special categories, you need an Article 6 basis and an Article 9 condition. Legitimate interests is not an Article 9 condition. For most commercial uses on adult sites, that leaves explicit consent, or minimising data so you don't process special category data at all. Read our guide to special category data on adult sites.

What each basis means for people's rights

Your choice of basis changes what you must do when someone pushes back:

  • Consent: people can withdraw at any time, as easily as they gave it, and you must stop. They also get the right to data portability.
  • Legitimate interests: people can object. You must stop unless you can show compelling legitimate grounds that override their interests, or need the data for legal claims. For direct marketing, an objection is absolute: you must stop, no balancing allowed.
  • Contract and legal obligation: there is no right to object, but you must still be transparent and keep only what you need.

Build these into your processes: an unsubscribe link that works immediately, a suppression list so people aren't re-added, and a clear route for objections in your privacy notice.

Common scenarios at a glance

ProcessingTypical basis
Server security logsLegitimate interests
Bot and click-fraud detectionLegitimate interests
Analytics cookies (EU)Consent
Analytics cookies (UK, within the statistical exemption)PECR exemption plus legitimate interests
Affiliate tracking pixels on your pagesConsent
Newsletter to individualsConsent (or soft opt-in for customers)
Delivering a paid membershipContract
Keeping invoicesLegal obligation
Reporting suspected crime to police (UK)Recognised legitimate interests (crime condition)

Frequently asked questions

Is legitimate interest easier than consent?

It avoids asking, but it isn't easier: you must document an assessment, honour objections and accept that regulators may second-guess your balancing. Where consent is required by other laws, legitimate interests isn't an alternative.

Can I use legitimate interests for cookies?

Not for non-essential cookies. Cookie rules require consent unless an exemption applies. Legitimate interests can only be the GDPR basis for processing data from exempt cookies, such as UK statistical cookies.

Do I need a legitimate interests assessment for every purpose?

Yes, for each purpose where you rely on legitimate interests. Short assessments are fine for obvious, low-risk processing; keep more detailed ones for anything sensitive.

Next steps

List your processing purposes, assign a basis to each using the table above, and write short LIAs where needed. If you're building a mailing list, read how to build an email list for affiliate marketing alongside the consent rules, and find more in our GDPR and cookies section.