Consent
Follow topic LLM context A cited markdown file you can paste into your AI assistant (ChatGPT, Claude, a RAG or project knowledge base) to ground it in this topic. Contains: the overview, key law text, case law, enforcement and guidance for this topic. Everything links back to its source on overview.legal — legal information, not advice.Freely given, specific, informed indication of data subject wishes
‘consent’ of the data subject means any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her;
Overview
28 sources · Aug 27, 2026Legal Framework
"'consent' of the data subject means any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her;"
— GDPR Art. 4(11)
This statutory definition establishes four cumulative requirements — freely given, specific, informed, and unambiguous — each of which must be independently satisfied. Article 6(1)(a) makes consent one of six possible lawful bases for processing, while Article 7 sets the operational conditions: the controller bears the burden of demonstrating consent, consent requests must be clearly distinguishable from other matters, and withdrawal must be as easy as giving consent.
"The data subject shall have the right to withdraw his or her consent at any time. The withdrawal of consent shall not affect the lawfulness of processing based on consent before its withdrawal."
— GDPR Art. 7(3)
Article 8 adds age-verification obligations for children's consent in information society services, setting a default threshold of 16 (with a Member State floor of 13). Article 9 elevates the standard to "explicit consent" for special categories of data. Article 13 requires disclosure of the withdrawal right at the time of data collection.
Key Developments
The CJEU has reinforced the rigor of these requirements across multiple rulings. In Planet49, the Court confirmed that consent under Article 6(1)(a) must be tied to "one or more specific purposes." In Inteligo Media, the Court emphasized that consent embedded in broader declarations must be clearly separable:
"the request for consent shall be presented in a manner which is clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language."
— Inteligo Media SA v ANSPDCP
Enforcement authorities have applied the same specificity principle on the ground. The Belgian DPA, citing EDPB guidelines, held that controllers must offer a separate opt-in for each processing purpose — bundled consent does not satisfy the granularity requirement. The DPA also stressed that withdrawal mechanisms must be as simple as the original consent act, consistent with Article 7(3).
Status of the Debate
Consent remains actively contested in court, with divergent interpretations emerging at the highest judicial level. The Schrems v Meta litigation illustrates the unresolved tension between consent, contractual necessity, and platform power — particularly when special category data under Article 9 intersects with consent-based processing:
"Mr Schrems referred to his sexual orientation for the purpose of criticising Facebook's processing of personal data, including the processing of his own data."
— Maximilian Schrems v Meta Platforms Ireland Limited
This case departs from earlier CJEU authority and signals that the conditions for freely given consent in platform ecosystems — including the intersection with special category data under Article 9 — remain unresolved at the highest level. The EDPB's April 2024 opinion on consent-or-pay models further confirms that the debate over whether genuine freedom of choice exists in these contexts is far from settled.
Practical Guidance
- Document the consent lifecycle end-to-end. Article 7(1) imposes a burden of proof on the controller — maintain records showing who consented, when, what they were told, and to what they agreed.
- Provide granular opt-in for each processing purpose. Bundled or all-or-nothing consent fails the specificity requirement confirmed by Planet49 and the Belgian DPA; offer separate toggles for each purpose.
- Ensure withdrawal is as simple as giving consent. Article 7(3) requires parity of ease — if consent is a one-click action, withdrawal must be equally accessible.
- Segregate consent requests from other terms. Inteligo Media confirms that consent buried in general terms and conditions is not validly obtained.
- Verify age and parental authorization for minors. Article 8(2) requires reasonable efforts to verify parental consent for children below the applicable age threshold, calibrated to available technology.
Why here The entire document is about consent under GDPR, making it central to this topic.
the text this rests on
any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her.
assessed by deepseek/deepseek-v4-flash-0731 · 7 Sept 2026
Why here The recital sets out central requirements for consent: it must be demonstrable and informed, and the data subject must have a genuine choice, including the ability to refuse or withdraw without detriment.
the text this rests on
Consent should not be regarded as freely given if the data subject has no genuine or free choice or is unable to refuse or withdraw consent without detriment.
assessed by openai/gpt-6-luna · 8 Oct 2026
Why here The recital sets out circumstances in which consent is presumed not to be freely given, including a failure to allow separate consent for different processing operations.
the text this rests on
consent is presumed not to be freely given if it does not allow separate consent to be given to different personal data processing operations
assessed by openai/gpt-6-luna · 8 Oct 2026
Why here The recital sets out the required qualities of consent and gives examples of valid and invalid ways of expressing it. It also requires consent to cover the relevant processing purposes.
the text this rests on
Consent should be given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication
assessed by openai/gpt-6-luna · 10 Oct 2026
Why here The provision directly sets out the core requirements for consent as a lawful basis for processing, making it a primary source for this topic.
the text this rests on
Where processing is based on consent, the controller shall be able to demonstrate that the data subject has consented to processing of his or her personal data.
assessed by deepseek/deepseek-v4-flash-0731 · 26 Aug 2026
Why here The document includes a section 'Explicit Consent' discussing consent under GDPR and PSD2, including differences.
the text this rests on
the data subject has given consent to the processing of his or her personal data for one or more specific purposes
assessed by deepseek/deepseek-v4-flash-0731 · 7 Sept 2026
Why here The document identifies explicit consent as one of the Article 49 derogations.
the text this rests on
the “explicit consent derogation”
assessed by deepseek/deepseek-v4-flash-0731 · 28 Aug 2026
Why here Explicit consent is listed as one condition under which otherwise restricted automated decision-making may be allowed; the recital does not address consent generally.
the text this rests on
or when the data subject has given his or her explicit consent.
assessed by openai/gpt-6-luna · 10 Oct 2026
Why here Where the data subject has given consent, the recital permits further processing irrespective of purpose compatibility; it does not set consent-validity requirements.
the text this rests on
Where the data subject has given consent or the processing is based on Union or Member State law which constitutes a necessary and proportionate measure
assessed by openai/gpt-6-luna · 11 Oct 2026
Why here Withdrawal of consent is identified as a circumstance supporting erasure. The recital does not set out the requirements for valid consent.
the text this rests on
where a data subject has withdrawn his or her consent or objects to the processing of personal data concerning him or her
assessed by openai/gpt-6-luna · 8 Oct 2026
Why here Consent is one of the grounds on which the processing must be based for the portability right to apply; contract is the other stated basis.
the text this rests on
That right should apply where the data subject provided the personal data on the basis of his or her consent
assessed by openai/gpt-6-luna · 8 Oct 2026
Why here It expressly refers to obtaining the data subject’s consent before personal data are processed for targeted advertising, without setting out the full consent regime.
the text this rests on
need to obtain consent of the data subject prior to the processing of personal data for targeted advertising.
assessed by openai/gpt-6-luna · 8 Oct 2026
Why here The document lists parental consent mechanisms as a topic that codes may cover, but does not discuss consent as a lawful basis.
the text this rests on
mechanisms for obtaining parental consent
assessed by deepseek/deepseek-v4-flash-0731 · 7 Sept 2026
Why here The document lists consent withdrawal as a ground for erasure but notes it is rarely used in delisting.
the text this rests on
the data subject withdraws consent on which the processing is based (Article 17.1.b)
assessed by deepseek/deepseek-v4-flash-0731 · 28 Aug 2026
Why here Mentions user control but not consent as a lawful basis.
the text this rests on
The underlying processing of personal data which results in the delivery of a targeted message is often opaque.
assessed by deepseek/deepseek-v4-flash-0731 · 7 Sept 2026
Nothing of this type on this topic.
This is the top of each pile — all 111 Guidance · all 27 Laws · all 157 Case Law · all 510 Enforcement · all 140 News · all 69 Literature