Skip to main content

Lesson 15 of 25

Consent & Processing Special-Category Data (Articles 7 & 9)

5 min read · CIPP/E

Learn what makes consent valid—freely given, specific, informed, unambiguous—the children's-consent ages, and the Article 9(2) conditions, including explicit consent, that unlock special-category processing.

Why consent is the trickiest basis

  • Article 4(11) + Article 7 set a high bar
  • Freely given, specific, informed, unambiguous
  • Must be as easy to withdraw as to give
  • Often the wrong basis to choose

Consent feels like the obvious lawful basis, but it is the one organisations most often get wrong, and the exam exploits that. The GDPR sets a deliberately high bar. Article 4(11) defines consent as any freely given, specific, informed, and unambiguous indication of the data subject's wishes, given by a statement or a clear affirmative action.

Article 7 then adds conditions, including that withdrawal must be as easy as giving consent. Because the bar is high and consent can be withdrawn at any time, it is often not the most robust basis; for many activities, contract or legitimate interests is cleaner. Let's break down each element, because the exam tests them individually.

The four elements of valid consent

  • Freely given — real choice, no imbalance or detriment
  • Specific — separate consent per purpose, no bundling
  • Informed — who you are and what you'll do
  • Unambiguous — clear affirmative act, not silence

Valid consent has four elements. Freely given means the person has a genuine choice; consent is not free if refusing causes detriment, if there is a clear power imbalance, for example employer over employee, or if the service is conditioned on consent that is not necessary for it. Specific means consent is sought separately for each distinct purpose; you cannot bundle several purposes into one tick.

Informed means the person knows at least the controller's identity and the purposes of the processing before they agree. And unambiguous means consent is given by a clear affirmative action, such as ticking an unchecked box; silence, inactivity, or pre-ticked boxes do not count. Recital 32 is explicit that pre-ticked boxes are invalid, and the CJEU confirmed it.

Watch for those traps.

Demonstrating and withdrawing consent

  • Article 7(1) — controller must prove consent was given
  • Article 7(3) — withdrawal at any time, as easy as giving it
  • Withdrawal doesn't undo past lawful processing
  • Tell people about the right to withdraw before they consent

Article 7 adds operational duties. Under Article 7(1), the controller must be able to demonstrate that the data subject consented, that is accountability applied to consent, so keep records of who consented, when, and to what. Under Article 7(3), the person can withdraw consent at any time, and it must be as easy to withdraw as it was to give; you cannot make signing up a click and opting out a phone call.

Withdrawing consent does not make past processing unlawful, it just stops future processing on that basis. And you must inform people of the right to withdraw before they consent. If a scenario describes hard-to-find opt-outs or buried withdrawal mechanisms, that is an Article 7(3) failure.

Children's consent (Article 8)

  • Applies to information-society services offered directly to children
  • Default digital-consent age is 16
  • Member states may lower it, but not below 13
  • Below the age — need parental authorisation

Article 8 sets special rules for children's consent in the context of online services, what the GDPR calls information-society services, offered directly to a child. Where consent is the basis, the child can consent on their own from the age of sixteen by default. Below that age, the processing is lawful only with the consent or authorisation of the holder of parental responsibility, and the controller must make reasonable efforts to verify it.

Crucially, member states may set a lower age, but not below thirteen. So the digital age of consent ranges from thirteen to sixteen depending on the country. The exam tests both the default of sixteen and the floor of thirteen, so know both numbers.

Processing special-category data (Article 9(2))

  • Article 9(1) prohibits; Article 9(2) lists the exceptions
  • Explicit consent — a higher standard than ordinary consent
  • Employment/social-security law; vital interests; public health
  • Not-for-profit bodies; data made public; legal claims; research

Finally, the conditions for special-category data. Article 9(1) prohibits processing the sensitive categories we listed earlier, and Article 9(2) provides the limited exceptions that lift the prohibition. They include the data subject's explicit consent, a higher standard than ordinary consent, usually requiring an express statement; processing necessary for employment, social-security, or social-protection law; protecting someone's vital interests where they cannot consent; processing by a not-for-profit body about its members; data the person has manifestly made public; the establishment or defence of legal claims; substantial public interest with a legal basis; preventive or occupational medicine and public health; and archiving, research, or statistics.

The key exam points: you need an Article 9(2) condition in addition to your Article 6 basis, and for special-category data, consent must be explicit. Both keys, every time.

Recap

  • Consent: freely given, specific, informed, unambiguous (Art. 4(11), 7)
  • No pre-ticked boxes; withdrawal as easy as giving
  • Children: default 16, floor 13 (Art. 8)
  • Special-category data: explicit consent or another Article 9(2) condition

So, consent and sensitive data. Valid consent under Articles 4(11) and 7 must be freely given, specific, informed, and unambiguous, given by a clear affirmative act, never a pre-ticked box, and withdrawable as easily as it was given, with the controller able to prove it. For children using online services, the default digital-consent age is sixteen, and member states may lower it only to thirteen.

And for special-category data, you need both an Article 6 basis and an Article 9(2) condition, with consent in this context being explicit. Next, we cover what you must tell people, transparency and privacy notices under Articles 13 and 14. First, go test yourself on consent and special-category data.

Sources

  • Regulation (EU) 2016/679 (GDPR), Article 4(11) (definition of consent), Article 7 (conditions for consent), Article 8 (children's consent), Article 9(2) (special-category conditions)
  • Recitals 32, 42, 43
  • EDPB Guidelines 05/2020 on consent

Test your knowledge

A few CIPP/E questions on this material — pick an answer to see the explanation.

  1. Q1. An organisation appoints its head of marketing as DPO. Why is this problematic?

  2. Q2. A company completes a DPIA for a new employee-monitoring system and determines that a high residual risk to employees remains even after all proposed mitigations. What must the company do before launching the system?

  3. Q3. A large company violates Article 5 data-protection principles in a sustained and intentional manner. Under Article 83, what maximum fine applies?

  4. Q4. A data subject suffers anxiety and reputational damage after a controller's data breach exposes their personal information. Under Article 82, can the data subject claim compensation for this non-material damage?

Ready to practice?

Put this lesson to work on real CIPP/E questions.

Drill the full CIPP/E bank →