A Clean Record Is Not a Defence

The EDPB wants regulators to fine by default for any GDPR breach that is not minor. A clean past and a legal opinion won't help. Your records will.

PublishedReading time: 7 min read

Golden justice scales on a desk beside a laptop, symbolizing law and balance.

The European Data Protection Board wants regulators to fine by default for any GDPR infringement that is not minor. Under draft Guidelines 04/2026, a spotless history, routine cooperation and a lawyer's opinion will not, on their own, protect you. What counts is what you did before the regulator called, and whether you can prove it.

The letter from the data protection authority (in Czechia, the Office for Personal Data Protection, ÚOOÚ) concerns one complaint: a former customer waited six weeks for a reply to an access request. The managing director's defence: we have never had a problem, we will cooperate fully, and our lawyer approved the process years ago. Surely the worst case is a reprimand.

On 17 September 2026 the European Data Protection Board (EDPB) adopted draft guidelines under which none of those arguments works by itself.

What the EDPB Is Proposing

Guidelines 04/2026 ask the question that precedes any calculation: should the authority fine at all, or will a reprimand or another corrective measure do? Guidelines 04/2022 covered how to calculate a fine. The new draft sets out five steps:

  1. Can the infringement be fined under the GDPR or national law?
  2. Who is liable for it?
  3. Was it committed intentionally or negligently?
  4. Do the factors in Article 83(2) GDPR point to a minor infringement?
  5. Would a fine be effective, proportionate and dissuasive in this case?

Step four decides the outcome. If the infringement is minor within the meaning of Recital 148 of the GDPR, the authority will, as a general rule, not fine and may issue a reprimand instead. If it is not minor, the draft says there is a "strong presumption" of a fine. Step five allows a departure either way, but the starting point is clear.

This is still a draft: the public consultation runs until 13 November 2026 and the text may change. EDPB guidelines are not legally binding, but they exist to align supervisory authorities across the EU, and every national authority, the Czech ÚOOÚ included, sits on the Board. For a business, it is the best guide to how the regulator will think.

Three Arguments That Will Not Carry the Day

"We Have Never Done Anything Wrong"

Under Article 83(2)(e) GDPR, previous infringements are an aggravating factor. The reverse does not hold. Paragraph 88 of the draft states that the mere absence of previous infringements cannot in itself be a mitigating factor, because compliance with the GDPR is the norm. A clean record earns you nothing.

"We Are Cooperating Fully"

Cooperating with the authority is a duty under Article 31 GDPR, so the EDPB does not treat it as mitigation. Only cooperation beyond what the law requires can count, for example where it prevents harm to the people affected.

Reporting is similar: disclosing an infringement yourself, before the authority learns of it otherwise, can help. A breach notification under Article 33 GDPR is already required by law, so the draft treats it as neutral.

"Our Lawyer Signed It Off"

A fine requires fault, but the EDPB sets the bar for negligence low: the question is whether the company could have recognised that its conduct was unlawful, not whether it actually did. The draft gives three examples:

  • An external opinion against the prevailing view. A company relies on a lawyer's opinion that contradicts most of the legal literature. Because the opinion itself mentions the opposing view, the company knew the risk and is not exculpated.
  • An internal analysis against the regulator's known position. The in-house legal team finds the processing lawful although the authority has said the opposite. That is still negligence.
  • Advice that cannot be produced. A company says it took external advice on its privacy notice but cannot show the authority what the advice said or what it was based on. The argument has no effect.

Advice is only as good as the record behind it, a point we also made about legal process in A Subpoena Is Not a Permission Slip. If you rely on a legal view, keep it in writing, dated, with the material your adviser worked from.

A company also answers for an employee's infringements on the job, even if the employee broke an internal policy or management did not know. And a processor's conduct is generally attributed to the controller, unless the processor acted wholly outside its instructions, for its own purposes.

What Works in Your Favour

The draft also describes cases ending without a fine, and they show what helps.

When you fixed it. Under paragraph 74, measures a company takes on its own initiative, before it learns of an investigation, are more likely to count as mitigating than measures taken afterwards. "We fixed it in March" and "we fixed it after the regulator's letter" can separate a reprimand from a fine.

Proof of what you did and when. Under paragraph 78, the authority should consider the documentation the company provides: when measures were taken, how they were implemented, and whether the processor or the Data Protection Officer was involved. What you never wrote down is hard to prove later.

Scope, duration and impact. Short, small-scale breaches without sensitive data sit closer to minor. The draft cites a small company whose access request landed in a spam folder. It received only a reprimand, partly because it apologised to the requester in writing and dealt with the request as soon as the authority got in touch.

Where a Minor Slip Becomes a Fine

The most useful examples show a minor infringement ceasing to be minor. Each involves repetition.

A small telecoms operator answered a request for information a month late, without warning the requester. The authority first considered a reprimand, then found further identical cases and opened fining proceedings: one delay may be minor, a pattern of delays points to a systemic problem.

A recruitment agency had an erasure procedure and had briefed its recruiters. Two complaints brought a reprimand. Three more identical complaints brought a fine. The procedure existed on paper, but in practice it kept failing through human error.

The draft adds one more signal: an earlier infringement in a different area can still count if it shares the same cause, typically ignoring the Data Protection Officer's advice.

The authority is not asking whether you have a policy, but whether it works every time and whether you can show it.

How to Do This Without Another Binder

Most mid-sized companies split GDPR across a shared inbox, a deadline spreadsheet, a policy folder and a training tool. It works until someone asks exactly when something happened.

In the GDPR and data protection module of the VPoint platform, data subject requests, records of processing and security incidents run in one place. Statutory deadlines are tracked automatically and every step leaves an audit trail, so "when did you find out and what did you do" is answered with an export, not a reconstruction. Training drafted by AI from your own policies leaves a dated acknowledgement for every employee: the evidence that separates a working procedure from one on paper. And because the same platform covers whistleblowing, internal policies and a trust centre, you do not need a separate tool for each obligation.

Summary: What to Check Before Year End

  • For every data subject request in the past year, can you show when it arrived, when you replied and who handled it?
  • Does the same error keep recurring, such as late replies or unactioned erasures? Fix the cause, not the individual case.
  • Are the legal opinions you rely on in writing, dated and backed by the underlying material?
  • Do you have contracts with your processors and records of checking them?
  • Can you prove that staff completed training on a specific policy, and when?
  • Do you record your Data Protection Officer's recommendations and what you did with them?
  • When you find a problem yourself, do you fix and log it straight away, not after the regulator writes?

If the answer to two or more of these is "not sure", book a 30-minute demo. We will show you an audit pack built from day-to-day operations, showing what you did and when, for a single annual price per organisation with no per-user fees.