vibrance
Book a call

Cookies, consent and embedded services: what § 25 TDDDG and the GDPR mean for websites

Whether a website needs a cookie banner does not depend on the word "cookie" but on whether information is stored on or read from visitors' devices and whether data flows to third parties. This article explains the two sets of rules that apply, the key court decisions and practical ways to get by with as few consents as possible.

by Kilian Dickmann, Founder and ownerPublished on 7 min read

Few elements have changed the look of websites in recent years as much as the cookie banner. Many operators add one as a precaution; others leave it out without knowing whether they need it. Both can be avoided by separating the two questions the law asks: may the visitor’s device be accessed? And may the personal data that results be processed?

Two sets of rules, two questions

§ 25 TDDDG: access to the device

§ 25 of the German Telecommunications Digital Services Data Protection Act implements Art. 5(3) of the European ePrivacy Directive [1] [3]. Under it, storing information on the user’s device and accessing information already stored there are only permitted if the user has consented on the basis of clear and comprehensive information.

The rule is technology-neutral. It covers cookies as well as the browser’s local storage (localStorage, sessionStorage), tracking pixels and methods that read characteristics of the device in order to recognise it. It applies regardless of whether personal data is involved; the Court of Justice of the European Union made that clear in 2019 in the Planet49 case [4].

Under § 25(2) TDDDG, no consent is needed if

  1. the sole purpose is the transmission of a message over a public telecommunications network, or
  2. the storage or access is strictly necessary for the provider to supply a digital service explicitly requested by the user [1].

The second exception covers, for example, a shopping basket, a login, the chosen language or the stored decision about a banner itself. According to the supervisory authorities, audience measurement, advertising and profiling generally do not fall under it [10].

GDPR: processing personal data

If personal data such as the IP address is processed in the course of this access, or independently of it, the General Data Protection Regulation also applies [2]. It requires a legal basis under Art. 6 for every processing operation, such as consent, performance of a contract or a legitimate interest, and transparency under Art. 13 in the form of a privacy policy.

The two tests are separate. A website can manage without cookies and still need a legal basis under the GDPR, for example because loading an external font transmits the IP address to a third party. Conversely, technically necessary storage can be permitted under § 25(2) TDDDG without consent, while the subsequent processing has to be assessed under the GDPR.

Under Art. 4(11) GDPR, consent is a freely given, specific, informed and unambiguous indication of wishes by a statement or by a clear affirmative action [2]. This and the case law give rise to several requirements:

  • Active choice. A pre-ticked box is not consent. The CJEU decided this in Planet49, followed by the German Federal Court of Justice [4] [5].
  • Continuing to browse or scroll is not enough. The European Data Protection Board does not regard it as a clear affirmative action [11].
  • A real choice. Rejecting must be as easy as accepting. The German supervisory authorities consider it impermissible if rejection is only possible on a second layer while acceptance takes one click [10].
  • Specificity and information. Whoever consents must know which providers are integrated and for what purposes.
  • Withdrawal. Withdrawing must be as easy as giving consent (Art. 7(3) GDPR), in practice for example through a permanently available “cookie settings” link [2].
  • Demonstrability. The controller must be able to show that consent was given (Art. 7(1) GDPR).

A banner that only informs (“This website uses cookies”) and offers nothing but “OK” does not meet these requirements. It is either unnecessary, because nothing requiring consent happens, or insufficient, because there is no real choice.

Embedded services: fonts, maps, videos, calendars

Many data flows do not result from the operator’s own cookies but from embedded third-party content. If a page loads a font, a map, a video or a booking widget directly from someone else’s server, that server necessarily learns the visitor’s IP address and often further browser characteristics.

The case law

In 2019 the CJEU held that a website operator who embeds a third party’s plugin can be jointly responsible for collecting the data and transmitting it to that third party (Fashion ID) [6]. For this part of the processing, the operator therefore needs a legal basis of its own and must provide information.

A 2022 judgment of the Regional Court of Munich I drew a lot of attention: according to it, transmitting the IP address to Google when loading Google Fonts without consent was unlawful; the court awarded the claimant 100 euros in non-material damages and pointed out that the fonts can also be hosted locally [7]. Afterwards, some individuals sent out claim letters in large numbers. In 2023 the same court ruled in such a case that systematically visiting websites in order to generate claims is an abuse of rights [8]. The CJEU has also made clear that a mere infringement of the GDPR is not enough for a claim to damages; damage must actually have occurred, even though there is no threshold of seriousness [9].

For operators, this means less an acute liability risk than a clear design rule: anything transmitted to third parties without consent needs a sound legal basis, and for many embedded services a legitimate interest is hard to establish.

Practical solutions

Element Data-minimising solution
Web fonts Store the font files on your own server and load them from there. For common free fonts, the licences generally allow this.
Maps A static image of the map with a link to the map service, or loading the interactive map only after a click (“two-click solution”).
Videos Preview image on your own server, load the video only after a click; check the providers’ more privacy-friendly embedding options.
Booking and calendar services Load only after an explicit action, with a short note about the provider and the data transfer.
Social media content Plain links instead of embedded posts or buttons.
Audience measurement Methods without storage on the device and without profiling, or deliberately doing without; otherwise consent.

The two-click solution connects both sets of rules: the click is the action with which visitors explicitly request the service and consent; no data flows before it.

Transfers to third countries

Many of these providers are based in the United States. Since 10 July 2023, the Commission’s adequacy decision on the EU-US Data Privacy Framework has applied [12]. Transfers to companies certified under this framework have since been possible without additional safeguards. For providers that are not certified, standard contractual clauses in particular come into consideration. Neither changes the prior question of whether access to the device requires consent under § 25 TDDDG.

When a website needs no banner at all

A banner is not an end in itself. A website that

  • stores no information on the device that is not strictly necessary,
  • loads fonts and images from its own server,
  • embeds external services only after a click and
  • does without audience measurement that accesses the device,

can do without a consent banner. It still needs a complete privacy policy, because hosting, a contact form or sending email also process personal data. For many small businesses this is the simpler route: visitors see the content immediately, and the number of places where something can go wrong is small.

Checklist

  1. Which cookies and storage entries does the website actually set? A check with the browser’s developer tools in a new, empty profile shows this.
  2. Which connections to third-party servers are made when the page first loads, before any interaction?
  3. Can fonts, images and scripts be loaded from your own server?
  4. Are maps, videos and booking services only loaded after a click?
  5. If a banner is needed: are accepting and rejecting equivalent, the providers named and the settings available again at any time?
  6. Does the privacy policy name all services actually used, with purpose, legal basis and, where applicable, third-country transfer?

Conclusion

The legal position is more complex than a single banner suggests, but it is manageable. What matters is a sober inventory of what the website actually does technically. It is often easier to avoid data flows than to secure them with consents. Where third-party services are genuinely needed, embedding them after a click is the approach that best combines usability and legal certainty.

Frequently asked questions

Does every website need a cookie banner?
No. Consent is only needed if information that is not strictly necessary is stored on or read from the device, or if data flows to third parties without another legal basis. A site that hosts its fonts locally and loads external services only after a click often needs no banner.
Is a banner with only an "OK" button permitted?
Not if anything requiring consent happens on the website. Rejecting must be as easy as accepting, and continuing to browse or scroll is not consent.
May I use Google Fonts?
Yes, most safely hosted locally on your own server. Loading them from Google's servers transmits the IP address; in 2022 the Regional Court of Munich I held this to be unlawful without consent.

Sources

The numbers in square brackets in the text refer to this list. Online sources last checked in November 2026.

  1. [1]Telecommunications Digital Services Data Protection Act (TDDDG), § 25 Protection of privacy in terminal equipment. www.gesetze-im-internet.de/ttdsg/__25.html
  2. [2]Regulation (EU) 2016/679 (General Data Protection Regulation, GDPR), in particular Art. 4(11), Art. 6, Art. 7, Art. 13, Art. 26, Art. 82. eur-lex.europa.eu/eli/reg/2016/679/oj
  3. [3]Directive 2002/58/EC (Directive on privacy and electronic communications), Art. 5(3). eur-lex.europa.eu/eli/dir/2002/58/oj
  4. [4]CJEU, judgment of 1 October 2019, C-673/17 (Planet49), ECLI:EU:C:2019:801. curia.europa.eu/juris/liste.jsf?num=C-673/17
  5. [5]German Federal Court of Justice (BGH), judgment of 28 May 2020, I ZR 7/16 (Cookie consent II).
  6. [6]CJEU, judgment of 29 July 2019, C-40/17 (Fashion ID), ECLI:EU:C:2019:629. curia.europa.eu/juris/liste.jsf?num=C-40/17
  7. [7]Regional Court (LG) Munich I, judgment of 20 January 2022, 3 O 17493/20 (Google Fonts).
  8. [8]Regional Court (LG) Munich I, judgment of 30 March 2023, 4 O 13063/22 (mass Google Fonts claims).
  9. [9]CJEU, judgment of 4 May 2023, C-300/21 (Österreichische Post), ECLI:EU:C:2023:370. curia.europa.eu/juris/liste.jsf?num=C-300/21
  10. [10]German Data Protection Conference (DSK), Guidance for providers of digital services (OH Digitale Dienste), version 1.2, November 2024. datenschutzkonferenz-online.de/media/oh/OH_Digitale_Dienste.pdf
  11. [11]European Data Protection Board (EDPB), Guidelines 05/2020 on consent under Regulation 2016/679, version 1.1, 4 May 2020. www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-052020-consent-under-regulation-2016679_en
  12. [12]Commission Implementing Decision (EU) 2023/1795 of 10 July 2023 on the adequate level of protection under the EU-US Data Privacy Framework. eur-lex.europa.eu/eli/dec_impl/2023/1795/oj

About the author

Kilian Dickmann, Founder and owner

Designs and builds websites for small businesses and writes here about design, technology, accessibility and data protection in practice.

More insights

Questions about your own site?

In a free thirty-minute call we look at it together.