Law on your own website

No. The Telemediengesetz was replaced by the Digitale-Dienste-Gesetz on 14 May 2024. The correct reference is Section 5 DDG.

Usually three places on the same page are affected: the heading of the provider identification (Section 5 DDG), liability for own content (Section 7(1) DDG) and the reference to monitoring duties (Sections 8 to 10 DDG). Anyone publishing journalistic-editorial content also cites Section 18(2) MStV — no longer Section 55(2) RStV.

An outdated imprint is not a catastrophe, but it is the first thing a competitor or a warning-letter firm looks at. Fixing it takes minutes.

Better not. The Munich Regional Court I ruled on 20 January 2022 (case 3 O 17493/20) that dynamic embedding without consent breaches the GDPR; a wave of warning letters followed.

The question is not settled — in 2025 the Federal Court of Justice referred core questions to the European Court of Justice (VI ZR 258/24). More relevant in practice is a different decision: since the ruling of 27 March 2025 (I ZR 186/17), GDPR breaches are also actionable under competition law. Competitors can act, not only affected visitors.

The fix costs nothing: download the fonts once and serve them from your own server. With Next.js, `next/font/google` does this at build time — visitors' browsers then never contact Google.

This is an assessment of the legal situation, not legal advice.

Only if you load something that requires consent. If you run no audience measurement and no advertising scripts, you do not need one.

The relevant provision is Section 25(1) TDDDG: storing or reading information on the terminal device requires consent. Strictly necessary operations are exempt under Section 25(2) — session, security, storing the consent decision itself. The former TTDSG has been called TDDDG since the same reform.

If you do need a banner: withdrawing consent must be as easy as giving it. An accept button in the banner and a hidden opt-out in the privacy policy does not meet that.