Dear user,
Thank you for contacting iubenda Support Team.
Google Fonts does not install cookies, but if you use it through API calls, some final user data (such as IP address) are gathered, archived, and can be used for analytics purposes. Additionally, it may be possible for Google to track end users via their browser fingerprint crossed and other Google services they use.
Although this is not cookie-related, you must inform users of any tracking technology in use on your site and obtain their consent before using it.
You can find more info here: https://developers.google.com/fonts/faq#what_does_using_the_google_fonts_api_mean_for_the_privacy_of_my_users.
This means you need to add the “Google Fonts” service in your Privacy Policy and think of a way to block it.
Since most of the time Google Fonts is integrated via CSS and not via a real javascript snippet, there is no solution to “block it”.
An alternative solution could be integrating the font and loading it directly from your hosting. This will prevent the data from passing through Google servers and skipping the tracking.
Another solution, quite technical and used as an example, could be to load the font through an asynchronous call in Javascript using a library suggested by Google, called Web Font Loader- more info here: https://github.com/typekit/webfontloader.
In this way, you could set both our Cookie Solution and the loading of the font so that it is released only when the preference (consent) has been given.
You can verify the “callback” part in the Cookie Solution test script created at this link: https://personal.iubenda.com/daniele.comarca/ShareX/share/provacsgooglefonts.html
On this page, you can see that the font changes only after consent has been given when the font is actually downloaded. Try to consider this example and apply it to your specific situation.
Don’t hesitate to contact me should you have additional questions.