support home

Back to website
Login  Sign up

Googl Fonts e cookie

Buongiorno, ho un dubbio su Google Fonts. Sulle mie policy generate con Iubenda vedo che tra i dati raccolti tramite Google Fonts figurano Cookie e Dati di utilizzo. Per i dati di utilizzo non ho alcun dubbio. Per quanto invece riguarda i cookie mi chiedo di che si tratti, dal momento che testando i siti con gli strumenti per sviluppatori non riesco a trovare alcun cookie riconducibile a GF. Neanche Ghostery sembra accorgersi di nulla...
  • Hai avuto altre notizie in merito, Chiara? Cosa bisogna fare con i google fonts? Basta solo citarli nella privacy policy?
  • Ciao Marianna, nessuna notizia. Ti linko e copia-incollo, però, il testo delle faq relative alla privacy per questo servizio. Anche da questo documento sembrerebbe che Google Fonts non usi cookies. --- What does using the Google Fonts API mean for the privacy of my users? The Google Fonts API is designed to limit the collection, storage, and use of end-user data to what is needed to serve fonts efficiently. Use of Google Fonts is unauthenticated. No cookies are sent by website visitors to the Fonts API. Requests to the Google Fonts API are made to resource-specific domains, such as,, or, so that your requests for fonts are separate from and do not contain any credentials you send to while using other Google services that are authenticated, such as Gmail. In order to serve fonts as quickly and efficiently as possible with the fewest requests, we cache all requests made to our servers so that your browser only contacts us when it needs to. Requests for CSS assets are cached for 1 day. This allows us to update a stylesheet to point to a new version of a font file when it’s updated. This ensures that all visitors to websites using fonts hosted by the Google Fonts API will see the latest fonts within 24 hours of their release. The font files themselves are cached for one year, which is long enough that the entire web gets substantially faster: When millions of websites all link to the same fonts, they are cached after visiting the first website and appear instantly on all other subsequently visited sites. We do sometimes update font files to reduce their file size, increase coverage of languages, and improve the quality of their design. The result is that website visitors send very few requests to Google: we only see 1 CSS request per font family, per day, per browser. We do log records of the CSS and the font file requests, and access to this data is on a need-to-know basis and kept secure. We keep aggregated usage numbers to track how popular font families are, and we publish these aggregates in the Google Fonts Analytics site. From the Google web crawl, we detect which websites are using Google Fonts, and publish this in the Google Fonts BigQuery database. To learn more about the information Google collects and how it is used and secured, see Google's Privacy Policy. For further technical discussion of how Google Fonts serves billions of fonts a day to make the web faster, see this earlier tech talk from the Google Developers YouTube channel.
  • Grazie mille, Chiara. Quindi, a questo punto, basta citarlo nella privacy policy evidentemente. Speriamo risponda anche qualche membro dello staff. Ti aggiorno anch'io se ho altre notizie
Login or Signup to post a comment