Consent vs Legitimate Interest: Which Legal Basis Should Your Small SaaS Use?

en

Many early-stage founders treat consent as the default answer to every GDPR question. Add a checkbox, store the click, move on. But consent is only one of six legal bases for processing personal data, and for a small SaaS it is often not the best one.

This guide compares consent vs legitimate interest under GDPR for startups, so you can pick the right basis for each activity instead of using one for everything.

## Why Your Choice of Legal Basis Matters

Under Article 6 of GDPR, every processing activity needs a lawful basis, and you must decide before you start processing. You can’t easily swap bases later if one turns out to be inconvenient. The choice also shapes what rights users have. Consent can be withdrawn at any time, while legitimate interest comes with a right to object.

What Is Consent?

Consent means the user actively agrees to a specific purpose, and it must be freely given, specific, informed, and unambiguous. If you need a refresher, read our guide on what counts as valid consent under GDPR.

Strengths: it gives users real control and builds trust. Weaknesses: it can be withdrawn at any time, it requires proper records, and it fails if the user didn’t have a genuine choice.

What Is Legitimate Interest?

Legitimate interest lets you process data when you or a third party has a genuine business reason, as long as it doesn’t override the person’s rights and expectations. Regulators expect a three-part test, often documented as a Legitimate Interest Assessment (LIA):

Purpose: Is your interest real and lawful?

Necessity: Do you actually need this data to achieve it?

Balancing: Would a reasonable user expect this, and is the impact on them low?

Strengths: it is flexible and doesn’t depend on a click. Weaknesses: it requires written reasoning, users can object, and it is easy to misuse.

Side-by-Side Comparison

Factor Consent Legitimate Interest
User action needed Yes, opt-in No
Can the user withdraw? Anytime Can object, you may still override with strong grounds
Documentation Proof of consent record Written LIA
Best for Optional, non-essential uses Expected, low-risk, business-necessary uses
Risk if done wrong Invalid consent, unlawful processing Balancing test fails, complaints

Practical Examples for a Small SaaS

Activity Likely Legal Basis
Creating an account, delivering the service Contract
Fraud prevention and security logging Legitimate interest
Product update emails to existing customers Often legitimate interest, depending on local rules
Cold marketing newsletters to new contacts Consent
Non-essential cookies and ad tracking Consent
Sharing data with third parties for their own marketing Consent
Basic service analytics with minimal data Consent

Notice that “contract” appears first. Many core SaaS activities don’t need consent or legitimate interest at all.

The ePrivacy Trap

Here is where many founders get confused. Even when GDPR would allow legitimate interest, the ePrivacy Directive can still require consent. This applies to storing or reading information on a user’s device (cookies, local storage, tracking pixels) and to most electronic direct marketing. A “soft opt-in” exception exists for existing customers in some EU countries, but the rules differ by country. So for tracking and marketing, consent is usually the safer route.

A Simple Decision Guide

Ask these questions in order:

  1. Is the data strictly needed to deliver what the user signed up for? Use contract.
  2. Is a law requiring you to process it (such as tax records)? Use legal obligation.
  3. Does ePrivacy require consent (cookies, tracking, most marketing)? Use consent.
  4. Is it a low-risk activity users would reasonably expect? Consider legitimate interest, and write down your LIA.
  5. Is it sensitive, surprising, or intrusive? Choose consent, or reconsider the activity.

Common Mistakes to Avoid

  • Using consent for everything. If you collect consent for something you truly need, withdrawal forces you to stop, which creates a mess.
  • **Switching bases after a withdrawal. **Regulators view “you said no, so we’ll use legitimate interest instead” as a serious red flag.
  • Skipping the LIA. “We have a legitimate interest” without documentation won’t hold up in an audit.
  • Ignoring objections. For direct marketing, the right to object is absolute.
  • Mixing purposes. Each purpose needs its own legal basis.

Final Thoughts

Consent and legitimate interest aren’t rivals. They are tools for different jobs. Use consent for optional, intrusive, or tracking-related activities, and legitimate interest for expected, low-impact, genuinely necessary ones, backed by a short written assessment. Whichever you choose, document it. When consent is your basis, keep records that prove the user gave consent, and when it’s legitimate interest, keep your LIA on file.

> This article is for general information and isn’t legal advice. For your specific situation, consult a qualified data protection professional.