Privacy & GDPR

EDPB Fining Guidelines: Why a GDPR Fine Is Now the Default

The EDPB fining guidelines 04/2026 set a five-step test: minor breaches get a reprimand, anything else a strong presumption of a GDPR fine. What it means.

By Jasper Koers Published 7 min read

On this page
  1. What the EDPB adopted in September 2026
  2. The five-step method
  3. Reprimand vs fine: the factors that tip the balance
  4. Why "we will fix it after a warning" no longer works
  5. What it means for cookies and analytics
  6. Where ClearAnalytics fits

At its September 2026 plenary, the European Data Protection Board adopted Guidelines 04/2026 on the application of the power to impose administrative fines, the new EDPB fining guidelines. The document is dated 17 September and was announced on 21 September. It gives Europe's data protection authorities a common five-step method for deciding whether a GDPR infringement should lead to a fine, rather than a reprimand, an order or nothing at all.

The core message is simple. If an infringement is minor, the general rule is no fine and possibly a reprimand. If it is not minor, there is "a strong presumption" that a fine follows. For any organisation that has quietly relied on "we will fix it once the regulator complains", that is the part to read. The guidelines are open for public consultation until 13 November 2026.

Not legal advice. This article summarises a draft EDPB document for general information. Talk to your DPO or a lawyer about your own situation.

What the EDPB adopted in September 2026

The Guidelines 04/2026 are addressed to supervisory authorities, but they tell everyone else how those authorities are expected to reason. They:

  • replace the Article 29 Working Party guidelines on administrative fines (WP253), which the EDPB had endorsed;
  • complement the EDPB's Guidelines 04/2022 on the calculation of fines, which deal with how much to fine once the decision to fine is made;
  • describe each corrective power in Article 58(2) GDPR: warnings, reprimands, orders, limitations and bans, and withdrawal of certification;
  • include 14 practical examples, from an unanswered access request to a social media tracking pixel.

The EDPB says it needed new guidance because authorities have gained experience since 2018 and because the Court of Justice has clarified the conditions for fines in several rulings. At the same plenary, the Board also adopted the final version of its guidelines on the interplay between the Digital Services Act and the GDPR.

The five-step method

The EDPB splits the decision into legal preconditions (steps 1 to 3) and the actual choice of measure (steps 4 and 5).

Step Question the authority asks What it means for you
1 Can this infringement lead to a fine at all? Most GDPR obligations are listed in Article 83(4) to (6), so the answer is usually yes.
2 Can this party be fined for it? Liability follows whoever is bound by the breached provision: controller, processor or both.
3 Was it intentional or negligent? A fine requires culpability, but the bar for negligence is very low.
4 Do the Article 83(2) factors show a minor infringement? Minor: as a rule, no fine. Not minor: a strong presumption of a fine.
5 Would a fine be effective, proportionate and dissuasive? The authority can still deviate from the default in either direction, with reasons.

Step 3: negligence is almost always there

The guidelines spend several pages on culpability. Negligence does not require that you knew you were breaking the law, only that you were "in a position to know". Organisations are expected to inform themselves about the rules that apply to them. Citing an Advocate General's opinion, the EDPB says the threshold for negligence is so low that it is hard to imagine it not being met. Good faith "can only be invoked in very exceptional circumstances", and where EDPB guidelines on a topic exist, an error about the law is always considered avoidable. The examples show that even a contrary legal opinion from a lawyer does not remove negligence.

Step 4: what makes an infringement "minor"

An authority may treat an infringement as minor when it does not pose a significant risk to the people concerned and does not affect the essence of the obligation. To decide, it weighs the factors in Article 83(2) GDPR. The guidelines are unusually concrete about which way each factor pushes.

Reprimand vs fine: the factors that tip the balance

Factor (Art. 83(2)) Pushes toward a fine Pushes toward a reprimand
Nature, gravity, duration Monitoring or profiling, many people affected, systemic, long-running One person, limited scope, short duration
Intent or negligence Intent, or a high degree of negligence A low degree of negligence
Mitigation Measures taken only after the investigation is known Measures taken spontaneously, before the investigation
Responsibility Weak technical and organisational measures Going "above and beyond" (only in exceptional cases)
Previous infringements Any relevant earlier infringement, especially the same one Absence of earlier infringements is not mitigating
Cooperation Not cooperating Only cooperation beyond what the law requires counts
Categories of data Special categories, location data, financial data Non-sensitive or hashed data
How it became known Complaint or investigation is neutral Reporting it yourself before the authority knew
Earlier orders Not complying with them Complying is mandatory, so it adds nothing
Other circumstances Profit made or losses avoided through the infringement Exceptional circumstances

Two points stand out. First, profit from the infringement is called a strong indication that the infringement is not minor, because a reprimand cannot take that gain away. Second, repetition turns minor into not minor: in two of the examples, an authority first issues a reprimand, receives more complaints about the same problem, and then fines.

Why "we will fix it after a warning" no longer works

Many website owners treat enforcement as a three-stage process: a complaint, a letter, then a fix. The guidelines undermine that assumption in four ways:

  1. A GDPR "warning" is not a first strike. Under Article 58(2)(a), a warning is for processing that is likely to infringe the GDPR but has not yet happened. Once an infringement has occurred, the warning is off the table.
  2. Late fixes count for less. Measures taken before an investigation becomes known are "more likely to be considered a mitigating factor" than measures taken afterwards.
  3. Cooperation is expected, not rewarded. Cooperating with the authority is a legal duty under Article 31, so ordinary cooperation does not reduce the risk of a fine.
  4. Not minor means a fine by default. The authority has to find reasons not to fine, rather than reasons to fine.

There is still room for proportionality. The EDPB accepts that an authority can refrain from any measure when a controller ended an infringement as soon as it became aware of it, as in one example where an SME corrected its privacy notice before an investigation started. But that path depends on acting first.

What it means for cookies and analytics

The guidelines cover fines under the GDPR. In many countries, the consent rule for cookies and similar trackers comes from national ePrivacy law, which may have its own sanction rules (France's CNIL, for example, has its own simplified sanction procedure). The data your analytics and marketing tags collect, however, is GDPR territory: lawful basis, transparency, security and transfers.

One example is directly relevant. An SME used a social media tracking pixel on a web page, and a setting in the platform's developer tool overrode its own data protection settings. Hashed email addresses and phone numbers of about 50,000 users went to the platform over two years. The authority found a breach of Article 32 but treated it as minor and issued a reprimand, because the data was hashed, contained nothing sensitive and other safeguards limited the collection. Change those facts, such as unhashed data, sensitive pages or a repeat, and the same case would land on the fine side of the table.

Practical steps that follow from the method:

  • Find problems before a complainant does. Audit which tags run on which pages and what they send. Our GDPR analytics checklist lists the questions to ask.
  • Fix and document immediately. Timeliness is an explicit factor, and the guidelines expect documentation of when and how measures were taken.
  • Collect less. The amount of data per person and its sensitivity weigh on the decision. Data you never collect cannot be part of an infringement.
  • Expect publication. In some countries sanctions become public, as in the Netherlands from September 2026 (more here), so a reprimand has a reputational cost as well.

For the full picture of what web analytics must do under the GDPR, see our complete guide.

Where ClearAnalytics fits

The cheapest infringement is one your analytics cannot commit. ClearAnalytics sets no cookies, stores nothing on the visitor's device and does not store IP addresses; unique visitors are counted with a hash that rotates daily. Data stays in the EU and is never shared with third parties or used for advertising. That keeps the analytics part of your stack small and easy to explain to a DPO. You can see the plans, including the free tier.

Frequently asked questions

What are the EDPB fining guidelines 04/2026?

Guidelines 04/2026 explain how European data protection authorities should decide whether to impose a GDPR fine, instead of or in addition to measures such as reprimands and orders. They set out a five-step method and include 14 worked examples. They were adopted for public consultation on 17 September 2026.

What is the difference between a reprimand and a fine under the GDPR?

A reprimand is a formal finding that you broke the GDPR, without a financial penalty. A fine has a punitive purpose and is meant to deter. Under the new EDPB guidelines, minor infringements generally get a reprimand, and other infringements are presumed to deserve a fine.

Can I avoid a GDPR fine by fixing the problem after a warning?

Not reliably. Under the GDPR a warning only concerns processing that has not happened yet. Once an infringement has occurred, fixing it after an investigation is known counts for less than fixing it beforehand, and if the infringement is not minor there is a strong presumption of a fine.

How do the new guidelines relate to EDPB Guidelines 04/2022?

Guidelines 04/2022 explain how to calculate the amount of a GDPR fine. The new Guidelines 04/2026 cover the earlier question of whether to fine at all, and they replace the Article 29 Working Party guidelines on that subject.

When can I comment on the EDPB fining guidelines?

The EDPB's public consultation on Guidelines 04/2026 runs until 13 November 2026.

  • gdpr
  • gdpr-fines
  • edpb
  • enforcement
  • compliance

Back to blog Read as markdown

Enjoyed this article?

Try ClearAnalytics for free and get privacy-first analytics for your website.