Regulations

GDPR: prove the consent, then honour it.

The General Data Protection Regulation has applied since 25 May 2018. Article 7 asks you to demonstrate consent. A banner log is not a demonstration. A hash-chained receipt with notice version and purpose is closer. This page is education, not counsel.

25 May 2018

In force across the EEA (and UK GDPR parallel)

Art. 7

Controller must be able to demonstrate consent

4% / €20M

Upper-tier administrative fine (whichever is higher)

In force since 25 May 2018. No countdown — the duties are current.

Introduction

What is GDPR?

GDPR is the EU’s general law on personal data. It applies to organisations in the Union and, in many cases, to organisations outside it that offer goods or monitor people in the Union. Lawful basis is the spine: consent is one basis, not the only one. Whatever basis you claim, you still owe transparency, purpose limitation, security, and rights.

Lawful basis first

Article 6 lists the grounds. If you say consent, Article 7’s quality tests apply. If you say legitimate interests, you still document the balancing test — you do not hide a marketing pixel behind a cookie wall labelled ‘necessary’.

Demonstrate, don’t assert

Article 7(1): the controller shall be able to demonstrate that the data subject consented. Screenshots of a theme are not a demonstration.

Signals are inputs

TCF v2.3, GPP, and Global Privacy Control can feed the same ledger. Parallel toys that never reach processors are theatre.

Enforcement downstream

A CMP that never projects grant/withdraw into tags, CDPs, and AI pipelines still leaks personal data.

Key terms

Data subject
The identified or identifiable natural person.
Controller
Determines purposes and means of processing.
Processor
Processes on behalf of the controller (Art. 28 contract).
Supervisory authority
The national DPA; one-stop-shop for cross-border cases via the lead authority.
Special category data
Art. 9 data (health, biometrics used to identify, etc.) — extra conditions, not a DPDP clone.
DPIA
Data protection impact assessment where processing is likely high risk (Art. 35).
Planning

Timeline

  1. In force

    GDPR applies

    • Directly applicable in EU member states
    • Extra-territorial reach via Art. 3
    • UK GDPR continues as assimilated law after Brexit — similar duties, different authority
  2. Practice

    What actually moved

    • Cookie consent + TCF as the public face of Art. 7 for ads
    • Schrems II / transfer tools for extra-EEA flows
    • DSA, DMA, and browser-level signals stacking on top of GDPR — still not a replacement for Art. 6

Notable rules

Art. 5

Principles

Lawfulness, fairness, transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; accountability.

Art. 6

Lawful bases

Consent, contract, legal obligation, vital interests, public task, legitimate interests. Pick one per purpose and keep it honest.

Art. 7

Conditions for consent

Distinguishable, intelligible, freely given. Withdrawal as easy as grant. Pre-ticked boxes fail.

Arts. 13–14

Information duties

Privacy information at collection (or within a month if obtained elsewhere). Version the notice you actually showed.

Art. 33

Breach to the SA

Without undue delay and, where feasible, not later than 72 hours after becoming aware — unless unlikely to result in a risk.

Art. 28

Processors

Written instructions, confidentiality, sub-processor controls, deletion or return at end of service.

Processing without a consent grant

Article 6 is the menu. Consent is not required when another basis genuinely fits — and using the wrong basis is worse than admitting you needed consent.

6(1)(a)

Consent

Freely given, specific, informed, unambiguous indication of wishes.

6(1)(b)

Contract

Necessary for a contract with the data subject, or to take steps at their request.

6(1)(c)

Legal obligation

Necessary to comply with EU or member-state law.

6(1)(d)

Vital interests

Life-and-death processing — narrow.

6(1)(e)

Public task

Public interest or official authority.

6(1)(f)

Legitimate interests

Controller (or third party) interests not overridden by the subject’s rights — document the LIA.

Does this act apply to you?

Select an industry. This is orientation — thresholds and extra-territorial tests still need counsel.

Implementing

A working sequence

Accountability is a file you can open: records of processing, notice versions, basis per purpose, processor list, rights SLAs, breach clock.

  1. 1

    Map

    Purposes, categories, recipients, transfers, retention.

  2. 2

    Basis

    Article 6 (and 9 if needed) per purpose — written down.

  3. 3

    Inform

    Arts. 13–14 notices; cookie/ePrivacy layer where it applies.

  4. 4

    Collect

    Consent events or documented non-consent bases.

  5. 5

    Enforce

    Project the decision into processors and tags.

  6. 6

    Rights

    Access, erasure, objection, portability — clocks and identity.

  7. 7

    Incident

    Art. 33/34 playbooks; 72-hour awareness clock.

Readiness checklist

Mark what you already operate. Stored only in this browser. Not a certificate and not legal advice.

Orientation score 0/6 — not a compliance certificate.

Consent capture and Art. 7 proof

Versioned notices, purpose grants, withdrawal.

  • Unbundled purposes
  • Easy withdrawal
  • TCF / GPP / GPC as ledger inputs
Related product

Data-subject rights

Arts. 15–22 as workflows, not an inbox alias.

  • Access and portability packs
  • Erasure / restriction / objection
  • Identity verification
Related product

Records of processing

Art. 30 is the map, not a once-a-year PDF.

  • Purpose register
  • Recipient and transfer flags
  • Retention linked to purpose
Related product

Processor governance

Art. 28 in force, not in a drawer.

  • DPA inventory
  • Sub-processors
  • Transfer tools
Related product

Breach clock

72 hours to the SA when the threshold is met.

  • Awareness timestamp
  • Risk assessment
  • Subject notification when required
Related product

Server-side enforcement

Honour the basis where data actually flows.

  • Tag / CDP / AI pipeline suppression
  • Fail closed on uncertain geo
Related product
Compliance

Rights

Access (Art. 15)

Whether you process, what, why, and with whom.

Rectification (Art. 16)

Complete or correct personal data.

Erasure (Art. 17)

The right to be forgotten — with listed exceptions.

Restriction (Art. 18)

Pause processing while a dispute is live.

Portability (Art. 20)

Structured, machine-readable copy when processing is consent- or contract-based and automated.

Object (Art. 21)

Including to direct marketing — which must stop.

Withdraw consent

As easy as given; other bases for other purposes may remain.

Penalties (orientation)

Up to €10M or 2%

Lower-tier administrative fines (Art. 83(4))

Up to €20M or 4%

Upper-tier (Arts. 5, 6, 7, 9, rights, transfers…)

Civil

Compensation (Art. 82)

Individuals can claim damages separately from DPA fines. Member-state DPAs also publish enforcement themes — read yours.

Questions

Do we still need GDPR if we have a cookie banner?

A banner is an ePrivacy/consent UX. GDPR still requires a lawful basis per purpose, records, processors, rights, and security. The banner is one capture surface.

Is legitimate interests enough for analytics?

Sometimes, in some member states, for some strictly necessary measurements — and often not for advertising analytics. Document the LIA; do not cargo-cult a CMP default.

How do TCF and GPC fit?

They are signals. HashQuill treats them as inputs to the same ledger as an explicit grant. They are not a second source of truth.

Is this legal advice?

No. Your DPO and counsel own bases, DPIAs, and transfer tools. HashQuill stores proof and enforces the decision you configured.

Official sources

What HashQuill stores

Each grant or withdrawal is an append-only event: purpose, notice version, jurisdiction, timestamp, content hash. TCF, GPP, and GPC are recorded as inputs, not parallel databases. Enforcement projects the resulting purpose state into downstream systems.

This page is not legal advice and not a substitute for a DPO. Article 6 still has to be right; the ledger cannot invent a lawful basis.

Platform · Governance · Cookie Consent