Not GDPR compliant

Hi @agenturmai

At first, thank you for your response and for choosing our theme.

I will redirect this topic to the developer’s board and they will check for the issue.

Kind Regards

Hi @agenturmai

We are sorry for the inconvenience, but actually it’s very easy to dequeue “FontAwesome” CSS and Font files. There is no “hack” for it, you should just do it a correct way (just like you dequeue any other style). Just add this code to your Child Theme functions.php file and that’s it:

function ashe_dequeue_fontawesome() {
	wp_dequeue_style( 'fontawesome' );
}

add_action( 'wp_enqueue_scripts', 'ashe_dequeue_fontawesome', 1000 );

P.S. Please change 1-star rating or just remove it, because Theme works fine, there are NO GDPR issues, if you were doing something wrong, it does NOT mean that the theme is NOT GDPR compliant. And also, you haven’t asked for help so again, please remove this rating.

Thanks for understanding!
Kind Regards, Duke

Just to clarify one thing for you, GDPR compliance can include fonts. That is, if you’re requiring a font, and it’s non-optional, then you are, in fact, sending their data to a 3rd party.

You see, when a font is requested by the user’s browser, their IP is logged by the provider and used for analytics. An IP address is considered identifying information. The question that remains, and note that I cannot answer this for you, is if the requirement of the font is such that is an exception for GDPR or not.

So. Is it a GDPR violation? Sure could be.

Read https://github.com/google/fonts/issues/1495 if you want to have your head explode.

My personal recommendation is to not include all of Font Awesome anyway unless you really need the whole thing.

@ipstenu

Thanks for the answer. All modern themes and plugins include FontAwsome and any of them can dequeue/deregister it (which means it’s optional). Elementor page builder (with 3+ million active installs) uses FontAwesome, does that mean it’s NOT a GDPR compliant?

And also, if this theme and other themes and plugins (using FontAwsome) are “Not GDPR compliant” why are they still available on wp.org?

But if it’s not a big deal than this review should be removed because this is a lie:
I’ve already provided a solution for this.

Even with technical solutions like deregister it was not possible to get rid of fontawesome

P.S. We need to include all FontAwesome because the theme has Icon Select options in Customizer.

Kind Regards, Duke

@wproyal You don’t need to sign your posts (and the forum guidelines ask you not)

All modern themes and plugins include FontAwsome

No they don’t. I review plugins, not even a fourth do.

And also, if this theme and other themes and plugins (using FontAwsome) are “Not GDPR compliant” why are they still available on wp.org?

Because, as I said, they COULD be a violation.

Allow me to quote myself:

So. Is it a GDPR violation? Sure could be.

Bolded the important bit there. It’s a maybe, and depends on context. Which you just provided:

P.S. We need to include all FontAwesome because the theme has Icon Select options in Customizer.

Now what this means is the font is a requirement of your plugin, and that means you should, wait for it, properly disclose the requirements in the readme so people can know what 3rd party services are required.

So. Go make sure your readme is VERY CLEAR about that, and you should be fine.

I’m not a lawyer, though, and neither are you, so I’d recommend hiring one if this becomes a larger concern.