Regulatory Intelligence · · 14 min read

Digital Omnibus on Data: What the Council Changed in the GDPR, Cookie Rules and AI Provisions

Digital Omnibus on Data: What the Council Changed in the GDPR, Cookie Rules and AI Provisions

Key takeaways

  • The Digital Omnibus on data amends the GDPR, the ePrivacy Directive, the Data Act and NIS2 in a single package. The Commission proposed it in November 2025.
  • The Council agreed its mandate on 21 October 2026 (Council document ST 14756/26). It keeps the overall aim of lighter obligations but drops or narrows the most ambitious changes.
  • The definition of personal data stays as it is. Pseudonymised data gets a new Art. 25a instead.
  • Cookie rules stay in the ePrivacy Directive, the rule on browser signals is deleted, and the pause before a site may ask for consent again after a refusal is cut from six months to four.
  • Companies can still rely on legitimate interest to develop and operate AI (new Art. 88 bis), but with general rather than detailed safeguards.
  • Parliament hasn't adopted its position yet, and its committee vote isn't expected before early 2027. Until a final text is adopted, the current rules apply unchanged.

What is the Digital Omnibus on data?

The Digital Omnibus on data is an EU simplification package that amends mainly the GDPR, the ePrivacy Directive, the Data Act and NIS2 in a single legislative act. The Commission presented it in November 2025 [proposal reference COM(2025) xxx] to reduce the administrative burden on businesses and support competitiveness, estimating savings of at least €5 billion by 2029.

It was tabled alongside a separate proposal to simplify the AI Act, COM(2025) 836. To meet the AI Act's 2 August 2026 application date, that part was fast-tracked through the AI Omnibus and has since been adopted as Regulation (EU) 2026/1744, as discussed in [our previous article]. The data part faces no such deadline, and its subject matter is politically sensitive, which explains its slower progress.

Where does the Digital Omnibus stand now?

The Council has agreed its position, but the European Parliament hasn't, so the final text is still open.

In the Council, where national governments negotiate, the Cyprus Presidency produced several drafts in the first half of 2026 before passing the file to Ireland on 1 July. The Irish Presidency's compromise was finalised in a mandate agreed on 21 October 2026 and published as Council document ST 14756/26. It differs from the Commission's proposal in several respects.

Parliament's committee vote is not expected before early 2027, and trilogue negotiations between Parliament, Council and Commission can only begin once Parliament has adopted its position. The call by EU leaders to conclude pending Omnibus packages before the end of 2026 therefore appears out of reach for this file.

What has the Council changed?

Topic Commission proposal (November 2025) Council mandate (October 2026)
Definition of personal data Art. 4(1) GDPR: information does not count as personal data for a company that cannot reasonably identify the person. The change to Art. 4(1) is dropped. New Art. 25a on pseudonymised data.
AI and legitimate interest Art. 88c GDPR: companies could use personal data to develop and operate AI on the basis of legitimate interest, under specified conditions and with an unconditional right to object. Reworked into Art. 88 bis. The detailed safeguards and the unconditional right to object are replaced by a general safeguards requirement; some survive in a non-binding recital.
Residual sensitive data in AI Art. 9(2)(k) and Art. 9(5) GDPR: exception for residual sensitive data in AI development and operation, with safeguards. Kept but narrowed to incidental processing of residual data the controller did not intend to process. Data provided to the AI system during deployment is excluded (recital 33).
Browser signals Art. 88b GDPR: browser and device signals must be honoured. Deleted.
Cookie rules Art. 88a GDPR: cookie rules moved from ePrivacy into the GDPR, with a six-month wait before asking again after a refusal. Art. 88a is gone. The rules stay in ePrivacy Art. 5(3); the wait is cut to four months; new exemption for measuring contextual advertising.
Access requests Art. 12(5) GDPR: refuse or charge where requests are abused for purposes other than data protection; lower burden of proof for excessive requests. The controller must demonstrate an abusive intention, but reasonable grounds are enough. The same applies to complaints (Art. 57(4)).
Privacy notices No notice in simple, low-data relationships, unless data is shared, transferred abroad, profiled or high-risk. No notice if people are likely to know who uses their data and why, and the risk is low. Sharing, transfers and profiling no longer block it; complex, sensitive and large-scale processing is excluded.

Does the Digital Omnibus change the definition of personal data?

No. Under the Council's mandate, the current definition in Art. 4(1) GDPR stays, and the question of pseudonymised data moves to a new Art. 25a.

The Commission had proposed that information should not count as personal data for a company that cannot reasonably identify the person, even if others could. It presented this as codifying the Court of Justice's EDPS v SRB ruling, with the obligations remaining for the entity that originally pseudonymised the data. Technical criteria for when pseudonymised data stops being personal were to be set through Commission implementing acts (Art. 41a).

The Council dropped that rewrite. Under the new Art. 25a, pseudonymised data is not personal data for someone who cannot identify the person, but becomes personal data again for a third party that can, judged by practical factors such as cost, time and effort. An opinion from the European Data Protection Board (EDPB) replaces the Commission's planned technical criteria.

Can companies use legitimate interest to develop and use AI?

Yes, under the Council's text, but with a general requirement for safeguards rather than the detailed safeguards the Commission proposed.

Under the GDPR, a company needs a legal basis to process personal data. One of them, legitimate interest (Art. 6(1)(f)), allows processing without consent where it is necessary for the company's legitimate interests, unless these are overridden by the person's interests, rights and freedoms. This is assessed case by case in a balancing test.

The Commission proposed a new Art. 88c confirming that legitimate interest can be used to develop and operate AI systems and models, with the balancing test still applying. It came with safeguards: stronger transparency, data minimisation, protection against disclosure of data, a clause protecting children, and an unconditional right for people to object.

The Council kept the permission but reshaped it as Art. 88 bis. The detailed safeguards and the unconditional right to object were replaced by a general requirement of appropriate measures and safeguards, including the right to object under Art. 21 GDPR. Only part of the original safeguards remains, in a non-binding recital (33a). The balancing test in Art. 6(1)(f) still applies, so AI developers must still show that their interest is not overridden by the person's rights.

The change remains contested. Critics argue that naming AI in the law creates a very broad category, since AI already sits behind recommender systems, advertising systems and workplace tools, so companies would in effect be presumed to have an overriding legitimate interest whenever they train or use AI. Others point out that the Council's text still requires the balancing test.

What happens to sensitive data in AI development?

The Council keeps an exception for sensitive data in AI, but only for data that ends up in a system incidentally, and not for data people provide to an AI system while using it.

The GDPR's rules on special categories of data (Art. 9), such as health, ethnicity or religion, are hard to apply to AI development. Training data collected at web scale inevitably contains some of this information, for example a forum post mentioning someone's illness or a news article mentioning someone's trade union membership.

The Commission therefore proposed a new exception, Art. 9(2)(k), for processing such data in the development and operation of an AI system or model. Under the safeguards in Art. 9(5), controllers would have to try to avoid collecting such data, delete it if they find it, and, where deletion would take disproportionate effort, protect it so it cannot surface in outputs or reach third parties.

The Council narrowed the exception to the incidental processing of residual data that the controller did not intend to process (Art. 9(2)(k)). Controllers must erase such data without undue delay, or protect it where erasure is technically impossible or would take manifestly disproportionate effort (Art. 9(5)). Recital 33 adds that the exception does not cover sensitive data acquired by or provided to an AI system while it is in use, which would include user prompts.

What changes for cookies and browser signals?

Under the Council's mandate, cookie rules stay in the ePrivacy Directive, consent remains the default, one-click refusal stays, the pause before asking again is cut to four months, and the rule on browser signals is deleted.

Today, the rules requiring consent before a website stores or reads information on a user's device sit in Art. 5(3) of the ePrivacy Directive. They cover cookies and similar technologies, such as tracking pixels and the software development kits (SDKs) built into mobile apps.

The Commission proposed moving these rules into the GDPR as a new Art. 88a, so one regime and one set of supervisors would apply. Consent would stay the default, users could refuse with one click, and sites would have to wait six months before asking again for the same purpose. A companion Art. 88b would have required websites to honour automatic "no tracking" choices set in browsers or devices, with media services exempt.

The Council deleted the browser-signal provision and moved the cookie rules back into Art. 5(3) of the ePrivacy Directive, with updated wording. One-click refusal and the pause before asking again survive, but the pause is shortened to four months. Consent is not needed where storage or access is strictly necessary for one of six purposes:

  1. Transmitting a communication.
  2. Providing a service the user has explicitly requested.
  3. The provider's own anonymous and aggregated audience measurement.
  4. Audience measurement under Art. 24 of the European Media Freedom Act.
  5. Technical security.
  6. Measuring contextual advertising.

The last exemption lets a site measure the display and performance of contextual advertising without consent, provided the measurement relates to a single visit or search query, involves no profiling or link to the person's past or future activity, and the data is pseudonymised after collection and used for no other purpose.

An exemption from consent is not an exemption from the GDPR. Pseudonymised data remains personal data, so transparency and security duties still apply. Any use beyond the exempt purpose needs its own legal basis under Art. 6 GDPR. Supervision moves to the GDPR authorities (new Art. 15a(5)), and Member States would have 24 months to transpose the amended directive.

The deletion of the browser-signal rule, seen as one of the proposal's most visible benefits for internet users, is among the most contested changes. Industry warned about the cost of honouring such signals: a Google-commissioned study put it at €40 to 50 billion a year for EU businesses, a figure that noyb disputes. A coalition of civil society organisations has urged lawmakers to restore the rule, and amendments to that effect have been tabled in Parliament.

Can companies refuse data access requests?

Yes, but as today only where a request is manifestly unfounded or excessive. The Council adds one case: an access request also counts as excessive where the company can demonstrate that the person making it has an abusive intention.

Under the GDPR today, a controller may refuse a request, or charge a fee for it, only where it is manifestly unfounded or excessive (Art. 12(5)), and the controller has to show this. The Commission proposed allowing controllers to refuse or charge for access requests that abuse the right for purposes other than data protection, and lowering the burden of proof for showing that a request is excessive.

The Council kept the Commission’s idea but narrowed the test. The existing grounds stay, and the Commission’s wording on abuse “for purposes other than data protection” is replaced by an abusive intention that the controller can demonstrate. A controller that refuses must tell the person why. The burden of proof stays with the controller, but the Commission’s lower standard survives: it is enough to show reasonable grounds to believe that a request is excessive or made with an abusive intention.

The recitals add that repeated requests are not automatically excessive, although they may indicate abusive intent. Abusive intention would also become a ground for supervisory authorities to refuse complaints (Art. 57(4)).

When does a company not need a privacy notice?

Under the Council's text, a privacy notice is not needed when it is reasonable to believe the person already knows who the company is and why it uses their data, and the processing is not likely to result in a high risk.

Today, a controller that collects data from a person can skip the privacy notice only where the person already has the information (Art. 13(4)). The Commission proposed a wider exemption for clear and limited relationships with a controller whose activity is not data-intensive. It would not have applied where data is passed to other recipients, transferred to a third country, used for automated decision-making or likely to result in a high risk.

The Council replaced this with a new Art. 13(5). The "not data-intensive" test and the Commission's list of exclusions are gone. Instead, the exemption presented above does not apply to complex processing, large amounts of personal data, or sensitive and criminal conviction data (Arts. 9 and 10), and the recitals rule it out in employment and in dealings with public authorities. The example usually given is a craftsman and their clients.

What does the Digital Omnibus mean in practice?

The Council has pulled back from the most ambitious parts of the Commission's proposal while keeping its overall direction of lighter obligations. The new definition of personal data and the browser-signal rule did not survive, the cookie rules stay in the ePrivacy Directive, and the AI provisions were narrowed rather than removed. What the final text looks like now depends on Parliament, whose position is still pending.

Who benefits will depend on who is affected. The Commission presents the package as relief for smaller businesses with simple data processing. In practice, the benefits are likely to flow mostly to large companies. Flexible concepts that are open to national interpretation are easier to manage for firms with in-house legal teams, while smaller companies would face more uncertainty and more costly legal advice. Parts of the package, such as the cookie rules, also stay in a directive that each country implements, so larger firms are expected to track national differences with dedicated resources, while smaller ones may have to rely on external advice.

What to do now

  • Keep applying the current rules. Nothing changes until a final text is adopted.
  • Map the cookies, pixels and SDKs on your websites and apps, including those added by vendors.
  • Separate basic audience measurement from behavioural or programmatic advertising, which would still require consent.
  • If you develop or use AI, document your legitimate interest assessments and how you handle sensitive data in training data.
  • Follow Parliament's position in early 2027, since it will decide whether rules like the browser signals come back.

Frequently asked questions

When will the Digital Omnibus apply?

There is no date yet. Parliament still has to adopt its position, with a committee vote not expected before early 2027, and only then can trilogue negotiations begin. Once adopted, Member States would have 24 months to transpose the changes to the ePrivacy Directive.

Do the current GDPR and cookie rules still apply?

Yes. Until a final text is adopted, the current GDPR and ePrivacy rules apply unchanged.

Will the definition of personal data change?

Not under the Council's mandate. The current definition in Art. 4(1) GDPR stays, and a new Art. 25a deals with pseudonymised data instead.

Is the Digital Omnibus the same as the AI Omnibus?

No. They were proposed together, but the AI Omnibus was fast-tracked and adopted as Regulation (EU) 2026/1744. The Digital Omnibus on data is a separate file that is still being negotiated.

Will websites still need cookie consent?

Yes. Consent remains the default under the Council's text. It is not needed only for six strictly necessary purposes, including technical security, the provider's own anonymous audience measurement and, under conditions, measuring contextual advertising.

Sources

  • European Commission, Digital Omnibus proposal, November 2025: [EUR-Lex link]
  • Council of the EU, mandate of 21 October 2026, ST 14756/26: [Council register link]
  • Regulation (EU) 2026/1744 (AI Omnibus): [EUR-Lex link] Photo: FrDr / Wikimedia Commons, CC BY-SA 4.0, colour edited.
  • Photo: FrDr / Wikimedia Commons, CC BY-SA 4.0, colour edited

Want to know as soon as the Digital Omnibus moves? Set up a Watchtower to track it, free for 7 days: myriad.ai/watchtowers-regulatory-watchlists

The world's most informed compliance team is one call away.

Book a discovery call