Skip to content
senn-techsenn-tech
Back to blog
Strategy
Security and data protection2026-11-15· By Franz Senn

Advocate General on Google Fonts: provoked warning waves should not earn damages

On Thursday, 5 November 2026, Advocate General Maciej Szpunar filed his Opinion of the Advocate General in Case C-654/25 at the Court of Justice of the European Union. His recommendation is plain: whoever engineers data-protection breaches through automated mass checks and then derives money claims from them acts in abuse of the law. For website operators in Austria and Germany this is the second leg of a story that began with the Google Fonts warning wave in 2022, whose technical core still sits inside almost every web project.

Dynamic Google Fonts means: the HTML points at font files which the visitor's browser fetches directly from a Google server while the page loads. Every such fetch carries the visitor's IP address to Google in the United States. The operator rarely arranged that transfer on purpose and often did not have it in mind. The alternative is local: the fonts sit on your own server, and the IP address stays inside the house.

What the case file actually holds

The facts are easy to read up on, because the Bundesgerichtshof publishes its reference order (Az. VI ZR 258/24 of 28 August 2025). One plaintiff ran a website with dynamically embedded Google Fonts and had never touched the default setting. A defendant let a webcrawler on his laptop check a large number of websites for exactly that embedding. On every hit the same man visited the found page again, automatically, with a second piece of software built for the purpose, and his own dynamic IP address went to Google USA. A lawyer acting under power of attorney for the crawler operator then sent a standardised warning letter: the Interessengemeinschaft Datenschutz demanded 170.00 euros on an escrow account, deadline 3 November 2022, pointing at damages of up to 2,500.00 euros in comparable cases. The website owner paid on 25 October 2022 and went to court to get the money back. The Amtsgericht awarded the plaintiff 70 euros; on appeal the Landgericht Hannover ordered the defendants to repay the full 170 euros. The Bundesgerichtshof then referred several questions to Luxembourg.

How the warning business runsCrawler scans pageslooking for the dynamicGoogle-Fonts embeddingAutomated secondvisitthe collector’s own IP goesto GoogleStandard warningletter170 euros on an escrowaccountPayment under adeadline25.10.2022, 170 eurostransferredRecovery claimAG and LG Hannover, then theBGHCJEU C-654/25Opinion of 5.11.2026, nojudgment
Six steps that the Bundesgerichtshof records one by one in its order of August 2025. The second step is the legally decisive one: the checker produces the breach he reports afterwards. (Quelle: BGH order VI ZR 258/24)

According to the findings of the Bundesgerichtshof, the defendants sent more than 100,000 of those letters to website owners. The case now in Luxembourg is one single file from a business that paid for itself through volume.

What the Advocate General recommends to the Court

Three lines. Status: reported. They rest on a heise article about the Opinion of 5 November, a search-result summary from dig.watch (page itself not retrievable) and the reference order of the Bundesgerichtshof; we could not read the full text on EUR-Lex from our measuring path:

The first question asks something at the core of data-protection law: is a dynamic IP address automatically personal data when it reaches Google USA through such an automated fetch? Szpunar makes the answer depend on whether the receiving party has means that can reasonably be used to identify the person, and on whether the sender knew or had to know that. The blanket sentence "an IP address is always a personal reference" does not carry that far (our inference from the reported reasoning). What counts is what the recipient can do and what the sender knew.

The second line is the one operators care about: non-material damage under Article 82 GDPR is out of reach when the breach was provoked deliberately and by automation. Whoever triggers the very visit that produces the data transfer cannot build a damages claim on it. Third, the Advocate General classifies the money claims as abuse of law and points at the copyright-troll case law of the Court (heise names the copyright-troll case law but no case number; M.I.C.M., C-597/19, is our assumption, and whether the Opinion cites it we could not read): what decides it is whether the infringement was provoked on purpose in order to force its sanction.

For the reading: an Opinion of the Advocate General is an independent recommendation with advisory status. The Court follows it often and stays free to decide differently. The judgment is still pending, and no date for it is published.

What operators take from this, and what they do not

Anyone running a website today has two separate construction sites. One is the warning risk from 2022. How much of that wave is left we have not measured; if the Court follows the Advocate General, such claims lose their footing by his recommendation (reported). The other site is technical: as long as fonts load externally from Google, one IP address travels to Google on every page call. Whether that still counts as a data-protection breach depends on the answers in C-654/25. Operators get the subject off their desk either way, whatever the judgment says.

That is why we measured the five brand domains under our care, most recently on 15 November 2026:

DomainReferences to Google font servers (HTML and CSS files)Measurement dateMeasurement route
senn-tech.com02026-11-15curl, homepage HTML and linked CSS files
senn-logistik.com02026-11-15curl, homepage HTML and linked CSS files
senn-gruppe.com02026-11-15curl, homepage HTML and linked CSS files
theofficers.at02026-11-15curl, homepage HTML and linked CSS files
insulmaterials.com02026-11-15curl, homepage HTML and linked CSS files

Measured is the count of occurrences of fonts.googleapis.com and fonts.gstatic.com in the delivered HTML of the homepage (HTTP 200) and in the CSS files it links with <link> (one or two per domain), repeated with curl and grep on 15 November 2026; the first run on 6 November gave the same result. We did not check subpages, fonts loaded by JavaScript, cookie banners, embedded third-party content or the network requests a real browser makes. What is established: the HTML and CSS of the five homepages contain no reference to Google font servers. For your own site the same check takes two minutes: reload the page hard in the network tab of the browser tools and filter the requests for fonts.googleapis.com. A hit means you act on it, because the condition is avoidable, not because the Advocate General recommended it.

Whoever does not want to do the switch by hand can order a website review with a handover list; on our own five domains, our measurement found no fonts loaded from Google. Anyone integrating the fonts personally should keep the licence of every font family in view, it sits openly next to the files. Where your own font files already lie in the project, the security and data protection hub belongs on the bookmark: the chain from the font file to the AI answer runs through it. How automated visitors on your own site are handled in general stands in the post about robots.txt as a crawler guardrail.

Why the subject is not finished

One of the referred questions asks whether a breach of the data-protection rules can trigger compensation at all when nobody proves damage. The answer will land across the European legal area, past Google Fonts, in every case of a provocation detected by automation. A company that ties warning letters to data-protection damages should have read the full Opinion before it answers the next payment deadline, in Austria as in Germany.

For daily operation the schedule stays as it was after the Opinion: fonts served locally, third-party content reduced, the check built into the website handover. The legal position has moved, the technique stands where it always stood.

Amounts in the case as the Bundesgerichtshof records themAmount paid170 · euros, transferred 25.10.2022Maximum demanded2500 · euros in damages, from comparable cases02700
About fifteen times as much: what one warned owner paid, and the maximum the association held out in comparable cases. (Quelle: BGH order VI ZR 258/24, facts of the case)

Open points: We could not retrieve the full text of the Opinion on EUR-Lex or the case file on InfoCuria from our measuring path (bot protection, script-rendered page). The date (5 November 2026), the case number and the recommendation rest on heise and dig.watch, so details of the reasoning are not confirmed against the primary text; the reference to C-597/19 is our assumption (heise names only the copyright-troll case law), and whether benefits to later users rule out abuse is unresolved. There is no judgment and no published date for one. Our font measurement covers HTML and CSS of the homepages only.

Read next: Facebook and the Android gallery case in Italy · 15,579 infected sites and what CSP and SRI do about them

Further Reading

Labels: read = fetched by us on 15 Nov 2026; reported = press coverage, primary text not read.

Questions?
Do I have to change something on my site now because a judgment is coming?+

The Court has not decided yet and no hearing date for the judgment is published. How large the warning wave still is today we have not measured. What remains is plain technique: serve the fonts from your own server or drop down to the fonts the operating system already has. The effort depends on the site, and it removes the occasion for such letters whatever the judgment says.

Is the Opinion of the Advocate General already the judgment?+

No. An Advocate General presents an independent recommendation, and the Court stays free to ignore it, although it often follows such Opinions. Until the judgment arrives, one point is still open: whether the Court answers the question about identifiability of an IP address the same way.

How do I find out whether my site loads fonts from Google?+

We ran curl against the homepages of all five domains under our care on 6 and 15 November 2026: zero references to fonts.googleapis.com and fonts.gstatic.com in the delivered HTML and the linked CSS files. For your own site the same command is enough, or the network tab of the browser tools: reload the page once without cache and filter the requests for the Google font servers.