You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently VIVO uses the Google Fonts API. And although a legal complaint campaign about this failed in Austria not too long ago, it can be assumed that this is not GDPR-compliant. If I see this correctly, the only compliant solution would be to host the fonts locally.
Is your feature request related to a problem? Please describe.
Currently VIVO uses the Google Fonts API. And although a legal complaint campaign about this failed in Austria not too long ago, it can be assumed that this is not GDPR-compliant. If I see this correctly, the only compliant solution would be to host the fonts locally.
https://www.dataguidance.com/news/austria-dsb-finds-google-violation-gdpr-lack
German documentation of a legal case based on the use of Google fonts: https://www.ra-plutte.de/lg-muenchen-dynamische-einbindung-google-web-fonts-ist-dsgvo/ -> court stated that using it without a consent banner/button is not GDPR compliant.
Describe the solution you'd like
Replace Google fonts with a non-tracked solution, e.g. locally hosted fonts.
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: