Post by harunur017 on Feb 2, 2024 23:59:30 GMT -5
Let's see how to use the Google Fonts service in different ways: in a non-compliant and GDPR-compliant way to avoid incurring sanctions! Form Google Fonts is Google's freely licensed font library . This is a large collection of fonts that can be used within websites and other applications. The Google Fonts service can be used in two different ways: remotely : by connecting to the Google Fonts server locally : by installing the fonts (from Google Fonts) on your server In Italy , and throughout Europe , the use of Google Fonts is only allowed locally . In fact, in Germany, the Munich court sentenced a website to pay a fine of 100 euros for violating the European privacy regulation .
The website was fined for uploading its fonts using the Google Fonts service remotely . With this method, when the user browses the site itself, his IP is sent to Google's servers without Buy TG Number Data his having given his consent for this purpose. This behavior, as can be deduced from the sentence , is contrary to the indications of the GDPR and translates into a violation subject to sanctions . The most suitable solution to avoid this type of problem is to use the fonts locally , without connecting to an external server. So, essentially, if we want to be GDPR compliant , the answer is: No, we cannot use the Google Fonts remote service .
However, it is possible to download the fonts to upload them to our server and therefore use them locally rather than remotely. Let's see the different ways of use in more detail . How does GDPR violation occur when using Google Fonts remotely? To give an example, this is the code that loads the Open Sans font via Google: <link rel="preconnect" href="https://fonts.googleapis.com"> <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> <link href="https://fonts.googleapis.com/css2?family=Open+Sans:wght@300&display=swap" rel="stylesheet"> Markup Every time the user connects to a website configured in this way, he sends a request from his browser to the fonts.googleapis.com and fonts.gstatic.com servers , to obtain the characters necessary to display the page. This is how Google servers receive your IP address even without your consent. How to use fonts locally on your website without connecting to external servers with the risk of violating the GDPR? A solution like the following allows you to do the same operation but without sending the data to Google :
The website was fined for uploading its fonts using the Google Fonts service remotely . With this method, when the user browses the site itself, his IP is sent to Google's servers without Buy TG Number Data his having given his consent for this purpose. This behavior, as can be deduced from the sentence , is contrary to the indications of the GDPR and translates into a violation subject to sanctions . The most suitable solution to avoid this type of problem is to use the fonts locally , without connecting to an external server. So, essentially, if we want to be GDPR compliant , the answer is: No, we cannot use the Google Fonts remote service .
However, it is possible to download the fonts to upload them to our server and therefore use them locally rather than remotely. Let's see the different ways of use in more detail . How does GDPR violation occur when using Google Fonts remotely? To give an example, this is the code that loads the Open Sans font via Google: <link rel="preconnect" href="https://fonts.googleapis.com"> <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> <link href="https://fonts.googleapis.com/css2?family=Open+Sans:wght@300&display=swap" rel="stylesheet"> Markup Every time the user connects to a website configured in this way, he sends a request from his browser to the fonts.googleapis.com and fonts.gstatic.com servers , to obtain the characters necessary to display the page. This is how Google servers receive your IP address even without your consent. How to use fonts locally on your website without connecting to external servers with the risk of violating the GDPR? A solution like the following allows you to do the same operation but without sending the data to Google :