What Counts as Valid Consent Under GDPR? A Plain-English Guide for Small Teams

en

Most small teams believe they have GDPR consent because users click “Accept.” In reality, a click is only the starting point. Under GDPR, consent is valid only when it meets a specific set of conditions, and if it doesn’t, the data processing it was meant to justify can be unlawful.

This guide explains what valid consent under GDPR really means, in plain English, so you can check your own setup without hiring a legal team.

The Official Definition (Simplified)

GDPR Article 4(11) defines consent as “any freely given, specific, informed and unambiguous indication of the data subject’s wishes” expressed through a statement or a clear affirmative action. Article 7 adds extra conditions on top, including proof and withdrawal.

Put simply, valid consent has six ingredients.

1. Freely Given

The user must have a real choice. Consent is not free if:

Access to your service depends on agreeing to unrelated data processing. There is a clear power imbalance (for example, employer and employee). The user can’t refuse without negative consequences.

Example: Forcing users to accept marketing emails in order to download a free ebook is risky. Offering the ebook with an optional newsletter checkbox is safer.

2. Specific

Consent must be tied to a clear purpose. A single “I agree to everything” checkbox covering analytics, marketing, and third-party sharing is too broad. If you have several purposes, give users separate choices (this is called granularity).

3. Informed

Before agreeing, people need to know at least:

  • Who you are (the data controller)
  • What data you collect
  • Why you collect it
  • That they can withdraw consent at any time

Write this in clear, simple language. A wall of legal text hidden behind a tiny link doesn’t count as informed.

4. Unambiguous (A Clear Affirmative Action)

The user must actively do something: tick an empty box, click an “I agree” button, or toggle a switch. These do not count:

  • Pre-ticked boxes
  • Silence or inactivity
  • “By continuing to browse, you accept…”

The Court of Justice of the EU settled the pre-ticked box question in the Planet49 case (2019): pre-selected checkboxes do not produce valid consent.

5. Easy to Withdraw

Withdrawing must be as easy as giving consent. If users agreed with one click, they shouldn’t have to email support or fill out a form to undo it. Provide a visible preference center or unsubscribe link, and honor the withdrawal promptly.

6. Provable

Here is where most small teams fall short. Under Article 7(1), you must be able to demonstrate that consent was given. A banner that appeared on screen is not evidence. A record is.

A solid consent record typically includes:

  • A user identifier
  • The exact purpose(s) consented to
  • Timestamp
  • The wording or version of the text the user saw
  • How consent was collected (form, banner, API, app)
  • Any later changes or withdrawals

If you want to go deeper on evidence, see our guide on how to prove a user gave consent under GDPR, and the difference between consent logging and a cookie banner.

When Consent Isn’t the Right Legal Basis

Consent is only one of six legal bases under GDPR. If you need data to deliver the service someone signed up for (like processing an order or creating an account), contract is usually the correct basis, not consent. Asking for consent when you don’t truly need it can backfire, because people can withdraw it, and then you’d have to stop processing.

Use consent mainly for optional activities: marketing emails, non-essential cookies, analytics that go beyond what’s strictly necessary, and sharing data with third parties for their own purposes.

A Special Note on Children

If you offer online services directly to children, GDPR sets the age of digital consent at 16, though EU member states may lower it to as low as 13. Below that age, you need consent from a parent or guardian.

A Quick Self-Check for Small Teams

Ask yourself:

  1. Can users say no without losing access to unrelated features?
  2. Is each purpose asked about separately?
  3. Does the user see clear, plain-language information before agreeing?
  4. Is the action active (no pre-ticked boxes)?
  5. Can users withdraw just as easily?
  6. Do you store proof of each consent event?

If you can answer “yes” to all six, you are in far better shape than most.

Final Thoughts

Valid consent isn’t about collecting more clicks. It’s about collecting meaningful, documented choices. Get the six ingredients right, keep a clean record, and you’ll be prepared for user questions, customer security reviews, and regulator inquiries alike.

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