Your cookie preferences

EDPB guidance · Art. 7 GDPR

We use technical cookies essential for the platform to work (login, security, sessions). We would also like to use analytics cookies to understand how to improve it.

You can accept all, reject all, or choose which categories to switch on.Your consent is valid for 6 months and you can withdraw it at any time from the footer.

You will find everything in our privacy notice.

All news
EDPB / EDPS September 21, 2026 5 min

EDPB Guidelines 04/2026: five steps to decide whether an authority should fine

Not how much, but whether: fault is a condition, a minor infringement usually leads only to a reprimand, a non-minor one to a strong presumption of a fine. Open for consultation until 13 November 2026

TL;DR

At the plenary announced on 21 September 2026 the EDPB adopted Guidelines 04/2026 on how authorities decide whether to impose an administrative fine, alone or together with the other corrective powers of Article 58(2). Five steps: legal basis for the fine, liable party, intent or negligence, aggravating and mitigating factors, effectiveness and proportionality. Minor infringement: as a rule no fine, possibly a reprimand. Non-minor infringement: strong presumption of a fine. Fourteen practical examples. They replace the 2017 Article 29 Working Party guidelines and complement Guidelines 04/2022 on calculating the amount. Consultation open until 13 November 2026. The same plenary adopted the final version of Guidelines 3/2025 on the interplay between the DSA and the GDPR.

What changes

Guidelines 04/2022 explain how the amount of a fine is calculated. The step before was missing: when an authority must fine and when it may settle for another measure. The new guidelines fill that gap and replace the old Article 29 Working Party document. They also describe each corrective power — warnings, reprimands, orders, limitations and bans, withdrawal of certification — with its purpose and how it combines with a fine.

The five steps

  • LEGAL BASIS. The authority checks that the infringement can lead to a fine, under the GDPR or national law.
  • WHO IS LIABLE. Controller or processor, depending on who is bound by the provision breached: security under Article 32, for example, binds both.
  • INTENT OR NEGLIGENCE. No fault, no fine. This is the line already drawn by the Court of Justice in Deutsche Wohnen (C-807/21, 5 December 2023).
  • AGGRAVATING AND MITIGATING FACTORS. If the infringement is minor, as a rule no fine and at most a reprimand; if it is not minor, there is a strong presumption that a fine should be imposed.
  • EFFECTIVE, PROPORTIONATE, DISSUASIVE. The final check, with room to depart from the standard approach where the case justifies it.

The presumption that matters

The sharpest point is step four. Outside minor infringements, a fine is no longer an option that needs justifying but the rule, departed from only for good reasons. For anyone counting on a first «courtesy» reprimand, the room is shrinking.

Why it matters for small organisations too

The guidelines are meant to align European authorities: the same infringement should get the same response in Rome, Lisbon or Stockholm. For an organisation, this means that what weighs in step four — cooperation, measures already taken, existing documentation, prompt remedies — becomes even more predictable. And that is exactly what is built beforehand, not during an investigation.

What it means for the DPO

Four moves

One: fault is a condition, judged on what the organisation knew and had done. The record of processing, DPIAs, risk analyses and dated procedures are the evidence that negligence is absent or slight. Two: keep a trail of corrective actions with dates and owners, because they count as mitigating factors. Three: a reprimand is not «nothing»: it is a decision that stays on file and weighs as a precedent. Four: anyone wishing to comment has until 13 November 2026. In DPO Workspace, the record diagnosis and the activity history already keep dates, decisions and reasons together.

Looking for a workspace for your DPO work?

DPO Workspace is built by a certified DPO. 30-day free trial.

Start free

Related articles

EDPB / EDPS
EDPBfirst statement on smart glasses

Smart glasses: the EDPB takes a position — users can be controllers, and people being filmed must be able to tell

They look like ordinary glasses, but they have a camera, a microphone and a connection. The EDPB publishes its first statement on smart glasses: when the user becomes a controller, why manufacturers and app providers cannot pass their obligations on to users, and what making a recording visible means in practice.

Oct 13, 2026New 5 min
EDPB / EDPS
25the authorities looking at your privacy notice this year, not at your registers

The year the authorities read the privacy notice: CEF 2026 on transparency

On 19 March 2026 the EDPB launched this year's coordinated enforcement action on the transparency and information obligations of Articles 12, 13 and 14 GDPR. Twenty-five authorities are taking part, each free to choose its method: inspections, questionnaires sent to controllers, reading the notices published on websites, sector reviews. National results will be aggregated in the second half of 2026 and the EDPB will publish a summary report with follow-up recommendations. For anyone running compliance the point is that this year the check starts from a text that is already public.

Oct 09, 2026New 7 min
EDPB / EDPS
13 novlast day to send comments to the consultation

When a fine, and when not: the EDPB writes down the part that was missing

On 21 September 2026 the European Data Protection Board adopted Guidelines 04/2026 on the exercise of the power to fine in relation to the other corrective powers, open to public consultation until 13 November 2026. They replace the old Article 29 Working Party guidelines and complete the 2022 ones on calculating the amount. The difference is substantive: those said how much, these say whether. And at the fourth step there is a presumption that shifts the burden of the defence.

Sep 21, 2026New 6 min