GDPR incompliant usage of Google Fonts

I found the action hooks to add custom stylesheets, so basically, we just need a filter to disable Google Fonts from emails and web views (similarly to the filters you already offer to disable incompliant tracking).

For bypassing readers, these are the actions hooks:

• fluentform_email_header
• fluentcrm_view_on_browser_head.

This issue has incorrectly been marked as resolved (without an answer).

Hello @karlemilnikka,

Thank you for your suggestion regarding GDPR incompliant usage of Google Fonts. I will forward it to our developers so if possible they will add a filter in the future updates to disable Google Fonts from emails and web views.

Thank you.

Thanks. And even better would be if Google Fonts were automatically loaded from the WordPress server. That would let everyone use Google Fonts without compliance issues.

Thank you for your suggestion!

• This reply was modified 1 year, 10 months ago by Tahmid ul Karim.

Please stop incorrectly marking the issue as resolved until there’s a solution (or the part about 100?% GDPR compliance has been changed).

The GDPR compliance issue persists in the 2.7.0 release. So does the currently incorrect statement about full GDPR compliance.

The font issue persists with the 2.7.1 release. Do you have any ETA for when it will be addressed, @tahmidulkarim?

Hi @karlemilnikka,

I cannot provide any ETA at this moment. I will forward it to our developers again. Hopefully, they will address it within the next update.

Thank you.

Hi @tahmidulkarim.

I see. Thanks for the reply.

I wrote a small workaround-snippet to use while waiting for an official solution.

Keep in mind! This is an unofficial workaround. Do NOT use it on a live site without rigorous testing for your specific site. Feel free to report any issues on Github.

Hi @karlemilnikka,

We have replaced Google fonts with bunnycdn fonts to make it GDPR compliant.

Thank you.

Hi @tahmidulkarim.

That’s great! Do you have an ETA for when the compliant version will roll out?

Hi @karlemilnikka,

The update is already released. Please check the version – 2.7.40

Thank you.

Thanks. I read the changelog and there was no mention of any GDPR compliance improvements or changes to font handling.

I’ve checked the new version and it’s a step in the right direction. This fix is however currently not working at all. If you want to solve the web-view the same way I did (which is more of a workaround), you need to change line 1086 in ExternalPages.php from

$content = str_replace('https://fonts.googleapis.com/css2', 'https://fonts.bunny.net/css', $content);

to

$content = str_replace('https://fonts.googleapis.com/css', 'https://fonts.bunny.net/css', $content);

The 2.7.40 update doesn’t address the fonts in the emails (just the web-view). Check my Github snippet for more info.