GDPR Localizer – Smart Google Fonts Local Hosting & DSGVO Compliance
Automatically localizes Google Fonts to comply with GDPR/DSGVO requirements by hosting them on your own server. Set it and forget it.
00
·0 active installs·Updated 3 days agoAs of April 2026, GDPR Localizer is a WordPress GDPR plugin with 0 active installations and a 0/5 rating0. It has been downloaded 227 times in total. Requires WordPress 5.8+ and PHP 7.4+. Available on WordPress.org since 2026. Actively maintained — updated within the last month. Top alternative: Complianz – GDPR/CCPA Cookie Consent.
0/5Rating
0active installs
227total downloads
1 monthsince 2026
Overview
Most GDPR font plugins do one thing: download fonts once. GDPR Localizer goes further. It automatically detects when you update or switch your theme and alerts you instantly — so you always know when to refresh your font cache. It also localizes Gravatars, eliminating the last hidden IP leak most plugins ignore. Set it once, stay in control.
Why choose GDPR Localizer?
Unlike basic solutions, this plugin is designed to be truly “set and forget.” It doesn’t just download fonts; it monitors your site’s environment. If you update your theme version or switch to a new one, the plugin detects the change and prompts you to refresh the font cache to ensure your design stays perfect, fast, and compliant.
Key Features
- Automatic Interception: Seamlessly handles fonts enqueue…
Screenshots
Ratings & Reviews
00 reviews
5 ★
0
4 ★
0
3 ★
0
2 ★
0
1 ★
0
Compatibility
| WordPress | 5.8+ requiredTested up to 6.9.4 |
| PHP | 7.4+ required |
Top Alternatives to GDPR Localizer – Smart Google Fonts…
Frequently Asked Questions
Changelog
1.1.3
- Improved: Enhanced compatibility with block-based themes (FSE), including WordPress 2025.
- Improved: Added theme slug tracking alongside versioning to ensure more reliable cache management during theme switches.
- Enhanced: Added a “Clean” status indicator in the admin dashboard to confirm successful scans on sites already free of external Google Fonts.
- Security: Implemented nonce verification for frontend scan requests to meet the latest WordPress security standards.
- Fixed: Resolved a potential PHP Fatal error related to security function loading order.
Contributors
Plugin data sourced from WordPress.org. Analysis and metrics by PluginSift.