In January, 2022 a German court ruled that a website owner was in breach of GDPR and should pay a € 100,- fine, because embedded Google Fonts were used, essentially transferring the user’s personal data (IP address) without the user’s prior consent.
When an external (i.e. loaded from another server, besides your own) resource is embedded into a webpage, it basically means that the resource behaves as if it’s loaded from the same server hosting the webpage.
Why is using embedded resources in breach of GDPR?
Because of the way the internet works. When a browser (i.e. computer) requests a file (e.g. an image or a font file), the server needs the IP address of that computer to send it back. All these requests (including the IP address) are logged in a so-called
Once this IP address leaves the European Union, your website is violating the GDPR.
What does this plugin do?
GDPRess scans your homepage for 3rd party scripts (JS) and stylesheets (CSS), and:
- Allows you to download or exclude them from downloading,
- Parses the stylesheets for loaded font files, downloads them, and rewrites the stylesheet to use the local copies,
- Makes sure the local copies of each script/stylesheet are used in your site’s frontend.
In short, it makes sure no requests are made to external/embedded/3rd party scripts and stylesheets.
- Upload the plugin files to the
/wp-content/plugins/gdpr-pressdirectory, or install the plugin through the WordPress plugins screen directly.
- Activate the plugin through the ‘Plugins’ screen in WordPress
- Use the Settings -> GDPRess screen to configure the plugin
Can I remove/preload stylesheets and/or scripts with this plugin?
No, because there are other plugins (like Asset Cleanup or Autoptimize) that are already excellent at that.
GDPRess downloaded a stylesheet/script, but I’m still seeing requests to font files loaded by the stylesheet?
GDPRess parses the stylesheet for defined src urls. But if it somehow missed it, I’d love to hear about that, because that might be a bug. Please head over to the support forum and submit a ticket, and include the full URL to the external stylesheet.
Will this plugin allow me to use Google Analytics in compliance with GDPR?
No, because much more is needed than just downloading analytics.js/gtag.js to your server. To use Google Analytics in compliance with GDPR, you need CAOS Pro.
Col·laboradors i desenvolupadors
«GDPRess | Eliminate external requests to increase GDPR compliance» és programari de codi obert. La següent gent ha col·laborat en aquesta extensió.Col·laboradors
“GDPRess | Eliminate external requests to increase GDPR compliance” s'ha traduït a 4 configuracions regionals. Gràcies als traductos per les seves aportacions.
Tradueix “GDPRess | Eliminate external requests to increase GDPR compliance” a la teva llengua.
Interessats en el desenvolupament?
Navegueu pel codi, baixeu-vos el repositori SVN, o subscriviu-vos al registre de desenvolupament per fisl de subscripció RSS.
Registre de canvis
- Fixed: call to undefined function download_url().
- Fixed: GDPRess now runs before OMGF/CAOS, so e.g. OMGF Pro can optimize previously externally hosted stylesheets.
- Fixed: Protocol (//) and Root (/) relative URLs shouldn’t be interpreted as external URLs.
- Fixed: Let CAOS/OMGF handle their files, if these plugins are active.
- Added: Run a quick scan on each page to see if new external (3rd party) requests are present on that page!
- Added: Test Mode (enabled by Default) to allow users to first test the optimizations before releasing them to the public.
- Fixed: Don’t use WP_Filesystem to get and put file contents.
- Added: Google Fonts support
- When many Font Families or Font Styles are detected, GDPR Press will suggest to use OMGF to optimize the request before downloading it.
- Fixed several bugs, notices and warnings.
- Added: tooltip next to success message.
- Fixed: tooltip-icon line height.
- Fixed: Conflicts with several caching/optimization plugins:
- WP Rocket
- W3 Total Cache
- WP Optimize
- Fixed: several warnings and notices.
- First release!