Written by Alexis Hirschhorn, CEO of Acuna GRC. ISO/IEC 27001 Lead Auditor, ISO/IEC 42001 Lead Auditor, PECB Certified Trainer; leads ISO 27001 and ISO 42001 implementations for Swiss organisations.
The legal statements in this article rest on primary sources (EUR-Lex, the European Commission, the Council of the EU, the European Parliament's Legislative Observatory and the UK government), listed under Sources.
This article provides general information about EU law as at 19 November 2026. It is not legal, regulatory or compliance advice, does not create a lawyer-client or advisory relationship, and should not be relied on to determine whether a specific law applies to your organisation. Part of what it describes is a legislative proposal that can still change. Obtain advice from a qualified lawyer before making compliance decisions.
The short answer. "Digital Omnibus" is the name of two separate EU packages, and only one of them is law. The first, the Digital Omnibus on AI, Regulation (EU) 2026/1744, has been in force since 27 July 2026. It amended the EU AI Act: the high-risk duties for the Annex III areas now apply from 2 December 2027 instead of 2 August 2026, those for AI in regulated products from 2 August 2028, and a ninth prohibited practice applies from December 2026. The second, the Digital Omnibus on data, the GDPR, cookies and incident reporting, COM(2025) 837 (procedure 2025/0360(COD)), is still a proposal. The Council agreed its negotiating mandate on 21 October 2026; the European Parliament has no position yet, and no trilogue has started. None of its changes applies today.
| Item | Status as of 19 November 2026 |
|---|---|
| Digital Omnibus on AI | Law. Regulation (EU) 2026/1744, in force since 27 July 2026 |
| AI Act high-risk duties | Annex III areas: 2 December 2027. Annex I regulated products: 2 August 2028 |
| AI Act new prohibition | Prohibition 9 (non-consensual intimate content and child sexual abuse material): December 2026 |
| Digital Omnibus (data, GDPR, cookies, incident reporting) | Proposal. COM(2025) 837, procedure 2025/0360(COD) |
| Council of the EU | Negotiating mandate agreed on 21 October 2026 |
| European Parliament | No position. Status "Awaiting committee decision"; no committee or plenary vote |
| Trilogues | Not started |
| GDPR breach deadline | Still 72 hours. The 96 hours in the Commission's proposal do not apply |
Much of what is written about the "Digital Omnibus" mixes the two packages. Treating the draft as law leads to the wrong breach deadline in your incident procedure; treating the law as a draft leads to a missed date.
This guide keeps the two apart. It sets out what the AI Omnibus changed, where the data Omnibus stands and what each institution wants, what both mean for a Swiss or EU company, and what to do now rather than later.
- AI Act, as amended by 2026/1744High-risk from 2 Dec 2027 (Annex III) and 2 Aug 2028 (Annex I)
- GDPR, Art. 33Breach notice to the authority within 72 hours
- ePrivacy Directive, Art. 5(3)Cookie consent rules, as implemented nationally
- NIS2, Art. 23Its own reporting channel: 24 h, 72 h, 1 month
- Breach notice96 hours, high-risk breaches only (Commission)
- CookiesOne-click consent and browser preference signals
- Incident reportingOne entry point for NIS2, GDPR and DORA
- Data rulesConsolidated into the Data Act
Two packages under one name
The Commission presented both packages on 19 November 2025, as part of its plan to simplify the EU's digital rulebook. They then went down separate legislative tracks, and they now stand at opposite ends of the process.
| Digital Omnibus on AI | Digital Omnibus (data, GDPR, cookies, incident reporting) | |
|---|---|---|
| Reference | Regulation (EU) 2026/1744 | Proposal COM(2025) 837, procedure 2025/0360(COD) |
| Amends | The AI Act, Regulation (EU) 2024/1689 | The GDPR, the ePrivacy Directive, the Data Act, and the incident-reporting rules of NIS2, the GDPR and DORA |
| Status on 19 Nov 2026 | In force since 27 July 2026 | Council mandate agreed 21 Oct 2026; no Parliament position |
| Applies to you today? | Yes, through the amended AI Act | No. Current law applies until a final text is adopted |
| Main effect | Later high-risk dates, a new prohibition, a reworded AI literacy duty | A narrower breach-notification duty, cookie consent changes, a single incident-reporting entry point, data rules consolidated |
The Parliament's Legislative Observatory calls the second package "Digital Omnibus (Omnibus VII)". In this guide, "AI Omnibus" means Regulation (EU) 2026/1744 and "Digital Omnibus proposal" means COM(2025) 837.
The Digital Omnibus on AI: what changed in the AI Act
The Commission adopted its AI Omnibus proposal on 19 November 2025. Parliament and the Council reached a political agreement on 7 May 2026, and Regulation (EU) 2026/1744 entered into force on 27 July 2026. It does not replace the AI Act; it amends it. The EU AI Act guide has the full timeline and obligations. This section covers only what the Omnibus changed.
New dates for high-risk AI systems
The largest change is the delay of the high-risk regime, the part of the AI Act with the heaviest obligations: risk management, data governance, technical documentation, logging, human oversight, conformity assessment and registration.
- Annex III high-risk systems (biometrics, critical infrastructure, education, employment, access to essential services, law enforcement, migration, justice): the rules apply from 2 December 2027. The original AI Act date was 2 August 2026.
- High-risk AI in products covered by Annex I (for example lifts, toys or medical devices that need a third-party conformity assessment): the rules apply from 2 August 2028. The original date was 2 August 2027.
Both are fixed dates in the regulation. Plan against them, not against a further delay.
To know whether a system falls into either group, the test itself has not changed: Article 6 and Annex III of the AI Act. Our high-risk AI classification analysis works through it step by step. The Commission's guidelines on high-risk classification under Article 6(5) were published as a draft on 19 May 2026; treat them as a draft until the final version appears.
What did not move
The delay concerns high-risk systems only. Everything else in the AI Act kept its date:
- Prohibited practices and AI literacy have applied since 2 February 2025.
- General-purpose AI model rules and the governance rules have applied since 2 August 2025.
- The rest of the AI Act, including the Article 50 transparency rules (telling people they are dealing with a chatbot, labelling deepfakes), has applied since 2 August 2026. From that date the AI Office and national authorities enforce the Act.
- Penalties are unchanged: up to EUR 35 million or 7% of worldwide annual turnover for prohibited practices, and up to EUR 15 million or 3% for most other obligations (Article 99).
So the AI Act was not postponed: one part was, and the rest is live.
A ninth prohibited practice
The AI Omnibus added a new prohibition to Article 5: AI systems that generate non-consensual sexually explicit or intimate content, or child sexual abuse material. The Commission cites "nudification" apps as the example. The Commission calls it Prohibition 9 and states that it applies from December 2026. The UK government's guidance on the AI Act in Northern Ireland gives the day: 2 December 2026. The same guidance gives 2 December 2026 for the Article 50(2) marking duty of generative AI systems already on the market.
AI literacy reworded
Article 4 originally required providers and deployers to ensure a sufficient level of AI literacy among their staff. The AI Omnibus reworded it: companies must take measures to support the AI literacy of their staff and of the people who use AI systems on their behalf. The duty remains, and national authorities have supervised it since 2 August 2026. Our AI literacy answer sets out what that means in practice.
- AI Act bans and AI literacyPassed:
- AI Act general-purpose AI rulesPassed:
- Both Omnibus proposals presentedPassed:
- Political agreement on the AI OmnibusPassed:
- AI Omnibus 2026/1744 in forcePassed:
- AI Act applies, incl. transparencyPassed:
- Council mandate on COM(2025) 837Passed:
- You are here: Nov 2026
- Prohibition 9 (Article 5)Still ahead:
- AI Act Annex III high-riskStill ahead:
- AI Act Annex I high-riskStill ahead:
The Digital Omnibus proposal: data, GDPR, cookies and incident reporting
COM(2025) 837 is a large amending act. It touches the GDPR, the ePrivacy Directive, the Data Act and the incident-reporting duties in NIS2, the GDPR and DORA. The Commission estimates savings for business of at least EUR 1 billion a year, plus EUR 1 billion in one-off savings, at least EUR 5 billion in total by 2029.
All of it is still a proposal. Until Parliament and the Council agree a text and it is published in the Official Journal, nothing below changes your obligations.
Where the procedure stands
- 19 November 2025: the Commission presents the proposal.
- 25 February 2026: Parliament appoints two rapporteurs, Aura Salla (EPP) for the Industry committee (ITRE) and Marina Kaljurand (S&D) for the Civil Liberties committee (LIBE), which share the file. The Internal Market (IMCO) and Legal Affairs (JURI) committees give opinions.
- 22 June 2026: the draft report is published in committee, followed by amendments in July.
- 21 October 2026: the Council agrees its negotiating mandate.
- 19 November 2026: Parliament's status is still "Awaiting committee decision". No committee vote and no plenary vote are scheduled in the Legislative Observatory.
Trilogues, the three-way negotiation between Parliament, Council and Commission, can only start once Parliament has a position. After a deal, the text still needs formal adoption, publication and, for most provisions, a transition period. No application date can be given today.
GDPR: what the Commission proposes and what the Council wants
The Council's mandate does not simply accept the Commission's text. On several points it narrows or adds safeguards.
| Topic | Commission proposal (19 Nov 2025) | Council mandate (21 Oct 2026) | Law today |
|---|---|---|---|
| Definition of personal data | Clarifies pseudonymisation and when data counts as non-personal for a given entity | Keeps the current definition; adds a provision on pseudonymisation and identification | GDPR Art. 4(1) unchanged |
| AI development and operation | Clarifies that legitimate interest can be a legal basis, with safeguards and a right to object | Not detailed in the Council's press release | Case-by-case legitimate-interest test |
| Special-category data in datasets | A narrow derogation for residual sensitive data in AI datasets | Adds safeguards to the sensitive-data derogation for biometric verification and AI | Art. 9 prohibition and its listed exceptions |
| Breach notification to the authority | 96 hours, only for higher-risk breaches, with a common EU template | Supports a longer deadline than today | 72 hours (Art. 33) |
The Council's mandate also provides for an EU-wide list of processing operations that require a data protection impact assessment, and common templates. Today each supervisory authority keeps its own list.
Breach notification: 72 hours still applies
The proposal would give controllers 96 hours instead of 72 to notify the supervisory authority, and only for breaches likely to bring a high risk, with a common EU template. The Council's press release says it supports a longer deadline but does not state a number of hours. Until a text is adopted, nothing changes: notify within 72 hours under Article 33 GDPR, and keep the incident procedure as it is. Our GDPR 72-hour breach notification answer covers the current rule.
- GDPR todayArt. 33, to the supervisory authority
- Discovery
- 72 hoursNotify
- Commission proposalCOM(2025) 837, high-risk breaches only
- Discovery
- 96 hoursNotify (proposed)
- Council mandate21 Oct 2026
- Discovery
- Supports a longer deadline; hours not stated in its press release
- NIS2 todayArt. 23, significant incidents
- Discovery
- 24 hoursEarly warning
- 72 hoursNotification
- 1 monthFinal report
Cookies and consent banners
The Commission wants fewer cookie banners. Its proposal lets users give or refuse consent with one click and lets browsers carry users' central preference settings, so a site does not ask again. The Council's mandate keeps the cookie rules in the ePrivacy Directive rather than moving them, and widens the cases in which no consent is needed. Where the rules end up, and in which law, is one of the main open questions for the trilogue. Until then, Article 5(3) of the ePrivacy Directive and its national implementations apply as they do today.
One entry point for incident reports
The proposal would create a single entry point for incident reporting under NIS2, the GDPR and DORA, on the principle "report once, share many". The Council's mandate prefers a national entry point in each member state, plus an information point at EU level. Who runs it, and whether it comes, depends on the trilogue. Today each regime still has its own channel and its own clock: see the NIS2 incident reporting answer for the 24-hour, 72-hour and one-month steps.
Data Act and the other data rules
The proposal folds elements of the public-sector re-use and data-intermediation rules into the Data Act, so that the main data rules sit in fewer texts. It also calibrates the Data Act's cloud-switching rules, with targeted exemptions for custom-made services and for certain small and medium-sized and small mid-cap providers under existing contracts.
Not part of the Omnibus: the NIS2 amendment
In January 2026 the Commission proposed a separate, targeted amendment to NIS2, COM(2026) 13 (procedure 2026/0012(COD)), together with a revised Cybersecurity Act. It is a different procedure from the Digital Omnibus, and also still a proposal. The NIS2 obligations in force, including the Article 21 measures and the Article 23 reporting clock, are unchanged by both.
What each package means for a Swiss or EU company
The AI Omnibus changes dates you must plan against now. The Digital Omnibus proposal changes nothing yet, but it shows where the GDPR, cookie and reporting rules are likely to go.
| Your role | Digital Omnibus on AI (law) | Digital Omnibus proposal (not law) |
|---|---|---|
| Provider of a high-risk AI system | Annex III duties from 2 Dec 2027, Annex I from 2 Aug 2028. Use the time for documentation, risk management and conformity assessment | Legitimate interest for AI training may become clearer; plan on today's GDPR test |
| Deployer of AI systems | AI literacy measures and Art. 5 checks already apply; Art. 50 transparency since 2 Aug 2026; Art. 26 deployer duties for high-risk systems from Dec 2027 | No change today |
| Any company using AI tools | Check no tool falls under Prohibition 9 before December 2026 | No change today |
| GDPR controller | No change | Breach deadline may become 96 hours for high-risk breaches; until then, 72 hours |
| Website operator | No change | Cookie consent may change (one-click, browser signals); today's rules apply |
| NIS2 essential or important entity | No change | A single or national entry point may replace separate channels; today, report to your CSIRT or authority |
| Swiss company with an EU link | The AI Act can apply through Art. 2: an AI system placed on the EU market, or output used in the EU | The GDPR can apply through Art. 3(2); any change would reach you the same way |
For Swiss companies, the AI Omnibus matters in the same way as the AI Act itself: the AI Act can reach a Swiss provider or deployer whose AI system is placed on the EU market or whose output is used in the EU. Our answer on whether the EU AI Act applies to Swiss companies explains the three routes. The Digital Omnibus proposal would amend the GDPR, which can apply to a Swiss company that offers goods or services to people in the EU or monitors them.
For UK companies selling into Northern Ireland, the UK government stated on 4 November 2026 that the AI Act applies in Northern Ireland, in a specific and limited way, from 10 November 2026, under the Windsor Framework. It covers AI closely integrated with physical products placed on the Northern Ireland market, not standalone software.
What to do now, and what to wait for
The rule of thumb: act on the AI Omnibus, watch the Digital Omnibus proposal.
- Update your AI Act timeline. Replace 2 August 2026 with 2 December 2027 for Annex III systems, and 2 August 2027 with 2 August 2028 for Annex I products, in your plans, board papers and supplier contracts.
- Keep the live duties live. AI literacy measures, the Article 5 prohibitions and the Article 50 transparency rules apply today. The delay does not touch them.
- Check your AI inventory against Prohibition 9 before December 2026. Include tools bought off the shelf and generative features inside larger products.
- Classify each AI system now. The high-risk test did not change; use the extra time to build the documentation, not to postpone the classification.
- Leave the GDPR breach procedure at 72 hours. Do not plan on 96 hours until a text is adopted.
- Leave cookie banners as they are. Do not redesign consent flows around one-click or browser signals before the rules are final.
- Keep each incident-reporting channel separate. NIS2, the GDPR, DORA and, for Swiss operators, the ISA each keep their own deadlines until a single entry point exists.
- Set a review date. Watch for Parliament's committee vote and the start of trilogues, and recheck your plan when either happens.
What to wait for: the final breach deadline and threshold, where the cookie rules end up, who runs the incident-reporting entry point, Parliament's position, the application dates of the Digital Omnibus, and the final Article 6 classification guidelines.
The pattern in both packages is the same: dates and procedures move, the underlying controls do not. An AI inventory, a record of processing, an incident log and a supplier register are evidence under the current law and under whatever version of the Omnibus is adopted.
How Acuna GRC helps
Acuna GRC keeps your obligations, measures, controls and evidence in one programme, so a change of date is an update to a plan, not a new project. When a law changes, you change the requirement once, and the measures and evidence linked to it stay in place.
| Obligation | Where it lives in Acuna GRC | What Acuna GRC does not do |
|---|---|---|
| AI Act inventory, classification and high-risk dates | AI Governance: AI system register, classification, impact assessments with a fundamental-rights section, human oversight | Certify conformity with the AI Act |
| AI Act programme for providers and deployers | EU AI Act solution: one register with your role for each AI system, its risk class, impact assessment, human oversight and incidents, next to ISO 42001 | Decide your role or risk class for you |
| Serious AI incidents | AI Governance: an incident register with a 72-hour clock on serious AI incidents | Report to the market surveillance authority |
| AI literacy measures | Staff Portal: published policies, read-and-acknowledge campaigns, reminders | Deliver the training itself |
| GDPR breach notification | Data Privacy: breach wizard with a live 72-hour clock and a generated authority notice | File with the supervisory authority |
| NIS2 measures and incident reporting | NIS2 solution: NIS2 measures with owners, reused ISO 27001 controls, supplier checks and an incident timeline | Submit reports to a CSIRT or authority |
Hosting: your data is hosted in Switzerland or the EU, as you choose, and on-premises deployment is available. See the Security and Trust Center.
Related reading: the EU AI Act guide, the NIS2 guide, high-risk AI systems under the EU AI Act and Swiss compliance requirements.
See the EU AI Act solution → · See the NIS2 solution
Sources
EU sources are the Official Journal texts on EUR-Lex and the institutions' own pages. All accessed on 19 November 2026.
- AI Act, Regulation (EU) 2024/1689 (EUR-Lex)
- Digital Omnibus on AI, Regulation (EU) 2026/1744 (EUR-Lex)
- European Commission: AI Act, regulatory framework and timeline (updated 19 October 2026)
- European Commission: AI literacy, questions and answers
- European Commission: draft guidelines on the classification of high-risk AI systems
- European Commission: Digital Omnibus regulation proposal
- European Parliament Legislative Observatory: procedure 2025/0360(COD), Digital Omnibus (Omnibus VII)
- European Parliament Legislative Observatory: summary of COM(2025) 837
- European Parliament Legislative Train: Digital Omnibus
- Council of the EU: press release on its Digital Omnibus position, 21 October 2026
- GDPR, Regulation (EU) 2016/679 (EUR-Lex)
- ePrivacy Directive 2002/58/EC (EUR-Lex)
- Data Act, Regulation (EU) 2023/2854 (EUR-Lex)
- NIS2, Directive (EU) 2022/2555 (EUR-Lex)
- European Parliament Legislative Observatory: procedure 2026/0012(COD), targeted NIS2 amendments
- UK government: partial application of the EU AI Act in Northern Ireland, 4 November 2026
| Date | Change |
|---|---|
| 2026-11-19 | First published. Status as of 19 November 2026: AI Omnibus in force since 27 July 2026; Council mandate on COM(2025) 837 agreed 21 October 2026; no Parliament position. |
Regulatory References
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

