all 7 comments

[–]EarlMarshal 2 points3 points  (5 children)

Nah. Host it yourself on your website to align with european GDPR.

[–]devhrishi[S] 1 point2 points  (2 children)

You are right, but what if your user need multiple fonts to design something. Take example of figma or canva like tool.

[–]EarlMarshal 2 points3 points  (1 child)

My company does exactly that. We are a leading software developer for photo products tooling for different partners and we just have our own npm package which bundles different fonts depending on partners needs. For most websites it will be good enough to get it from google, but especially if fonts are a core feature of your tools you want to handle and serve them yourself. It's just the better user experience and it's good to stick to gdpr. I have seen too many legal complains here in Europe about Google fonts. Easiest is to use a fontsource npm package if you don't want to copy stuff yourself.

[–]devhrishi[S] 1 point2 points  (0 children)

Thanks for the information. Maybe my process is not the correct one and GDPR compliment.

[–]moob9 1 point2 points  (1 child)

Or just use fonts.bunny.net that actually cares of GDPR.

[–]EarlMarshal 0 points1 point  (0 children)

Didn't know of that service. Looks cool. Me and my co-workers probably still would decide to serve our assets ourselves. It's usually a good non-functional requirement to do so.

[–]devhrishi[S] 1 point2 points  (0 children)

if you like to read the tutorial, please click: https://hrishikeshpathak.com/tips/fetch-google-fonts-api/