All news
Regulation September 11, 2026 5 min

The 250-employee exemption from the record of processing barely exists

Art. 30(5) exempts small organisations — but only if none of the three carve-outs applies. And one of them applies to any organisation with staff

TL;DR

Art. 30(5) exempts organisations with fewer than 250 employees — unless the processing is likely to result in a risk, OR is not occasional, OR involves special categories or criminal-offence data. The three conditions are alternatives. Payroll is not occasional and contains health data: two of them apply at once.

The mistake is in the word «or»

Art. 30(5) exempts organisations employing fewer than 250 persons «unless the processing it carries out is likely to result in a risk to the rights and freedoms of data subjects, the processing is not occasional, or the processing includes special categories of data as referred to in Article 9(1) or personal data relating to criminal convictions and offences referred to in Article 10». Three conditions, joined by «or». The Art. 29 Working Party made this explicit in its position paper of 19 April 2018: they are alternatives, and a single one of them removes the exemption.

«Not occasional» closes the argument almost every time

Processing is occasional when it is not carried out regularly, is not part of the ordinary course of business and has no settled character. Payroll runs every month. Customer management never stops. Applications arrive all year. None of these is occasional, and the exemption has already fallen, regardless of headcount. Add sick notes and the special-categories carve-out under Art. 9(1) applies as well.

  • The exemption is never total: at most it covers the processing operations that meet none of the three conditions. For all the others the record remains due — so an organisation keeps either a partial one or a complete one.
  • Art. 30(1) lists the minimum content: name and contact details, purposes, categories of data subjects and of data, categories of recipients, third-country transfers with their safeguards, erasure deadlines and a general description of the Art. 32(1) measures.
  • Processors keep their own record too (Art. 30(2)), with different content: it names the controllers they act for, not the purposes.
  • Art. 30(4): the record must be made available to the supervisory authority on request. In practice it is the first document asked for.

What a template does not do

A template gives you the columns, not the content. The two fields where records routinely fail cannot be copied: the retention period, which differs by data category and jurisdiction, and the Art. 32 measures, which must match the technology actually in use. A record that says «statutory retention periods» everywhere does not answer the question — it avoids it.

The practical advice for advisers: do not open the 250 discussion at all. It costs half an hour and always ends the same way. The useful question is which processing operations exist and how long the data stays — because that is where the answer is missing, and that is exactly what the authority asks.

Looking for a workspace for your DPO work?

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

Start free

Related articles

Regulation
nullathe decision on a worker taken by the algorithm alone, from 23 October

A dismissal decided by the algorithm is void: from 23 October in Italy

Published in Official Gazette no. 234 of 8 October 2026 and in force since 23 October, decree no. 179/2026 provides that final decisions on the employment relationship cannot be based solely on automated processing, that the worker may request an understandable explanation, and that decisions taken in breach are void. In parallel, AI systems affecting work organisation enter the risk assessment under Article 28 of decree 81/2008. For a DPO this is the rare case where the consequence is not economic but civil, and it changes how the check is framed.

Oct 08, 2026New 8 min
Regulation
3signals that make notification due

Poland's UODO: not every breach must be notified. Public-register data on one side, PESEL, health and financial data on the other

If an invoicing system leaks only a sole trader's name, business name, tax number and registered address, already public in the business register, risk is normally unlikely. If it also leaks the national ID number, purchase details revealing health, or financial data, notification is due. Either way, the decision goes into the internal register.

Oct 05, 2026New 5 min
Regulation
120days to charge you, not to fine you

The 120 days are not the deadline to fine you: they are the deadline to charge you

Anyone who built an appeal on the authority's delay should re-read the calendar. The Court clarifies three things: the complaint procedure and the sanctioning procedure are autonomous, so overrunning the nine-to-twelve months on the complaint does not extinguish the power to fine; the 120 days are for notifying the charge, not for imposing the fine; and they run from the «definitive finding», which is not the first notice but the moment the authority can assess every element — including the hearing of your side. After the charge, only the five-year limitation period remains.

Sep 20, 2026 7 min