Ad Tech Compliance
EU Digital Omnibus tracker: GDPR and ePrivacy status, timeline and text
Published · Last updated
Next scheduled review:
The EU Digital Omnibus is still a proposal. On 9 November 2026 the Council has a negotiating mandate, agreed on 21 October 2026, the European Parliament has no position, and trilogues have not started (Council document 14756/26). The Council text keeps cookie rules in ePrivacy Article 5(3), adds six consent exemptions and drops the browser signal.
Contents
Key facts
- The proposal. The Commission published COM(2025) 837 on 19 November 2025. It would amend the GDPR, the ePrivacy Directive, the Data Act and the incident-reporting rules (EUR-Lex, COM(2025) 837; Legislative Observatory, 2025/0360(COD)).
- The Council has a mandate. Coreper agreed it on 21 October 2026. The General Secretariat circulated the 179-page text as document 14756/26 on 22 October 2026 (Council document 14756/26).
- Parliament has no position. The ITRE-LIBE draft report of 22 June 2026 holds 78 amendments, none to the cookie or AI articles. The Legislative Observatory showed "Awaiting committee decision" on 9 November 2026 (draft report PE786.818; Legislative Observatory).
- Cookie rules in the Council text. Consent stays the rule, six purposes are exempt, refusal must take a single click, and a site must wait at least four months before asking again (Council document 14756/26, pp. 156 to 158).
- The regulators' view. The EDPB and the EDPS adopted Joint Opinion 2/2026 on 10 February 2026. They welcomed the browser signal and asked for a contextual advertising exception (EDPB-EDPS Joint Opinion 2/2026).
- The old ePrivacy Regulation is gone. EUR-Lex lists the 2017 proposal as withdrawn, with an end of validity of 6 October 2025 (EUR-Lex, COM(2017) 10).
Definition
Digital Omnibus (file 2025/0360(COD)) is a proposed EU regulation that would amend the GDPR, the ePrivacy Directive 2002/58/EC, the Data Act and other digital laws (EUR-Lex, COM(2025) 837).
The AI Act changes travelled separately. The Commission proposed them on the same day as file 2025/0359(COD), and the Legislative Observatory shows that procedure as completed, with publication in the Official Journal on 24 July 2026 (Legislative Observatory, 2025/0359(COD)). This tracker covers the data and privacy file only. Our ad tech compliance hub collects the other frameworks.
Digital Omnibus GDPR status on 9 November 2026
The ordinary legislative procedure needs three things before a text becomes law. The Council and the Parliament each adopt a position, the two then agree a text in trilogue with the Commission, and both formally adopt it. Only the first step has happened, and only on the Council side.
4 of 4 rows
European Commission | Proposal COM(2025) 837 | 19 November 2025 | Tabled (EUR-Lex) |
Council of the EU | Mandate for negotiations, document 14756/26 | Agreed 21 October 2026; circulated 22 October 2026 | Adopted by Coreper (Council register) |
European Parliament | ITRE-LIBE draft report PE786.818 | 22 June 2026 | Amendments tabled 27 July 2026; committee vote not held (Legislative Observatory) |
Trilogue | None | n/a | Not started; the Council said talks begin only after Parliament adopts its position (PPC Land, 25 October 2026) |
European Commission
- Latest document
Proposal COM(2025) 837
- Date
19 November 2025
- Status on 9 November 2026
Tabled (EUR-Lex)
Council of the EU
- Latest document
Mandate for negotiations, document 14756/26
- Date
Agreed 21 October 2026; circulated 22 October 2026
- Status on 9 November 2026
Adopted by Coreper (Council register)
European Parliament
- Latest document
ITRE-LIBE draft report PE786.818
- Date
22 June 2026
- Status on 9 November 2026
Amendments tabled 27 July 2026; committee vote not held (Legislative Observatory)
Trilogue
- Latest document
None
- Date
n/a
- Status on 9 November 2026
Not started; the Council said talks begin only after Parliament adopts its position (PPC Land, 25 October 2026)
Table by AdSovereign, CC BY 4.0.
The Parliament file sits with two committees jointly. Aura Salla (EPP, ITRE) and Marina Kaljurand (S&D, LIBE) were appointed co-rapporteurs on 25 February 2026 (Legislative Observatory). Their draft report says Parliament asked for a targeted impact assessment on specific provisions in Articles 3, 4 and 10 of the proposal. Article 3 holds the GDPR amendments (draft report PE786.818).
Members tabled more than 1,000 amendments to the GDPR and ePrivacy parts, according to noyb's count reported on 12 October 2026 (PPC Land, 12 October 2026). No committee vote date appears on the Legislative Observatory page we checked.
Digital Omnibus GDPR timeline
Each row names its source. "Primary" means we read the official text. "Reported" means the document is not public and we rely on dated reporting.
14 of 14 rows
19 November 2025 | Commission publishes COM(2025) 837 with Articles 88a, 88b and 88c GDPR | Primary (EUR-Lex) |
19 January 2026 | Referral to Parliament committees announced | Primary (Legislative Observatory) |
10 February 2026 | EDPB and EDPS adopt Joint Opinion 2/2026 | Primary (EDPB) |
25 February 2026 | Co-rapporteurs Salla and Kaljurand appointed | Primary (Legislative Observatory) |
18 June 2026 | Council fifth compromise text removes the Article 88b browser signal | Reported (PPC Land, 28 June 2026) |
22 June 2026 | ITRE-LIBE draft report published | Primary (PE786.818) |
27 July 2026 | Amendments tabled in committee | Primary (Legislative Observatory) |
3 September 2026 | Presidency text 12535/26 deletes Articles 88a and 88b and rewrites ePrivacy Article 5(3) with six exemptions | Reported, leaked LIMITE text (PPC Land, 21 September 2026) |
10 September 2026 | 19 organisations ask the Irish Presidency to restore the browser signal | Reported (PPC Land, 13 September 2026) |
2 October 2026 | Draft mandate 13886/26 cuts the re-ask wait to four months | Reported (PPC Land, 9 October 2026) |
7 October 2026 | Coreper meeting ends without a mandate | Reported (PPC Land, 25 October 2026) |
21 October 2026 | Coreper agrees the Council mandate | Primary (document 14756/26, cover note) |
22 October 2026 | Mandate circulated as document 14756/26 | Primary (Council register) |
9 November 2026 | Parliament still "Awaiting committee decision"; no trilogue | Primary (Legislative Observatory) |
19 November 2025
- Event
Commission publishes COM(2025) 837 with Articles 88a, 88b and 88c GDPR
- Source type and link
Primary (EUR-Lex)
19 January 2026
- Event
Referral to Parliament committees announced
- Source type and link
Primary (Legislative Observatory)
10 February 2026
- Event
EDPB and EDPS adopt Joint Opinion 2/2026
- Source type and link
Primary (EDPB)
25 February 2026
- Event
Co-rapporteurs Salla and Kaljurand appointed
- Source type and link
Primary (Legislative Observatory)
18 June 2026
- Event
Council fifth compromise text removes the Article 88b browser signal
- Source type and link
Reported (PPC Land, 28 June 2026)
22 June 2026
- Event
ITRE-LIBE draft report published
- Source type and link
Primary (PE786.818)
27 July 2026
- Event
Amendments tabled in committee
- Source type and link
Primary (Legislative Observatory)
3 September 2026
- Event
Presidency text 12535/26 deletes Articles 88a and 88b and rewrites ePrivacy Article 5(3) with six exemptions
- Source type and link
Reported, leaked LIMITE text (PPC Land, 21 September 2026)
10 September 2026
- Event
19 organisations ask the Irish Presidency to restore the browser signal
- Source type and link
Reported (PPC Land, 13 September 2026)
2 October 2026
- Event
Draft mandate 13886/26 cuts the re-ask wait to four months
- Source type and link
Reported (PPC Land, 9 October 2026)
7 October 2026
- Event
Coreper meeting ends without a mandate
- Source type and link
Reported (PPC Land, 25 October 2026)
21 October 2026
- Event
Coreper agrees the Council mandate
- Source type and link
Primary (document 14756/26, cover note)
22 October 2026
- Event
Mandate circulated as document 14756/26
- Source type and link
Primary (Council register)
9 November 2026
- Event
Parliament still "Awaiting committee decision"; no trilogue
- Source type and link
Primary (Legislative Observatory)
Table by AdSovereign, CC BY 4.0.
Article 88a GDPR vs ePrivacy Article 5(3): where the cookie rule would sit
The law today. Article 5(3) of the ePrivacy Directive allows storing or reading information on a device "only" with consent. It has two exemptions: technical storage for transmitting a communication, and storage "strictly necessary" to provide a service the user explicitly requested (Directive 2002/58/EC, consolidated, Article 5(3)). Each member state transposes it into national law and chooses the authority that enforces it.
The Commission's design. The proposal would add a sentence switching Article 5(3) off where the user is a natural person and the information "constitutes or leads to the processing of personal data" (COM(2025) 837, Article 5). A new Article 88a GDPR would then govern those cases, with four exempt purposes, from six months after entry into force. Article 88b would oblige controllers to honour automated, machine-readable choices after 24 months, and non-SME browser providers to support them after 48 months.
The Council's design. The mandate strikes Articles 88a and 88b in full (Council document 14756/26, pp. 143 to 145). It rewrites Article 5(3) of the Directive instead, so the rule stays in ePrivacy. Member states would transpose it within 24 months of adoption, and GDPR supervisory authorities would enforce it (pp. 156 to 158).
The practical difference is timing and uniformity. A GDPR article applies directly and at once. A directive arrives country by country, through national laws.
Side by side: what each version of the Digital Omnibus text says
The Commission column quotes COM(2025) 837 (EUR-Lex). The Council column quotes the mandate (document 14756/26), with page numbers. Parliament has no text to compare.
11 of 11 rows
Where the device-access rule sits | ePrivacy Article 5(3) (EUR-Lex) | New Article 88a GDPR for personal data of natural persons; Article 5(3) disapplied there | Rewritten ePrivacy Article 5(3); Articles 88a and 88b struck (pp. 143 to 145, 156) | No position (OEIL) |
Consent exemptions | Two: transmission; strictly necessary for a requested service | Four: transmission; requested service; aggregated audience measurement by the controller "solely for its own use"; security | Six, each "solely related to and strictly necessary for" the purpose: transmission; requested service and its functionality; anonymous aggregated audience measurement; media audience measurement under EMFA Article 24; technical security; contextual ad measurement (p. 157) | No position |
Audience measurement by a vendor | Not exempt in the Directive text | Controller only, for its own use | A third party may measure "on behalf of" the provider; data not shared, combined or reused (p. 157) | No position |
Contextual ad measurement and frequency capping | Not exempt | Not exempt | Exempt if the ad uses only the page or a single search query, with no profiling, no past or future activity, and pseudonymised data (p. 157); recital names "capping cookies" (p. 48) | No position |
Refusal and re-ask | Not specified in Article 5(3) | Single-click refusal; no new request for 6 months after a refusal | Single-click refusal; no new request for at least 4 months (p. 158) | No position |
Browser and machine-readable signals | None | Article 88b: controllers honour signals after 24 months; non-SME browsers support them after 48 months; media service providers exempt | Deleted (p. 145) | No amendment in the draft report (PE786.818) |
Legitimate interest after exempt access | GDPR Article 6 applies to later processing | Exempt access "and subsequent processing" lawful for the listed purposes | Later processing for other purposes needs an Article 6 basis; a recital sets limits for legitimate interest, such as no monitoring of large parts of online activity (p. 49) | No position |
AI training and operation | No specific article; a legal basis under Article 6 GDPR is needed | Article 88c: legitimate interest "where appropriate", with safeguards including "an unconditional right to object" | Article 88 bis: legitimate interest under Article 6(1)(f), with the Article 21 right to object; the unconditional right is struck (pp. 145 to 146) | No amendment in the draft report |
Definition of personal data | Article 4(1), read with the case law | Adds entity-relative sentences to Article 4(1) | Article 4(1) sentences struck (p. 131); new Article 25a: pseudonymised data is not personal data for a third party unable to identify the person (p. 140) | No amendment in the draft report |
Who enforces cookie rules | National authority chosen by each member state | GDPR authorities, for cases moved into Article 88a | GDPR supervisory authority for Article 5(3) (p. 158) | No position |
When the cookie rules would apply | In force | 6 months after entry into force (Article 88a) | National laws apply 24 months after adoption (p. 158) | No position |
Where the device-access rule sits
- Law today
ePrivacy Article 5(3) (EUR-Lex)
- Commission proposal, 19 November 2025
New Article 88a GDPR for personal data of natural persons; Article 5(3) disapplied there
- Council mandate, 21 October 2026
Rewritten ePrivacy Article 5(3); Articles 88a and 88b struck (pp. 143 to 145, 156)
- Parliament, 9 November 2026
No position (OEIL)
Consent exemptions
- Law today
Two: transmission; strictly necessary for a requested service
- Commission proposal, 19 November 2025
Four: transmission; requested service; aggregated audience measurement by the controller "solely for its own use"; security
- Council mandate, 21 October 2026
Six, each "solely related to and strictly necessary for" the purpose: transmission; requested service and its functionality; anonymous aggregated audience measurement; media audience measurement under EMFA Article 24; technical security; contextual ad measurement (p. 157)
- Parliament, 9 November 2026
No position
Audience measurement by a vendor
- Law today
Not exempt in the Directive text
- Commission proposal, 19 November 2025
Controller only, for its own use
- Council mandate, 21 October 2026
A third party may measure "on behalf of" the provider; data not shared, combined or reused (p. 157)
- Parliament, 9 November 2026
No position
Contextual ad measurement and frequency capping
- Law today
Not exempt
- Commission proposal, 19 November 2025
Not exempt
- Council mandate, 21 October 2026
Exempt if the ad uses only the page or a single search query, with no profiling, no past or future activity, and pseudonymised data (p. 157); recital names "capping cookies" (p. 48)
- Parliament, 9 November 2026
No position
Refusal and re-ask
- Law today
Not specified in Article 5(3)
- Commission proposal, 19 November 2025
Single-click refusal; no new request for 6 months after a refusal
- Council mandate, 21 October 2026
Single-click refusal; no new request for at least 4 months (p. 158)
- Parliament, 9 November 2026
No position
Browser and machine-readable signals
- Law today
None
- Commission proposal, 19 November 2025
Article 88b: controllers honour signals after 24 months; non-SME browsers support them after 48 months; media service providers exempt
- Council mandate, 21 October 2026
Deleted (p. 145)
- Parliament, 9 November 2026
No amendment in the draft report (PE786.818)
Legitimate interest after exempt access
- Law today
GDPR Article 6 applies to later processing
- Commission proposal, 19 November 2025
Exempt access "and subsequent processing" lawful for the listed purposes
- Council mandate, 21 October 2026
Later processing for other purposes needs an Article 6 basis; a recital sets limits for legitimate interest, such as no monitoring of large parts of online activity (p. 49)
- Parliament, 9 November 2026
No position
AI training and operation
- Law today
No specific article; a legal basis under Article 6 GDPR is needed
- Commission proposal, 19 November 2025
Article 88c: legitimate interest "where appropriate", with safeguards including "an unconditional right to object"
- Council mandate, 21 October 2026
Article 88 bis: legitimate interest under Article 6(1)(f), with the Article 21 right to object; the unconditional right is struck (pp. 145 to 146)
- Parliament, 9 November 2026
No amendment in the draft report
Definition of personal data
- Law today
Article 4(1), read with the case law
- Commission proposal, 19 November 2025
Adds entity-relative sentences to Article 4(1)
- Council mandate, 21 October 2026
Article 4(1) sentences struck (p. 131); new Article 25a: pseudonymised data is not personal data for a third party unable to identify the person (p. 140)
- Parliament, 9 November 2026
No amendment in the draft report
Who enforces cookie rules
- Law today
National authority chosen by each member state
- Commission proposal, 19 November 2025
GDPR authorities, for cases moved into Article 88a
- Council mandate, 21 October 2026
GDPR supervisory authority for Article 5(3) (p. 158)
- Parliament, 9 November 2026
No position
When the cookie rules would apply
- Law today
In force
- Commission proposal, 19 November 2025
6 months after entry into force (Article 88a)
- Council mandate, 21 October 2026
National laws apply 24 months after adoption (p. 158)
- Parliament, 9 November 2026
No position
Table by AdSovereign, CC BY 4.0.
Two points need care. First, the Council text speaks of "information", not "personal data", so its rule covers any reading of a device. Second, the Council deleted the Commission's sentence on the six-month start date (p. 169), which leaves transposition as the only clock.
What regulators and stakeholders have said
These are positions, not law. Each carries its date and its status.
EDPB and EDPS (10 February 2026). The two bodies "strongly welcome" Article 88b. They also warned that splitting device-access rules across two instruments could create legal uncertainty, and recommended "adding an exception for contextual advertising" (Joint Opinion 2/2026, pp. 6 and 32). The Council later adopted the contextual exemption and dropped the signal.
Industry and civil society. Google commissioned a study from Implement Consulting Group, published in March 2026. It estimated that browser-level consent would cost EU businesses EUR 40 billion to 50 billion a year (company-commissioned estimate, reported by PPC Land, 28 June 2026). noyb disputed the figures in the same report. The French association Alliance Digitale asked on 21 May 2026 for Article 88b and the re-ask ban to be deleted. A coalition of 19 organisations asked on 10 September 2026 for the signal to return (PPC Land, 13 September 2026).
Law firms. Taylor Wessing read the Commission's audience-measurement exemption as excluding tools that work across several services, so most advertising measurement would stay consent-based (Taylor Wessing, 2 February 2026). That reading concerns the Commission draft; the Council text changed the wording.
What would change for ad tech if the Council text became law
This section is our analysis of the texts above. It is not a statement of law in force. A bid request flow, an analytics tag and a frequency cap fall under different exemptions, so each needs its own test.
6 of 6 rows
Behavioural targeting, retargeting, cross-site IDs in bid requests | Consent | Consent; a recital excludes "providing programmatic advertising" from the contextual exemption (p. 48) | Consent signal quality; GDPR basis for later processing |
First-party web analytics | Consent, unless a national authority tolerates it | Exempt if anonymous, aggregated and not shared or combined (p. 157) | Whether the vendor pools data across clients |
Contextual ad measurement and per-campaign caps | Consent | Exempt within strict limits (p. 157) | Whether a cap uses past activity, which the article excludes |
Joint industry audience measurement | Consent | Exempt under EMFA Article 24 conditions (p. 157) | Pseudonymisation and no tracking outside the measured service |
Consent management platforms and TCF strings | Collect consent per purpose and vendor | Same, plus a single-click refusal and a four-month memory of refusals (p. 158) | How a CMP records refusal and which vendors fit the exemptions |
Clean-room and measurement partners | Recital 26 GDPR counts means reasonably likely to be used "by the controller or by another person" (GDPR) | Article 25a: not personal data for a third party unable to identify; processors stay in scope (p. 140) | Whether the partner is a processor or an independent recipient |
Behavioural targeting, retargeting, cross-site IDs in bid requests
- Law today (Article 5(3))
Consent
- Council mandate
Consent; a recital excludes "providing programmatic advertising" from the contextual exemption (p. 48)
- What still decides the answer
Consent signal quality; GDPR basis for later processing
First-party web analytics
- Law today (Article 5(3))
Consent, unless a national authority tolerates it
- Council mandate
Exempt if anonymous, aggregated and not shared or combined (p. 157)
- What still decides the answer
Whether the vendor pools data across clients
Contextual ad measurement and per-campaign caps
- Law today (Article 5(3))
Consent
- Council mandate
Exempt within strict limits (p. 157)
- What still decides the answer
Whether a cap uses past activity, which the article excludes
Joint industry audience measurement
- Law today (Article 5(3))
Consent
- Council mandate
Exempt under EMFA Article 24 conditions (p. 157)
- What still decides the answer
Pseudonymisation and no tracking outside the measured service
Consent management platforms and TCF strings
- Law today (Article 5(3))
Collect consent per purpose and vendor
- Council mandate
Same, plus a single-click refusal and a four-month memory of refusals (p. 158)
- What still decides the answer
How a CMP records refusal and which vendors fit the exemptions
Clean-room and measurement partners
- Law today (Article 5(3))
Recital 26 GDPR counts means reasonably likely to be used "by the controller or by another person" (GDPR)
- Council mandate
Article 25a: not personal data for a third party unable to identify; processors stay in scope (p. 140)
- What still decides the answer
Whether the partner is a processor or an independent recipient
Table by AdSovereign, CC BY 4.0.
The mandate does not mention consent management platforms or the IAB Europe Transparency and Consent Framework; we found no reference to either in document 14756/26 (Council register). How TCF purposes would map to the six exemptions is therefore open. For the bid-request fields that carry consent today, see our guide to GDPR, ePrivacy and RTB consent signals, and for decoding strings, the TCF consent string decoder.
The pseudonymisation rule may matter more to measurement than any cookie change. If it survives, a clean room partner's legal position would depend on what that partner can do with the data. Our comparison of clean room architectures explains the processor and independent-recipient models.
ePrivacy Regulation status
The ePrivacy Regulation proposal of 10 January 2017 is no longer pending. EUR-Lex marks COM(2017) 10 as withdrawn and gives 6 October 2025 as its end of validity (EUR-Lex, COM(2017) 10). The Directive of 2002, as amended in 2009, remains the law. The Digital Omnibus is now the only live vehicle for changing the cookie rule. For how member states apply Article 5(3) today, see our tracker of cookie banner rules by country.
Where to read the Digital Omnibus text
- Commission proposal: COM(2025) 837 final on EUR-Lex, with the explanatory memorandum (EUR-Lex).
- Council mandate: document 14756/26, a public PDF on the Council register. Bold marks additions and strikethrough marks deletions against the Commission text (Council register).
- Parliament: draft report PE786.818 of 22 June 2026 and the amendment documents listed on the procedure file (Legislative Observatory).
- Regulators: EDPB-EDPS Joint Opinion 2/2026 (EDPB).
A plain-text copy of the mandate loses the strikethrough, so deleted Commission wording reads as if it were kept. Only the PDF layout shows which wording the Council struck.
What to watch next
4 of 4 rows
ITRE-LIBE committee vote | No date on the procedure file (OEIL) | Sets whether Parliament restores the browser signal or the Commission's six-month wait |
Plenary mandate and trilogue start | Not scheduled | The Council said the Irish Presidency will lead talks once Parliament has a position (PPC Land, 25 October 2026) |
End-2026 political target | The European Council asked for all pending omnibus packages to be agreed before the end of 2026, as cited in the Council cover note (PPC Land, 9 October 2026) | Explains the pace; it is not a legal deadline |
Application date | If adopted as in the Council text, cookie rules apply through national laws 24 months after adoption (document 14756/26, p. 158) | Nothing in the cookie rules can apply in 2027 on that text |
ITRE-LIBE committee vote
- Status on 9 November 2026
No date on the procedure file (OEIL)
- Why it matters
Sets whether Parliament restores the browser signal or the Commission's six-month wait
Plenary mandate and trilogue start
- Status on 9 November 2026
Not scheduled
- Why it matters
The Council said the Irish Presidency will lead talks once Parliament has a position (PPC Land, 25 October 2026)
End-2026 political target
- Status on 9 November 2026
The European Council asked for all pending omnibus packages to be agreed before the end of 2026, as cited in the Council cover note (PPC Land, 9 October 2026)
- Why it matters
Explains the pace; it is not a legal deadline
Application date
- Status on 9 November 2026
If adopted as in the Council text, cookie rules apply through national laws 24 months after adoption (document 14756/26, p. 158)
- Why it matters
Nothing in the cookie rules can apply in 2027 on that text
Table by AdSovereign, CC BY 4.0.
The dates of every other 2027 deadline that touches advertising are in our ad tech regulation calendar. The UK changed its own cookie rules separately; see the UK Data (Use and Access) Act guide. The AI Act timetable is covered in EU AI Act and advertising, and the Data Act changes in EU Data Act for ad tech.
FAQ
What is the Digital Omnibus GDPR status today?
What is the Digital Omnibus GDPR timeline?
Will the Digital Omnibus remove cookie banners?
Does the Digital Omnibus make legitimate interest available for ad targeting?
What happened to the ePrivacy Regulation?
How this works on owned infrastructure
The Council text exempts first-party audience counts and contextual ad measurement only while the data stays with the service provider, or with a party acting for it, and is not shared, combined or reused. That condition is about where data lives and who can query it. AdSovereign is an enterprise, on-premise RTB stack (DSP, SSP, exchange and clean room) designed to run measurement, frequency capping and consent-state storage inside a publisher's or advertiser's own environment, so the measurement data does not pool with other clients' data by default. Whether a given setup fits an exemption remains a legal question for each deployment. The architecture page shows where data sits, and the security page describes access controls and logging.
Sources
- European Commission, Proposal for a Regulation as regards the simplification of the digital legislative framework (Digital Omnibus), COM(2025) 837 final (19 November 2025). EUR-Lex. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52025PC0837
- Council of the European Union, document 14756/26, Mandate for negotiations with the European Parliament, outcome of proceedings (22 October 2026; agreed by Coreper 21 October 2026). https://data.consilium.europa.eu/doc/document/ST-14756-2026-INIT/en/pdf
- European Parliament, Legislative Observatory, procedure file 2025/0360(COD) (checked 9 November 2026). https://oeil.europarl.europa.eu/oeil/en/procedure-file?reference=2025%2F0360%28COD%29
- European Parliament, ITRE and LIBE, Draft report PE786.818, rapporteurs Aura Salla and Marina Kaljurand (22 June 2026). https://www.europarl.europa.eu/doceo/document/CJ72-PR-786818_EN.html
- EDPB and EDPS, Joint Opinion 2/2026 on the Digital Omnibus proposal (adopted 10 February 2026). https://www.edpb.europa.eu/system/files/2026-02/edpb_edps_jointopinion_202602_digitalomnibus_en.pdf
- Directive 2002/58/EC (ePrivacy Directive), consolidated version of 19 December 2009, Article 5(3). EUR-Lex. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02002L0058-20091219
- European Commission, Proposal for a Regulation on Privacy and Electronic Communications, COM(2017) 10, procedure record showing withdrawal (end of validity 6 October 2025). EUR-Lex. https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:52017PC0010
- European Parliament, Legislative Observatory, procedure file 2025/0359(COD), Digital Omnibus on AI (checked 9 November 2026). https://oeil.europarl.europa.eu/oeil/en/procedure-file?reference=2025%2F0359%28COD%29
- PPC Land, "EU Council drops cookie signal after Google lobbying - EUR 40-50 bn at stake" (28 June 2026). https://ppc.land/eu-council-drops-cookie-signal-after-google-lobbying-eur-40-50-bn-at-stake/
- PPC Land, "19 groups ask EU to re-insert the cookie banner fix Google lobbied out" (13 September 2026). https://ppc.land/19-groups-ask-eu-to-re-insert-the-cookie-banner-fix-google-lobbied-out/
More sources (6)
- PPC Land, "EU Council draft drops unconditional opt-out from GDPR AI clause" (21 September 2026). https://ppc.land/eu-council-draft-drops-unconditional-opt-out-from-gdpr-ai-clause/
- PPC Land, "EU Council draft cuts cookie re-prompt wait from 6 months to 4" (9 October 2026). https://ppc.land/eu-council-draft-cuts-cookie-re-prompt-wait-from-6-months-to-4/
- PPC Land, "EPP tabled 248 omnibus amendments weakening privacy, noyb finds" (12 October 2026). https://ppc.land/epp-tabled-248-omnibus-amendments-weakening-privacy-noyb-finds/
- PPC Land, "EU Council agrees 4-month cookie re-ask wait for Digital Omnibus talks" (25 October 2026). https://ppc.land/eu-council-agrees-4-month-cookie-re-ask-wait-for-digital-omnibus-talks/
- Taylor Wessing, Megan Lukins, "The Digital Omnibus: cookies, consent and digital advertising" (2 February 2026). https://www.taylorwessing.com/en/global-data-hub/2026/the-digital-omnibus-proposal/gdh---the-digital-omnibus---cookies
- Regulation (EU) 2016/679 (GDPR), Recital 26 and Article 4(1). EUR-Lex. https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
Changelog
- 9 November 2026: tracker created. Status: Council mandate of 21 October 2026 (document 14756/26); Parliament awaiting committee decision; no trilogue.