Back to the blog

The Digital Omnibus: what Brussels proposes for the GDPR and the AI Act

· By Bee Flow · 5 min read

On 19 November 2025 the European Commission proposed changes to the GDPR, the cookie rules and the AI Act. What the two proposals say, what keeps applying until a text is adopted, and what a small company should and should not do yet.

An open rulebook with a loose sheet of tracing paper laid over one page, showing sketched changes, and a pencil beside it

On 19 November 2025 the European Commission presented its digital package. Two of its legislative proposals land on the desk of anyone who handles privacy or compliance: the Digital Omnibus, which amends the GDPR, the ePrivacy Directive and the incident reporting rules, and the Digital Omnibus on AI, which amends the AI Act. According to the press release, both now go to the European Parliament and the Council.

They are proposals. Nothing about what you have to do changes today, and the text can still move a long way in negotiation. This article is a reading guide to the Commission's texts, not legal advice.

What the Commission proposes for the GDPR

We read the proposed articles themselves. These are the points that matter most to a small or mid-sized organisation.

  • The definition of personal data becomes relative. Under the proposed Article 4(1), information is not personal data for a given party if that party cannot identify the person with the means it can reasonably use.
  • A new Article 88c says that processing personal data to develop and operate an AI system or AI model can rely on legitimate interest. It comes with safeguards, such as data minimisation when selecting sources and training, and an unconditional right to object. Special category data that ends up in training data anyway must in principle be removed.
  • A controller may refuse an access request, or charge a reasonable fee, when the request is used for purposes other than protecting the person's own data. The controller still has to show that the request is unfounded or excessive.
  • A data breach would only be notified to the supervisory authority when it is likely to result in a high risk, without undue delay and where feasible within 96 hours, through a single EU entry point. Until that entry point exists, you notify the authority directly.
  • National DPIA lists would give way to a single EU list of processing that does and does not need a DPIA, proposed by the EDPB. The national lists stay valid until the Commission adopts the EU one.
  • The cookie rule moves into the GDPR, as a new Article 88a. Refusing must take one click, and after a refusal you may not ask again for the same purpose for at least six months. Audience measurement for your own use gets an exemption. Later, websites would also have to respect choices sent automatically, for example by the browser.

The press release says the core of the GDPR and its high level of protection remain intact.

What the Commission proposes for the AI Act

Under the current text, the rules for high-risk AI systems apply from 2 August 2026 and 2 August 2027. The AI proposal ties those dates to the availability of standards and other support tools. Once the Commission confirms by decision that they are in place, the rules start six months later for the uses in Annex III, such as AI in recruitment, and twelve months later for the products in Annex I. Without such a decision, they apply on 2 December 2027 and 2 August 2028 at the latest.

The AI literacy duty in Article 4 changes in kind. Today, providers and deployers of AI systems must ensure a sufficient level of AI literacy among their staff. In the proposal, the Commission and the Member States would encourage organisations to do so. The training duty for deployers of high-risk AI systems stays.

What applies until a text is adopted

All of the current rules. Until a text is adopted, published and in application, you work with the law as it stands.

  • A breach that poses a risk to individuals is notified to the supervisor, in the Netherlands the Autoriteit Persoonsgegevens, within 72 hours.
  • Whether you need a DPIA follows from Article 35 of the GDPR as it reads now.
  • The AI literacy duty in Article 4 of the AI Act has applied since 2 February 2025. It covers deployers, the organisations that use AI systems at work, so also a company whose staff only use an AI chat.
  • Your cookie banner and consent flow stay as they are.
  • If you use AI for something listed in Annex III, plan for 2 August 2026 for now.

What to do now, and what not yet

What we would do now:

  • Keep your breach procedure at 72 hours. The proposal also keeps the duty to record every breach internally, so that register stays in any case.
  • Carry on with AI literacy. It is required today, and a team that knows what not to paste into an AI chat is useful under any version of the law.
  • Map which AI tools process personal data, on what legal basis and where. The proposed Article 88c still asks for a balancing test and safeguards.
  • If a vendor wants to train on your data and points to Article 88c, ask how it weighed the interests under the current rules. Article 88c is not law yet.

What we would not do yet:

  • Treat pseudonymised data as anonymous on the strength of this proposal.
  • Refuse access requests by pointing to the new abuse ground. It does not exist yet.
  • Remove the cookie banner or change your analytics settings.
  • Push back high-risk AI planning on the expectation that the delay will come.

We would not change any procedure until there is a final text.

Where Bee Flow helps

Whatever text comes out, accountability starts with knowing which personal data goes into which AI tool and where that tool runs. Bee Flow is an AI workspace you can run on your own server, where you choose which language model answers, including a model hosted in the EU or on your own hardware. Messages are checked for personal data before they reach a model. That makes the overview you need to build anyway a good deal simpler. See our privacy and security page for how it works, or get in touch if you want to look at it for your own organisation.

#privacy #compliance