All news
EDPB / EDPS April 15, 2026 7 min

"We keep it for research purposes": the EDPB explains why that is not an answer

Guidelines 1/2026 on processing personal data for scientific research: 171 paragraphs on broad consent, Article 89 safeguards and — a point few expected — on your retention schedule

In short

Guidelines 1/2026 were adopted in draft on 15 April 2026: 67 pages, 171 paragraphs. They cover the notion of scientific research, legal bases, transparency, data subject rights and the safeguards under Article 89(1). Public consultation closed on 25 June 2026 and the final text will follow the revisions: what you read today is still a draft.

Broad consent exists, but it comes at a price

The knot the research community had been waiting on for years is broad consent: can you ask for consent to research that is not fully defined at the time of collection? The Board's answer is yes, subject to conditions. Consent may cover a clearly described research field, or identifiable expected outcomes, backed by appropriate safeguards. What does not hold up is consent to "research" in general: if the data subject is not told which area the study will move in, the consent is neither specific nor informed.

  • Describe the area, not the word: "paediatric oncology studies", not "scientific purposes"
  • Future processing must be reasonably foreseeable at the time of collection
  • Article 89(1) safeguards are not decoration: minimisation, pseudonymisation where feasible, separation between whoever holds the identifying data and whoever analyses it
  • Consent stays withdrawable: you need a procedure stating what happens to data already fed into an ongoing study
  • If the study changes field you go back to the data subject: broad consent is not perpetual consent

The line that ends up in the record

Here comes the part that matters to whoever fills in the Article 30 record and the retention schedule. The Board is explicit: storing personal data for a generic "scientific research purpose", without indicating the area, is not permissible. The controller must specify the potential research and support it with Article 89 safeguards. Translated into record language: "retained for research purposes" is not a retention period, it is an omission with an elegant formula in front of it.

The check to run on your clients' records

Look for lines where the retention period reads "as long as necessary for research purposes", "for statistical and research purposes" or similar. In most cases they cover archives nobody has opened in years. If there is no defined research area and no Article 89 safeguards, that line does not describe a period: it describes indefinite retention, and in an inspection it reads exactly that way.

What the document does not solve

  • It does not turn research into a legal basis: Article 89 is a safeguards regime, not a standalone lawfulness condition
  • It does not remove the compatibility assessment: the Article 5(1)(b) presumption is not automatic and must be documented
  • It does not touch national law: member state rules on research processing remain in place
  • It is not final: the consultation drew heavy comments from the life sciences sector and the text will change

In DPO Workspace

In the retention matrix, rules with no numeric period have their own type and can stay flagged as pending verification until the source is confirmed. That is the right place to park "for research purposes" lines while the final text is awaited, rather than leaving them written as if they were a period.

The document is long and not all of it serves the corporate DPO. But the broad consent paragraphs and the retention one are the kind of passage that, a year from now, will show up in an enforcement decision introduced by "as clarified by the Board".

Official source:EDPB - Guidelines 1/2026 on processing of personal data for scientific research purposesOfficial source:EDPB - Guidelines 1/2026 (testo integrale, PDF)

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
25the authorities looking at your privacy notice this year, not at your registers

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

On 19 March 2026 the EDPB launched this year's coordinated enforcement action on the transparency and information obligations of Articles 12, 13 and 14 GDPR. Twenty-five authorities are taking part, each free to choose its method: inspections, questionnaires sent to controllers, reading the notices published on websites, sector reviews. National results will be aggregated in the second half of 2026 and the EDPB will publish a summary report with follow-up recommendations. For anyone running compliance the point is that this year the check starts from a text that is already public.

Oct 09, 2026New 7 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