d8a .tech

Resources / Blog

The EU's new cookie rules: what the Council agreed, and when it could apply

data tech team • #privacy#gdpr#eprivacy#consent#cookies#regulation
Feature image

On 21 October 2026, EU ambassadors agreed the Council’s negotiating mandate on the Digital Omnibus, a 179-page package that rewrites parts of the GDPR, the ePrivacy Directive and the Data Act. For anyone who measures a website, one line matters most: first-party audience measurement would no longer need consent.

It’s the first time all 27 governments have agreed on that. It is also not law. The European Parliament hasn’t adopted its own position, and the two sides still have to negotiate a final text.

This post covers what the Council agreed, when it could apply, why you shouldn’t drop consent for analytics today, and what you can do now.

This is our reading of the Council’s text as reported by PPC Land. It isn’t legal advice; check your setup with your DPO.

What the Council agreed

The cookie rules stay in Article 5(3) of the ePrivacy Directive. Storing or reading information on a device still needs consent, except where it is “solely related to and strictly necessary for” one of six purposes:

  1. Transmitting a communication over a network.
  2. Providing a service the user explicitly requested.
  3. First-party audience measurement: creating “anonymous aggregated information about the usage of an online service”, by the provider or a third party on its behalf, where the data “are not processed for another purpose, shared with third parties or combined with data from third parties”.
  4. Media audience measurement under the European Media Freedom Act.
  5. Maintaining or restoring technical security.
  6. Measuring the display and performance of contextual advertising, with no profiling and no use of past or future activity.

Four other changes come with it:

The package also adds an article on pseudonymised data: data an independent recipient can’t link to a person would not be personal data for that recipient. A processor working on your behalf stays inside the GDPR.

When could it apply?

Not soon. Parliament has no date for its vote, and negotiations start only after it. Once the final text is adopted, the cookie rules still have to be written into each country’s law, with a 24-month deadline. Under the Council’s text, every member state applies them from the same date.

Digital Omnibus · cookie rules

When could the new cookie rules apply?

  1. 19 Nov 2025 · done

    Commission proposes the Digital Omnibus, with cookie rules moved into the GDPR and a browser consent signal.

  2. 18 Jun 2026 · done

    Council drops the browser consent signal.

  3. 21 Oct 2026 · done

    Council agrees its negotiating mandate: six consent-free purposes and a four-month wait after a refusal.

  4. Now

    Not law. Today's national cookie rules still apply in full.

  5. No date yet

    European Parliament adopts its position. It has more than 1,000 amendments to work through.

  6. After that

    Trilogue: Council, Parliament and Commission negotiate the final text. Any line can still change.

  7. Adoption · pick a month

  8. + 24 months · national laws apply

    New cookie rules apply from December 2029

    The cookie rules stay in a directive, so each member state writes them into its own law within 24 months of adoption and applies them from that date.

Dates up to October 2026 from the Council's record, as reported by PPC Land. Nothing later has a date: the default month is an example, not our forecast.

Even with a fast deal in 2027, the new cookie rules realistically wouldn’t apply before 2029.

It’s tempting to read the exemption as permission to remove the banner from your analytics now. That carries real risk:

Regulators can enforce today’s rules today. A setup built for a law that doesn’t exist yet is a setup that breaks the one that does.

How to get ready

You can prepare now without changing your legal position:

  1. Sort your tags by purpose. Separate audience measurement from advertising, remarketing and anything shared with a vendor for its own use. Only the first group could become consent-free.
  2. Keep measurement first-party. The exemption requires that the data isn’t shared with third parties or combined with their data. Analytics that sends raw events to an ad platform won’t qualify.
  3. Own the raw data. If the data lands in your own warehouse, you can show what you collect, what you keep and who gets it.
  4. Plan for aggregated reporting. The exemption speaks of “anonymous aggregated information”. Decide which fields you would drop or aggregate for consent-free traffic.
  5. Check your banner. Make refusing a single click, and check your consent tool can remember a refusal for at least four months.
  6. Watch Parliament. Its position decides how much of this survives.

Where d8a.tech fits

d8a.tech collects your GA4 or Matomo events, or events from its own tracker, and writes them to your BigQuery or ClickHouse, in our EU cloud or self-hosted. The data isn’t passed to Google or shared with anyone else, which is the first-party setup the exemption describes.

d8a.tech Cloud can also work on aggregates only. One setting hides the dimensions that could identify a person, and you switch off external destinations, so the data isn’t sent anywhere else. That matches the exemption’s “anonymous aggregated information” that isn’t “shared with third parties”.

Today, d8a.tech follows your consent setup. With analytics_storage denied, the d8a.tech tracker writes no analytics cookies and uses an in-memory client ID. Click IDs and IP addresses are personal data: you collect them under your own legal basis, and they won’t fit an “anonymous aggregated” exemption. Whether a given configuration qualifies is your call to make with your DPO, under the law that applies on the day.

Our view: this is the right direction

Measuring how people use your own website, kept first-party and aggregated, was never the privacy problem. Cross-site tracking and selling profiles were. For years the rules treated both the same, and a banner on every visit taught people to click whatever makes it go away.

The Council’s text draws the line in a better place: count your own audience without a banner, and ask for consent when data leaves your hands or follows people around. Meanwhile AI models have been trained on much of the public web, and the same package would let AI development rely on legitimate interest. Next to that, treating a page view on your own site as the threat that needs a banner is out of date.

We hope Parliament keeps the exemption. Until it’s law, keep asking for consent.

← Back to Blog

See d8a.tech on your own stack.

Talk to us about your architecture, terms, a partnership or sponsored development. Or start with free Cloud and evaluate it yourself.