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 October 9, 2026 7 min

The year the authorities read the privacy notice: CEF 2026 on transparency

Twenty-five European authorities are checking Articles 12, 13 and 14 in a coordinated action. The report is coming, and the interesting part is that transparency is the only obligation judged by reading, not by comparing documents

What was launched, and when

On 19 March 2026 the EDPB launched its 2026 coordinated enforcement framework (CEF) action on compliance with the transparency and information obligations of Articles 12, 13 and 14 GDPR. The topic was chosen at the October 2025 plenary, which described the right to be informed as the core of transparency. Twenty-five European authorities have joined. The EDPB does not impose a single method: each authority decides the form — formal inspections, questionnaires sent to controllers, analysis of notices published on websites, reviews of one sector. National results will be aggregated and analysed in the second half of 2026, with a summary report and recommendations.

The reason this action is more uncomfortable than the previous ones has nothing to do with how severe the authorities are. It has to do with transparency being the only obligation in the regulation that is assessed by reading, from the reader's side. A register of processing is judged on the completeness of its fields; a security measure is judged on what it prevents; a privacy notice is judged on whether an ordinary person, having read it, knows what happens to their data. That is a check that needs no visit to the premises: the text is already public, and has been for years.

It is worth keeping the three articles apart, because they are cited together and treated as one. Article 12 is about form: information that is concise, transparent, intelligible, easily accessible, in clear and plain language. Article 13 is about content when you collect the data from the person. Article 14 is about content when the data reaches you from someone else. In practice the first two almost always exist in some form; the third, in the large majority of cases, does not exist at all.

  • «For as long as necessary for the purposes indicated» is not a retention period: it is the question restated as an answer. Article 13(2)(a) asks for the period, or the criteria used to determine it.
  • «Our partners», «selected suppliers», «group companies» are not categories of recipients. A category is recognisable because the reader understands who is meant.
  • The legal basis must be stated for each purpose, not once at the bottom for all of them. When there are five purposes and three bases, the pairing has to be readable.
  • A transfer outside the Union must be declared with the instrument that supports it, and with where to obtain a copy of it.
  • The Article 14 notice must be given within one month of obtaining the data, or at the first communication with the data subject if that comes sooner.

Article 14 is the one that catches people out

Almost every organisation holds data that arrived from third parties, and almost nobody informs those people. Some concrete examples: contact lists bought or exchanged; commercial and credit information on clients and suppliers; employee data received from another company in the group; references supplied by a third party in a recruitment process; records extracted from public registers; the contact details of a named person given to you by the company they work for; the data of a beneficiary provided by whoever signs the contract. In all these cases the data subject has never spoken to you, and that is precisely why the regulation expects you to seek them out: they have a right to know that you exist and that you hold their data.

How to prepare, without waiting for the report. The first exercise is to read your own notice the way a customer would, that is once and reluctantly. The second is to put it next to the register of processing and compare line by line: purposes, bases, recipients, periods, transfers. If the notice declares four purposes and the register lists nine, one of the two is false, and it does not matter which — the inconsistency between the two documents is itself the finding, because it shows that one of them does not describe reality.

On the questionnaire, if one arrives, a note on method. The temptation is to answer by describing the organisation as we would like it to be. It is a mistake that costs twice: the authority compares the answers with the documents, and the divergence between what you wrote in the questionnaire and what is in the register is a finding in its own right, additional to the original one. The useful answer says what exists, what is missing, and by what date it will be closed. The second part is not a weakness: Article 24 asks for measures that are appropriate and kept up to date, not for perfection already achieved.

A note on the calendar, because it determines what is reasonable to do now. The aggregation of national results is expected in the second half of 2026 and the summary report will follow. Waiting for it before moving is the least sensible choice of all: the report will say which defects the authorities found in notices that are already published, which includes yours. Rereading it beforehand costs an afternoon; rereading it after a questionnaire costs the same, with a deadline attached.

Official source:EDPB — Coordinated Enforcement FrameworkOfficial source:Irish Computer Society — EDPB launches its CEF action for 2026 on transparency and information obligationsOfficial source:McCann FitzGerald — Delete and Disclose: EDPB CEF 2025 & 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
13 novlast day to send comments to the consultation

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

On 21 September 2026 the European Data Protection Board adopted Guidelines 04/2026 on the exercise of the power to fine in relation to the other corrective powers, open to public consultation until 13 November 2026. They replace the old Article 29 Working Party guidelines and complete the 2022 ones on calculating the amount. The difference is substantive: those said how much, these say whether. And at the fourth step there is a presumption that shifts the burden of the defence.

Sep 21, 2026New 6 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