nextlevels logo
DEEN

Cookie consent in Germany: § 25 TDDDG explained

Consent in accordance with Section 25 TDDDG, cookie banner, Consent Mode v2 and PIMS

Compliance20 min read
Legally compliant tracking according to TDDDG - cover image in nextlevels design
Legally compliant tracking according to TDDDG - cover image in nextlevels design

If you use web tracking in 2026, you are working at the interface of two sets of rules that are constantly confused: the TDDDG (the law you knew as the TTDSG until May 2024) and the GDPR.

The first determines whether you are allowed to store or read anything at all on your visitors' devices. The second determines what you are allowed to do with the data afterwards. This is exactly where the expensive mistakes happen: an incorrectly built cookie banner can be fined up to 300,000 euros under § 28 TDDDG, and on the GDPR side the range goes considerably higher.

This article shows what legally compliant tracking actually requires: when you need consent under § 25 TDDDG, what a banner must look like to stand up to scrutiny, and how to assess Google Consent Mode v2, the „Pur-Abo“ model, the new consent management services (PIMS) and the still undecided EU cookie reform. It treats cookie consent as a tracking question, not the entire GDPR documentation. And it is professional guidance, not legal advice for individual cases.

Timeline of legal developments: Planet49 2019, BGH 2020, Consent Mode v2 and TDDDG 2024, EinwV 2025, PIMS Consenter 2025
Timeline of legal developments: Planet49 2019, BGH 2020, Consent Mode v2 and TDDDG 2024, EinwV 2025, PIMS Consenter 2025

What applies since when?

Cookie consent under § 25 TDDDG: the rules in chronological order
DateRuleWhat it means for you
1 December 2021TTDSG enters into force (§ 25: consent for device access)Legal basis for cookie banners in Germany
14 May 2024Renamed TDDDG (when the Digital Services Act, DDG, entered into force)§ 25 unchanged; update references in your privacy policy and banner
1 April 2025Consent Management Ordinance (EinwV) enters into forceRecognized consent management services (PIMS) become possible; participation is voluntary
2025/2026EU “Digital Omnibus” proposal (including cookie rules)Not yet applicable law; check the current status before publishing

The principle of § 25(1) TDDDG is strict: every storage or read operation on the user's device requires consent.

Strictly necessary: these cookies work without consent

The exceptions in paragraph 2 are narrow. Access is exempt from consent only if its sole purpose is to transmit a message, or if it is “strictly necessary” for a service explicitly requested by the user to work at all. Typical examples:

  • Session cookie, login status
  • Shopping cart in an online shop
  • Load balancing, security tokens
  • Storing the consent decision itself
  • Language setting actively chosen by the user

A central, often overlooked point: § 25 TDDDG does not recognize legitimate interest as a legal basis. Unlike the processing of data under Art. 6 GDPR, you cannot rely on a balancing of interests to access the device. Either the exception applies, or you need consent. This also covers pure audience measurement. The exception for statistics cookies that was planned at times in the ePrivacy draft never became law – and the Commission finally withdrew the ePrivacy Regulation itself in 2025.

You therefore need an opt-in in particular for:

  • Google Analytics, any audience measurement
  • Marketing and retargeting pixels (e.g. Meta, Google Ads)
  • Google Tag Manager, if it loads tracking
  • Browser fingerprinting, device IDs
  • A/B testing and personalization tools

If in doubt: anything that is not strictly necessary for the explicitly requested service requires consent. The Administrative Court of Hanover shows how far this goes. In its judgment of 19 March 2025 (case no. 10 A 5385/22), it confirmed that even using Google Tag Manager requires prior consent, because merely loading the gtm.js script accesses the device and transfers data to Google. The Tag Manager is simply not privacy-neutral.

Who regulates what: Section 25 TDDDG regulates terminal device access, the GDPR regulates data processing - with fines
Who regulates what: Section 25 TDDDG regulates terminal device access, the GDPR regulates data processing - with fines

TTDSG, TDDDG and GDPR: who regulates what?

First the question of names, because it confuses many people: the TTDSG (Telecommunications Telemedia Data Protection Act) was renamed the TDDDG on 14 May 2024, in full the Telecommunications Digital Services Data Protection Act. This happened as part of the new Digital Services Act (DDG), which transposes the EU Digital Services Act into German law. Nothing changed in substance: the provision that matters for cookies is still § 25, only now it is § 25 TDDDG. If you still have “TTDSG” in mind, you mean the right law under its old name.

More important than the name is the division of labor. § 25 TDDDG governs access to the device: as soon as you store information on a user's device (e.g. set a cookie) or read information stored there, this provision applies – regardless of whether personal data is involved. The GDPR only applies afterwards, to the processing of the data obtained this way.

An example makes the separation tangible: setting an analytics cookie falls under the TDDDG. The subsequent analysis of the resulting usage profile falls under the GDPR. You need both sides to be clean, and each has its own range of fines. Violations of § 25 TDDDG cost up to 300,000 euros under § 28 TDDDG; on the GDPR side, Art. 83 goes up to 20 million euros or 4 per cent of worldwide annual turnover. Both can apply to the same operation at the same time.

The standards have been settled by the highest courts. In 2019, the CJEU ruled in the Planet49 case (C-673/17) that a pre-ticked checkbox is not valid consent. The Federal Court of Justice (BGH) adopted this for Germany on 28 May 2020 (“Cookie-Einwilligung II” judgment, I ZR 7/16). Since then, the rule has been unambiguous: you need an active opt-in. “Continuing to browse counts as consent” is not permitted, and neither are pre-ticked checkboxes.

Consent only holds if it meets four criteria, and each has a typical counterexample. It must be informed: if you ask for consent across the board “for a better experience” without naming tools and purposes, you have missed the mark. It must be freely given: a banner that blocks the page until you accept is coercive.

It must be granular: a single “Accept all” button without a separate choice per purpose is not a real yes. And it must be as easy to withdraw as it was to give: if accepting takes one click but withdrawing takes an email to support, the balance is wrong. This is not to be confused with the withdrawal button under Section 356a BGB, which since 19 June 2026 lets consumers withdraw from a contract concluded online.

The DSK (German Data Protection Conference) specifies these requirements in its guidance for providers of digital services (version 1.2, November 2024), the successor to the former “OH Telemedien”. It is the document the German supervisory authorities rely on in an audit, which makes it the most important reading in practice alongside the statutory text.

These requirements translate into a manageable set of concrete levers. The most important concerns the first layer of the banner: a “Reject” button must sit on an equal footing next to “Accept”, with the same click distance and the same visual weight. The classic that fails in court is the large green “Accept all” button next to a pale, small-print “Settings” link. This counts as a dark pattern and makes the consent challengeable. In the judgment mentioned above, the Administrative Court of Hanover also explicitly required an equivalent “Reject all” option.

The technical behavior behind the banner is just as decisive. Tracking scripts may only load after consent. If you start Google Analytics, the Meta pixel or the Tag Manager as soon as the page loads and only show the banner afterwards, the data has already been collected. The consent then comes too late.

On top of that come granular switches per purpose, a withdrawal option that is as easy to reach as giving consent (e.g. via a permanent “Cookie settings” link in the footer), and documentation of every consent as proof for your accountability obligation. This last point is often forgotten, and in a dispute it is the one that counts. If you want to bring tracking and compliance together properly, it is best to plan this as part of the shop and web architecture, the way we set it up in e-commerce projects, and not as a banner bolted on afterwards.

Legally compliant cookie banner: vulnerable vs. correct design in comparison
Legally compliant cookie banner: vulnerable vs. correct design in comparison

Since 6 March 2024, Google Consent Mode v2 has effectively been a prerequisite for using Google Ads and Google Analytics in the EEA with full functionality. The trigger was the Digital Markets Act, not the TDDDG. What matters is placing it correctly: Consent Mode is a signalling layer between your Consent Management Platform (CMP) and Google. It does not replace consent and is not a legal basis in itself.

In practice, the difference between the two variants matters. In Basic Mode, Google tags are only loaded and fired after the user has consented. Without consent, nothing happens. In Advanced Mode, the tag already loads when the page is opened and sends anonymised, cookieless pings to Google even without consent. Basic Mode is the lower-risk choice from a data protection perspective, because no device access takes place without consent. Advanced Mode delivers more modeled conversion data, but is legally trickier and should be reviewed under data protection law before use.

One point added in 2026: since 15 June 2026, only the Consent Mode ads signals (ad_storage, ad_user_data) decide whether Google Analytics collects ads cookies and IDs and passes them on to Google Ads. The Google Signals setting in Analytics no longer controls this; it now only affects linking with signed-in users for reporting.

For personalization, Google has announced the same step for later in 2026, so far without a fixed date, then via the ad_personalization signal (Google Analytics Help).

A second point from the same announcement is rarely noticed: the IP addresses collected automatically by the Google tag will also flow, encrypted, into the linked Google Ads account and will be subject to the Ads settings and terms there. Google has not yet named a date for this. If you maintain a record of processing activities, you should review the Analytics–Ads link with this in mind. The group of recipients changes there without anyone ticking a box.

For a properly configured CMP setup, this does not change your obligations, but it makes correct signal handover even more important: if you map the consent signal incorrectly, you lose data quality and, in case of doubt, process data without a legal basis. A review of your Consent Mode configuration therefore belongs in your routine once a year.

Google Consent Mode v2: Basic vs. Advanced mode in process comparison
Google Consent Mode v2: Basic vs. Advanced mode in process comparison

Many media sites have introduced the “pay or consent to tracking” model (“Pay or Okay”, „Pur-Abo“) in recent years. The legal situation is nuanced. In its Opinion 08/2024, the European Data Protection Board (EDPB) stated that for large platforms, a merely binary choice between paying and consenting generally does not result in freely given consent. The German supervisory authorities do not reject pay-or-consent models across the board, but tie their admissibility to clear conditions – above all that users can consent to or reject individual processing purposes granularly.

How strict this standard is shows in a decision by the Austrian Federal Administrative Court of 13 August 2025: it declared the blanket consent in the banner of the newspaper Der Standard invalid because it did not allow a granular choice between advertising, profiling and analytics, and referred the case back to the data protection authority. In practice, this means: a pay-or-consent model can be permissible, but it is not a carte blanche. It needs a reasonable fee as a genuine alternative and granular consent. A single yes/no hurdle is not enough.

What many consider settled actually is not. The General Court of the EU dismissed Meta's action against the EDPB opinion as inadmissible on 29 April 2025 (T-319/24) – an opinion under Art. 64 GDPR cannot be challenged on its own. That is not a ruling on the merits, and the matter is not closed either: Meta lodged an appeal on 10 July 2025; a CJEU decision in case C-454/25 P has not yet been issued.

The fine against Meta (€200 million, 23 April 2025) concerned its pay-or-consent model and is based on the Digital Markets Act, not the GDPR. The simultaneous fine against Apple (€500 million) is often mentioned in the same breath, but concerned the anti-steering rules and has nothing to do with consent.

A final CJEU decision or binding EDPB guidelines on “consent or pay” are still pending as of early October 2026 – the EDPB work program for 2026/2027 lists the guidelines as an open item, not even as a consultation draft. Articles citing “new EDPB guidelines” from 2026 do not refer to any verifiable source.

So if you use a pay-or-consent model, you are building on a legal situation that may still shift.

The Consent Management Ordinance (EinwV) entered into force on 1 April 2025 and has remained in force unchanged since. It is based on § 26 TDDDG, and its aim is to relieve users of the flood of banners. The idea: recognized consent management services (PIMS) manage cookie preferences centrally, for example via a browser plugin, so that not every website has to ask individually.

In practice, this is still in its early days. The first recognized service, “Consenter”, developed by the Berlin-based Law & Innovation Technology GmbH, was recognized by the BfDI (Federal Commissioner for Data Protection) on 17 October 2025 and entered in the public register; the corresponding browser plugin has been available since early 2026, and user numbers are so far in the three-digit range.

As of 5 October 2026, Consenter is still the only service entered in the BfDI's public register; actual adoption remains low, and use is voluntary for website operators and users alike. Whether this changes can be checked at any time in the BfDI register – it is the only reliable source for which services are recognized. The sober assessment: PIMS is a topic to watch, but no reason to do without a clean banner today.

Digital Omnibus: what may change

Since November 2025, the European Commission's proposal for the Digital Omnibus package has been on the table, and since then marketing circles have expected cookie banners to soon be history. Developments in 2026 have thoroughly dampened that expectation, and the course of events is worth a closer look.

First, the distinction that almost all expert articles get wrong: the package has two parts. The AI part has passed – Regulation (EU) 2026/1744, published in the Official Journal on 24 July 2026, in force since 27 July 2026. It amends the AI Act and has nothing to do with cookies. If someone tells you “the Omnibus has been adopted, the banners are going away”, they are mixing up the two parts.

The data protection part – and only that part contains the cookie reform – is stuck. Not in a trilogue, but before it: neither institution has a negotiating position yet. In the Council, the Cypriot Presidency's compromise text found no qualified majority in June 2026; since 1 July, Ireland has held the Presidency and is consulting the member states again, among other things on the list of consent-free cookie purposes. As of early October 2026, there is no Council position.

In Parliament, a joint draft report by the ITRE and LIBE committees has been available since 22 June 2026; amendments were tabled on 27 July 2026, spread across nine documents. A committee vote has still not been scheduled, and the procedure status in the Legislative Observatory still reads “Awaiting committee decision”.

What the draft provided for

The Commission draft of November 2025 provided for the following:

  • The cookie rule from Art. 5(3) of the ePrivacy Directive moves into the GDPR (as a new Art. 88a).
  • A list of exceptions for low-risk purposes – such as audience measurement by the operator itself, shopping cart and session cookies, security functions – is to be possible without consent.
  • Rejecting must be possible with one click and on an equal footing with accepting.
  • After a rejection, sites should not be allowed to ask again for around six months.
  • Machine-readable consent signals from the browser must be respected as binding (Art. 88b).

Where the blockade lies

Of all things, the point that would actually have made banners redundant was the first to lose its majority in the Council. In the Presidency's revised compromise text of 18 June 2026 (Council document ST 10677/26, LIMITE, available in the Council's document register), not only Art. 88b was deleted, but the entire inserted block of Art. 88a and Art. 88b. The deletion was backed by Germany, France and Poland, among others, flanked by intensive lobbying against browser signals, which the privacy organization noyb made public.

Formally, nothing has been decided: the text was intended for the Committee of Permanent Representatives on 26 June 2026, but never became the Council's position. The Irish Presidency, in office since July, presented a further revised compromise text on 3 September 2026, which the Council discussed on 11 September.

There, too, Art. 88a and 88b remain deleted, as does the recital on machine-readable signals. The deletion is therefore not an episode of a single Presidency, but the Council's consistent line. This September text has not been officially published; it became public via noyb. In any case, it is not applicable law.

The German Council line is not undisputed within Germany: the Federal Commissioner for Data Protection opposes it. In press release 12/2026, the BfDI argues for using the ongoing Omnibus procedure to anchor cookie managers EU-wide and to make consent signals legally binding – exactly the mechanism the Council deleted.

This is backed by a forsa survey of 1,002 internet users (fieldwork July/August 2025, report August 2026): 60 per cent reject across the board as soon as rejecting is possible with one click, and 66 per cent could imagine using a cookie manager. If you build your banner today, you should factor in these 60 per cent instead of waiting for a reform.

The Council does not support the move into the GDPR either. The cookie rule is to stay in Art. 5(3) of the ePrivacy Directive, but receive an extended, exhaustive list of consent-free purposes there: transmission, an explicitly requested service, anonymous aggregated audience measurement by the provider, audience measurement under Art. 24 EMFA, technical security and, newly, measuring ad delivery and performance without profiling. The exception for fraud detection still included in June has dropped out again.

The result is paradoxical: the Commission wanted to abolish cookie banners, and in the Council it is, among others, the member states with the loudest criticism of banners that are blocking exactly the mechanism that could have replaced them. What will ultimately be adopted is therefore completely open.

Pressure from civil society

The decision now lies with Parliament, and that is exactly where pressure from the other side has recently been directed. On 10 September 2026, an alliance of 19 organizations, companies and academics published an open letter to the Commission, Council and Parliament. It includes the European consumer organization BEUC, the civil rights network EDRi and noyb.

It calls for a strong Art. 88b and legally binding automated privacy signals; as the technical basis, the letter names ADPC and navigator.consent. Corresponding amendments are on the table in Parliament. For practice, this means: the question is open, and it will be decided in the committees.

How the supervisory authorities view the draft is also on record. The EDPB and the European Data Protection Supervisor issued a Joint Opinion 2/2026 on the Digital Omnibus on 11 February 2026. As long as the Council and Parliament have no positions, any statement about “new cookie rules from 2027” is speculation.

For you, this means today: change nothing. § 25 TDDDG continues to apply in the form described above. However, if you already build the way the draft would later require – a reject button on the first layer, granular purposes, clean signal handling – you gain two advantages at once: you are compliant today and will have little to change later. That is exactly the order in which we set up consent configurations.

For implementation, the most important points can be condensed as follows:

  1. Without consent, only set what is strictly necessary for the requested service (§ 25(2) TDDDG), and check this list against the scripts actually loaded.
  2. Load tracking scripts only after consent, with no early start on page load.
  3. Place “Reject” on an equal footing with “Accept” on the first banner layer.
  4. Obtain consent granularly per purpose, with no blanket collective yes and no pre-ticked checkboxes.
  5. Make withdrawal as easy as giving consent (permanent footer link).
  6. Document every consent as proof for your accountability obligation.
  7. Name tools, purposes and providers in the banner and in the privacy policy, and update references from “TTDSG” to “TDDDG”.
  8. Connect Google Consent Mode v2 correctly; if in doubt, use Basic Mode.
  9. Use a pay-or-consent model only with a reasonable fee and granular choice.
  10. Keep an eye on the reform, but don't wait for it: the cookie part of the Digital Omnibus has neither a Council position nor a committee vote in Parliament.

Legally compliant tracking does not require special technology, but it does not tolerate shortcuts. The sequence of consent first, then data collection must be right both technically and organisationally – and this is exactly the pattern behind all three current special topics: Consent Mode v2 is not a free pass, the „Pur-Abo“ is not a carte blanche, and PIMS does not yet abolish the banner.

If you are waiting for cookie banners to disappear, you are still waiting. Until then, you are better off building the banner correctly, ideally together with the marketing and analytics side, so that “legally clean” and “still delivers usable data” don't drift apart. The legal assessment of your specific setup ultimately belongs in the hands of data protection and legal experts.

Frequently asked questions (FAQ)

Only if you use cookies or similar technologies that are not strictly necessary (§ 25(1) TDDDG), e.g. for analytics or marketing. If you only use technically necessary cookies, you don't need a consent banner; you still have to provide information in your privacy policy.

What is the difference between the TTDSG and the TDDDG?

The TDDDG is the TTDSG, renamed on 14 May 2024. The cookie rule in § 25 has remained the same in substance.

Yes. GA4 reads or stores information on the device and is not strictly necessary. Google Consent Mode v2 does not replace consent.

Does “Reject all” have to be on the first layer?

According to the data protection supervisory authorities, rejecting must be as easy as accepting. In practice, this means: “Reject all” on the first layer, designed on an equal footing.

Those that are strictly necessary for the explicitly requested service, e.g. shopping cart, login, language setting, load balancing or security, as well as storing the consent decision itself.

What is the EinwV?

Since 1 April 2025, the Consent Management Ordinance (EinwV) has governed recognized consent management services (PIMS). Participation is voluntary for websites.

Not automatically. What matters is whether information is stored on or read from the device (§ 25 TDDDG) and whether the processing is lawful under the GDPR. Server-side tracking moves the technology, but does not replace consent.


Sources (primary sources):

This article is not legal advice.

Next step

Would your cookie banner stand up to scrutiny?

In a free initial call, we look at your banner and tracking setup and show what should be adjusted on the technical side.