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 6 min

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

Guidelines 04/2026 do not say what an infringement costs: they say WHETHER it ends in a fine. Five steps, fourteen examples, and a presumption that turns the defence of a client upside down

What was adopted

At the plenary announced on 21 September 2026 the EDPB adopted two documents. The first are Guidelines 04/2026 on the application of the power to impose administrative fines in relation to other corrective powers: they remain open to public consultation until 13 November 2026. The second is the final version of the guidelines on the interplay between the Digital Services Act and the GDPR, closed after consultation. Guidelines 04/2026 replace the Article 29 Working Party guidelines on the application and setting of fines and sit alongside Guidelines 04/2022, which concern calculating the amount.

The distinction between the two documents is the one thing to grasp properly. The 2022 guidelines answer the question «how much»: you start from seriousness, you find a starting point, you apply the factors of Article 83(2), you look at turnover. Guidelines 04/2026 answer a question that came earlier and that nobody had ever written down in an orderly way: «do we reach a fine at all, and why not a reprimand, an order or a limitation». Until yesterday that part was practice, which is to say it varied from one authority to the next.

The method runs in five steps, read in sequence: each one can close the matter before the next.

  • First: the authority checks that the alleged infringement can lead to a fine at all, finding support either in the GDPR or in national law.
  • Second: it checks that the party under investigation can be the addressee. Whether the controller or the processor answers depends on who is bound by the provision breached.
  • Third: it assesses whether the infringement was committed intentionally or negligently. Culpability is a condition of the fine, not a discount factor.
  • Fourth: it weighs aggravating and mitigating circumstances. If the infringement is minor, as a rule there is no fine and a reprimand is used; if it is not minor, there is a strong presumption that a fine should be imposed.
  • Fifth: it checks that the fine is effective, proportionate and dissuasive in the specific case, and whether there is reason to depart from the standard approach.

The fourth step changes how you defend a client

«Strong presumption that a fine should be imposed» is not a turn of phrase: it reverses the starting point. Until now the discussion with the authority turned on «nothing serious happened, a warning would have done». With this approach that sentence is no longer enough, because the presumption works against you: you have to show that the infringement IS minor, not hope the authority treats it as such. And «minor» is a qualification resting on documented facts — duration, number of data subjects, categories of data, actual harm, remedy applied — not on a general assessment of good faith.

The third step deserves the same attention, for the opposite reason. Culpability is presented as a condition: without intent or negligence no fine is imposed. That looks like good news for the controller, and in part it is, but it immediately turns into a practical burden. Being without fault is not asserted, it is shown: with the date a risk was spotted, the opinion the DPO gave, the decision taken by the body entitled to take it, the action carried out. An organisation that keeps no trace of these things has no way to tell itself apart from a negligent one, because from the outside the two look very much alike.

The most useful part of the document, for people who do the work, are the fourteen practical examples: cases built to show how an authority chooses between a reprimand, an order, a limitation, a ban, withdrawal of certification and a fine, and when it combines them. That material is worth more than many pages of principle, because it makes the boundary between situations readable.

One last thing, and it has a deadline. The text is open to public consultation until 13 November 2026: anyone can send comments, not only trade associations. For a practice with clients in several Member States it is a concrete opportunity, because the very unevenness between national authorities is the problem these guidelines say they want to close.

Official source:EDPB — EDPB harmonises fining methodology and adopts final DSA-GDPR guidelines (21/09/2026)Official source:EDPB — Guidelines 04/2026 on the application of the power to impose administrative fines in relation to other corrective powersOfficial source:EDPB — Consultazione pubblica aperta fino al 13 novembre 2026

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
5steps to decide whether to fine

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

The European Board has adopted guidelines on when a supervisory authority should impose an administrative fine and when it can stop at a reprimand, an order or a ban. Five steps, fourteen examples, and a clear rule: if the infringement is not minor, a fine is the norm.

Sep 21, 2026New 5 min