Europe's Privacy Watchdogs Pushed Back on Weaker GDPR: What It Signals
In 2026 the European Commission proposed a Digital Omnibus package that, among other things, would streamline parts of the GDPR and ease how AI providers process personal data. Europe’s own privacy regulators, the European Data Protection Board and the European Data Protection Supervisor, responded with a joint opinion rejecting key parts of the plan. Regulators pushing back on the people who regulate them is a signal worth reading, because it tells you which way the ground is still moving.
What Was Proposed, Briefly
The GDPR-touching parts of the Digital Omnibus floated several changes. The ones that matter for AI include a clearer basis for processing personal data to train and operate AI systems, and procedural simplifications. Secondary coverage also mentioned a possible extension of breach-reporting time and changes to cookie-consent provisions, with the Council’s text reportedly dropping some core consent rules. Treat the specifics as in-flux; the package was still being negotiated. The regulators’ materials are published at edpb.europa.eu, and the GDPR text itself is at gdpr-info.eu.
We set out how the AI Act and GDPR already run in parallel in GDPR and AI Act parallel enforcement.
Why The Pushback Matters To You
The practical signal is that the protections you rely on are contested, not settled. When regulators publicly oppose a loosening, it usually means the final text is uncertain and the direction is not a foregone conclusion. For anyone handling personal data through AI tools, that is a reason to not assume either the strict old rules or the proposed looser ones, and to design for the stricter reading while the dust settles.
It also tells you that “AI training on personal data” is the live battleground, which we cover directly in can AI train on your data under legitimate interest.
What To Do While It Is Unsettled
The sensible posture is caution that costs you little. Keep treating personal and client data in AI tools as if the strict interpretation holds, because if it does you are covered, and if it loosens you have lost nothing. Concretely: know what a tool does with your inputs, prefer tools with clear retention and no-training commitments, and keep the genuinely sensitive material out of third-party systems entirely. The vendor questions are in how to audit an AI vendor in 2026 and questions to ask an AI vendor about data.
Before:
The EU is relaxing GDPR for AI, so we can stop worrying about what we put into these tools.
After:
The EU proposed GDPR changes for AI, but its own privacy regulators rejected key parts, so the final rules are unsettled. We will keep handling personal data under the strict reading until it is resolved, and keep sensitive material out of third-party tools.
The second version treats a proposal under dispute as what it is, not as settled law.
The Move That Does Not Depend On The Outcome
Whichever way the legislation lands, text that never leaves your machine is not personal data you have shared with anyone. For confidential or personal material, drafting locally removes the question of what a provider may or may not do with it, because there is no provider. That is a hedge against an uncertain legal outcome, not a bet on it. We cover it in local AI versus cloud AI for confidential writing.
A Wrivio Context for a privacy-update note could say:
Rewrite this as a neutral, accurate update. Keep every body name, regulation, and date exactly as written. Make clear what is proposed, what is contested, and what is settled. Do not state a proposal as if it were law. Flag anything to confirm with counsel.
Press Ctrl+Shift+Space, paste your draft, and check the diff. A rewrite that keeps “proposed” and “contested” where they belong is doing the work. This is a summary, not legal advice.
Common Questions
What did the EDPB and EDPS say?
They issued a joint opinion in 2026 rejecting key parts of the Commission’s proposed Digital Omnibus changes to the GDPR, including aspects of how the plan would ease data protections. It is an opinion from the EU’s own privacy regulators, not a final decision.
Does this mean GDPR is being weakened?
It means a weakening was proposed and is contested. The regulators’ pushback signals the final text is unsettled, so neither the old strict rules nor the proposed looser ones should be assumed.
What should I do while the rules are in flux?
Handle personal and client data under the strict interpretation, prefer tools with clear retention and no-training terms, and keep genuinely sensitive material out of third-party systems. If it loosens, you have lost nothing.
How does local AI help here?
Text that never leaves your machine is not data you have shared with a provider, so for confidential material local drafting removes the question entirely, regardless of how the legislation lands.
Download Wrivio for Windows to keep personal and confidential drafts on your own machine while the rules are still being argued.
Read Next
Can AI Train on Your Data Under Legitimate Interest? The Proposed GDPR Change
The EU's 2026 Digital Omnibus floated letting AI train on personal data under legitimate interest. What that legal basis means, and what the change would allow.
Is It Safe to Use AI for HR and Personnel Writing?
Performance reviews, warnings, and terminations contain some of the most sensitive data you handle. What is safe to run through AI, and what must stay local.
Subject Access Requests and AI Chat Logs: Are Your Prompts Disclosable?
If staff paste personal data into AI tools, those prompts may fall within a GDPR subject access request. What that means and how to reduce the burden.
How to Ask a Colleague to Cover for You While You Are Out
Asking a coworker to cover your work is a favour, not an assignment. How to size the ask, name the decisions, and say thanks, with a before-and-after example.
This article is filed underPrivacy & Compliance, which has 114 articles.