Summary

  • Article 33 gives the regulator a figure: 72 hours from the moment the controller becomes aware, qualified by "where feasible" and backed by a duty to explain any delay.
  • Article 34 gives the people whose data leaked a duty with no figure in it, a higher threshold, and three exceptions the controller decides about its own conduct.

On 2 October 2019 a privately practising doctor in France learned that patient data in his care had been compromised. On 24 September 2020, the day the sanction report was notified, he still had not told the Commission nationale de l'informatique et des libertés anything. The restricted formation set out both dates in Délibération SAN-2020-015 of 7 December 2020, recorded the same finding in an independent reproduction of the decision, held that an Article 33 breach was constituted, and priced the security and notification failures together at €6,000 for breaches of Articles 32 and 33 of Regulation (EU) 2016/679. The published text does not identify him.

Two dates, and a duty that had not moved for 358 days. That is roughly 11.8 months, and about 119 times the figure the article prints as its ceiling. The number is real, the interval is real, and this is the file most often carried around as proof that Europe's breach clock bites.

Then read the rest of the instrument, because the doctor's case only ever exercises one half of it.

Article 33(1) is the half with the number. It requires notification to the competent supervisory authority "without undue delay and, where feasible, not later than 72 hours after having become aware of it", unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons; where the notification comes later than 72 hours, it "shall be accompanied by reasons for the delay" (full text, corroborated against the retained text on legislation.gov.uk). Round the same article: processors must tell controllers without undue delay; the notification must carry the nature of the breach and the approximate numbers of people and records, a contact point, the likely consequences and the measures taken or proposed; information may be supplied in phases without undue further delay; and every breach must be documented — facts, effects, remedial action — so that the authority can verify compliance.

Article 34 is the other half, and it opens without a number. Where a breach "is likely to result in a high risk", the controller communicates it to the data subject "without undue delay" — and the paragraph stops there (full text, again checkable against the retained version). No hours, no days. Article 34(2) fixes the register: clear and plain language, and at least the contact point, the consequences and the measures that Article 33(3)(b), (c) and (d) require. Article 34(3) then removes the duty in three situations — measures that render the data unintelligible, encryption being the named example; subsequent measures ensuring the high risk is no longer likely to materialise; and disproportionate effort, replaced by public communication or a similar measure of the controller's own choosing.

Three exceptions, and all three are determinations the controller makes about its own conduct. The one place where someone else can see something sits in Article 34(4): where the controller has not already communicated, the supervisory authority, having weighed the likelihood of high risk, "may require" communication or "may decide" that an exception applies. That is a genuine counterweight and it belongs in the open rather than in a footnote — the subject limb is not wholly self-judged.

It is discretionary, it runs through the authority rather than through the person affected, and nothing in the record reviewed below shows it being used.

A word on what I read. The Official Journal text itself was not opened for this piece: the EUR-Lex publication page establishes the instrument, OJ L 119, 4 May 2016, pages 1 to 88, CELEX 32016R0679, and nothing more. The operative wording above comes from two full-text reproductions, cross-read against the UK retained version, which diverges from the EU instrument in Article 34(4) by naming the Commission where the EU text names the supervisory authority. Where the readings agree the wording is corroborated, not authenticated, and a reader who needs the enrolled text should go to the Journal.

The CNIL reads the two limbs as two duties, and its own breach-notification guidance says so in as many words. Notification to the CNIL is due dans les meilleurs délais and, si possible, within 72 hours of awareness; a notification past that mark must explain the delay; and where the breach is likely to result in a high risk, the controller must also inform the people concerned — the obligations attributed to Articles 33 and 34 respectively. The guidance attaches no hour figure to the second duty, because the article contains none to attach.

So the fair reading of the numbered limb is not a stopwatch either. It is a qualified ceiling plus a duty to explain, and the doctor's file is a case of total failure rather than of lateness: nobody argued about a few hours, because there had been no notification at all for the better part of a year. The distinction matters, because a programme built to hit hour 71 has satisfied the arithmetic and not necessarily the duty.

Then the appeal, which is the part of the story usually left out. On 22 July 2022 the Conseil d'État, in decision n° 449694, quashed an Article 33 finding against a doctor in a companion decision: because the CNIL itself had informed the controller of the breach and opened a control on that basis, he did not fall within the field of the notification duty at all, and the deliberation was vitiated by an error of law. The fine went from €3,000 to €2,500. The ruling does not say the controller was quick enough; it removes the trigger rather than satisfying it. One detail resists a tidy narrative: the judgment describes the challenged deliberation as 3 December 2020 in its narrative and as 7 December 2020 in its operative part, and which of the two doctor decisions from that date it reformed cannot be settled from its text. This article therefore says only that the reformed decision is the €3,000 companion, and asserts nothing about SAN-2020-015.

The second readable administrative application of Article 33 is not about hours at all. In Délibération SAN-2022-022 of 30 November 2022, the restricted formation found the documentation duty breached, holding at point 76 that the file produced after two days of on-site inspection did not allow the delegation to know the full set of measures taken to remedy the breach and its effects. The fine was €300,000, for breaches of Articles 12, 15, 17, 32 and 33. Three figures, three separate stages: €6,000 for Articles 32 and 33 in 2020; €3,000 cut to €2,500 in the reformed companion; €300,000 across five articles in 2022. No figure in that set is attributable to a failure to tell the people affected.

French criminal law, by contrast, does not rank the limbs at all. The CNIL's own page on criminal penalties sets out Article 226-17-1 of the Criminal Code: failing to notify a breach to the CNIL or to the person concerned, in breach of Articles 33 and 34, is punishable by five years' imprisonment and a €300,000 fine. Identical maxima for the limb with the number and the limb without one.

What the record does not show has to be said as carefully as what it does. Across the thirteen sources read on 19 November 2026 — the EUR-Lex publication page and four full-text readings of Articles 33 and 34, the CNIL's breach-notification guidance, its published sanctions table, its criminal-penalty page, the two reproductions of SAN-2020-015, the Conseil d'État judgment, SAN-2022-022, and the Article 29 Working Party guidance hosted by the CNIL — no CNIL decision finding a breach of Article 34 was located, the extracted passages of SAN-2020-015 contain no Article 34 finding, no published aggregate count of breach notifications received by the CNIL was located, and no published decision was found in which the authority exercised its Article 34(4) power. That guidance renders Article 34(1) as dans les meilleurs délais and states plainly that the threshold for telling individuals is higher than the threshold for telling the authority. None of this is a finding that the subject limb goes unenforced. It is a finding about what a stranger can read.

BTW's own prior coverage of this ground was checked the same day with two literal queries, "CNIL" and "GDPR", which returned five published rows. The nearest neighbour is a 17 November 2026 briefing on the CNIL's separate penalty-payment clock; the others are a 10 October 2026 briefing on the EDPB's draft tests for calibrating GDPR penalties, an 18 October 2026 briefing on the EDPB's opinion on the CNIL's Michelin binding-corporate-rules draft, and two August 2025 signal briefings on the Bouygues Telecom breach in which the CNIL appears only as the authority notified.

None of them reads Articles 33 and 34 as two limbs carrying different kinds of obligation, and none reads a published decision against either limb. That is the delta this piece is meant to hold.

Here is the asymmetry in one sentence: the limb addressed to the authority carries a number and a reasons field; the limb addressed to the person carries neither, and its three exits are authored by the party that benefits from them. Nothing about that is unlawful, and nothing here alleges that any controller has exploited it. It is a design fact with an operational consequence, and the consequence is checkable. A record of the controller's own reasons for a late notification exists because Article 33(1) demands one. No equivalent sentence demands a reason for a late communication to the people affected.

Both clocks start from the regulated party's own determination: awareness on one side, the likelihood of high risk on the other. The two numbers cannot be converted into each other, and there is no honest way to rank the limbs. What can be said is what would change the picture — a published decision in which the authority applies Article 34 and states why it did; a direction under Article 34(4) that someone outside the case can read; or a row coded to Article 34 in the authority's own table, which today is where you go to read about the other limb. Until one of those exists, the record has a number on one side, and on the other a verb.