Block Font Awesome

Hello @kateeba,

While it shouldn’t be necessary to block the loading of this font from the Bootstrap CDN, as it is not quite the same as, for instance, connecting to the Google Fonts API: you could always opt to go for a self-hosted implementation such as the one described here: https://fontawesome.com/docs/web/setup/host-yourself/webfonts

Hope it helps!
Kind regards,
Jarno

Hello Jarno,

Thank you. Your answer helped me.

Elena

Hi,

I have the same question:
Is there a simple way to block fontawesome with complianz in the script center? Many themes and plugins are loading fontawesome automatically and so it would be a nice option.

@jarnovos That is very interesting for me: Why is it not necessary to block fontawesome? In which way is it different to using google fonts?

Regards

• This reply was modified 2 years, 6 months ago by philwied.

Hi @philwied,

Please note that this should not be interpreted as legal advice, to be certain we would always recommend reaching out to a legal professional.

Both the use of the Google Fonts API as well as the Font Awesome CDN can be avoided if you simply serve these files locally, from your own webserver. This would prevent the request to an external server and is the recommended approach.

For Google Fonts an API call is made to request and download the font files and CSS assets. This is the tricky part; does this API request send anything related to personal data, according to the GDPR?

Kind regards,
Jarno

• This reply was modified 2 years, 6 months ago by jarnovos.

Thank you for the info.

Is it possible, to block ALL requests according to Font Awesome with Complianz. Maybe to add some line of codes to the script center, that blocks all requests to MaxCDN URL?

As I already mentioned, Font Awesome is loaded by some themes and plugins by default and I have to stop this, before hosting Font Awesome locally.

There is a way to add Google Fonts with complianz in the assistant. Would be a nice feature to add the same for Font Awesome.

Regards

Hi @philwied,

As the Font Awesome CDN in your case is being requested as a result of using a specific plugin or theme, we’d recommend reaching out to them so that they can offer the possibility for you to switch to the locally hosted variant.

Let’s say you have an @import url statement to request the Font Awesome font, inside a CSS file from your theme. We can’t specifically isolate that @import url statement and remove it from the CSS file. We’d have to block the entire theme CSS file, but this is almost certainly not what you want as this would have a significant impact on the layout of your site prior to user consent.

Kind regards,
Jarno