we are serving customers within EU where GDPR applies. I wanted to share feedback that our current workflow with Cwicly requires to download the fonts from “google fonts” and add them to the custom fonts manager. Loading Google Fonts directly from their servers is not GDPR compliant as user data get transfered to Google this way.
As an alternative I pitch replacing google fonts with bunny fonts, as the implementation is the same is serverd through CDN too. I guess the change just requires to change the API endpoint of the source. This solution would not require us to download and upload fonts manually & would improve our workflow.
Cwicly stores all Google Fonts that are downloaded via Font Manager locally on your installation. There is no need to download them externally and install them manually as dedicated local fonts.
As long as you use downloaded fonts, there never will be a connection to the Google servers from Cwicly’s side.
The Font Manager uses a locally hosted font library and the font files are stored on your own server. This ensures that they are transmitted securely and without the risk of them being intercepted by third parties.
Interesting project! Your feedback has been addressed, but I got a question for you:
Since connecting to the servers alone involves the IP address, which is seen as private data, what makes the bunny CDN more gdpr compliant than others?
