Google Fonts check
Check if a website loads external Google Fonts (GDPR-relevant).
How this tool works
Checks if a website loads Google Fonts externally via fonts.googleapis.com or fonts.gstatic.com. Since the LG Munich ruling (Az. 3 O 17493/20, January 2022), dynamically loading Google Fonts without consent is a GDPR violation because the visitor IP is transmitted to Google (USA).
Typical use cases
- Check own website for GDPR-compliant font loading
- Check client sites for Google Fonts legal risk before takeover
- After theme change, check if new external fonts are loaded
- Compliance check for German company websites
Frequently asked questions
Why are external Google Fonts a GDPR issue?
When loading from fonts.googleapis.com, the visitor IP is transmitted to Google servers (USA). This is data transfer to a third country without legal basis — actionable per the LG Munich ruling.
How do I load Google Fonts GDPR-compliant?
Download the fonts and serve them from your own server (self-hosting): place the woff2 files in your own directory and declare them via @font-face in your own CSS. No IP address leaves the site on page load after that.
Are CSS @import inclusions also detected?
Yes — both link tags in the HTML head and @import statements in inline styles are detected.
What about other font services (Typekit, FontAwesome)?
These are also detected and listed under "Other external font services". They also transmit IP addresses and are GDPR-relevant.
Are JS-loaded font inclusions detected?
Only if the link is in the initial HTML source. Dynamically loaded fonts via JavaScript (e.g. Web Font Loader) are not captured.
How high is the legal risk?
After the LG Munich ruling, thousands of cease-and-desist letters were sent. LG Munich I awarded the plaintiff a total of 100 EUR in damages (case 3 O 17493/20). Since 2023 serial warnings are restricted, but the risk remains.
Related tools
Continuous monitoring vs. one-shot?
XICTRAQ monitors uptime, SSL, security headers, GDPR and performance 24/7. Free plan, no credit card.