All news
Regulation September 6, 2026 6 min

Three rules almost no Italian register contains

Email metadata, the cancer right to be forgotten, and the reasoning behind a suspicious-transaction report that was never sent: three live obligations missing from Art. 30 registers

TL;DR

Twenty-one indicative days on employee email metadata; the ban on asking about cancer treated more than ten years ago; the duty to keep the reasoning behind an AML report you decided NOT to file. Three register entries almost nobody writes.

One: email metadata, configured by your provider

The Italian DPA's guidance document of 6 June 2024 indicates twenty-one days as an orientative retention period for the metadata generated by email management software — sender, recipient, date, time, size. Not content: logs. It is the rule a controller most often breaches without knowing, because the breach is the default setting of the suite they bought: many keep logs for months or years, nobody chose that, and precisely for that reason nobody entered it in the register. Going beyond twenty-one days is not banned outright — the document is guidance, and documented technical needs can justify it — but Art. 4 of the Workers' Statute still applies where retention enables remote monitoring.

Two: the cancer right to be forgotten is not a retention period, it is a collection ban

Law 193 of 7 December 2023 prohibits asking about oncological conditions whose active treatment ended, without recurrence, more than ten years ago; five years if the illness arose before the age of twenty-one. It covers banking, financial and insurance contracts, adoption and public competitions. A questionnaire asking «have you ever had cancer» with no time limit is unlawful upstream, and no retention period makes it lawful. The ministerial decree of 22 March 2024 then identifies conditions for which the right matures earlier than ten years: applying the general period to all of them is still a breach, by default.

Three: the file of the report you did NOT send

Art. 35 of Legislative Decree 231/2007 requires suspicious transaction reports. What registers leave out is the other half: the analysis preceding the decision, and the reasoning for internal filing when no report goes out. That file holds a judgment on an identified person — a suspicion assessed and set aside — and it is more sensitive than the report itself, because it stays internal and is not covered by the confidentiality the law grants to a report that was sent. Who can open it, and for how long it stays, has to be written down.

  • What they share: none of the three arises from a decision to collect data. The logs are already there, the questionnaire predates the statute, the file is the residue of a negative decision.
  • What happens under review: these are real archives the register does not describe, and their absence is not a formal oversight — it means nobody set a period, and therefore nobody deletes.
  • Where to start: ask your email provider how long it keeps logs, re-read your health questionnaires, open the drawer of filed AML assessments.

The common thread

A record of processing describes what an organisation decided to do. These three archives exist without anyone deciding on them: they were created by a default setting, an inherited form, a procedure that produces paper even when it ends in a no. That is where the register ages — not in the activities somebody designed.

All three are now in the Italian retention matrix, with the source cited and the verification status declared entry by entry.

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