Privacy policy

 

published:  August 2, 2020
last modified: December 30, 2020

This site and its owner do NOT store your personal information in any way. However, the site does use certain externally hosted services, each of which has its own privacy policies and methods of complying with applicable privacy regulations.

Notes about external services

Cloudflare Browser Insights

This site’s traffic goes through Cloudflare and is configured to use its Browser Insights tool. Cloudflare says Browser Insights “collects the bare minimum amount of information, timing metrics, to show customers how their websites perform” and that “Cloudflare does not track individual end-users [sic] across our customers’ Internet properties.” For more details, see this Cloudflare support article and the Cloudflare blog post, “Introducing Browser Insights.”

FastComments

This site uses FastComments for commenting. For more details, please refer to the FastComments privacy policy.

Fathom Analytics

This site uses Fathom Analytics, which does not store your personal data in any way. Please refer also to my article, “Fathom Analytics: Count on it.”

Google Fonts

When I learned that the use of Google Fonts served from Google transmit a visitor’s apparently not anonymized IP address1 to Google, I quit using this product (and suggesting to others that they use it) and, instead, served from my own site any typefaces that aren’t part of the so-called “system fonts stack.”

Other considerations

Embedded videos

I no longer embed YouTube or other sites’ videos, since they can and do transmit personal information through cookies. In the two instances where I formerly did—“Some curmudgeonish thoughts” and “Coherence and COVID-19”—I replaced them with clearly identified links to their original locations, and footnoted each link with a reference and link to this privacy policy.

Twitter content

I do not embed tweets, since doing so makes the embedded tweets transmit personal information through cookies. Instead, each tweet is shown as a screen capture linked to its original location. For accessibility-respecting purposes, each such screen capture has a plain-text version of the tweet’s content in its ALT attribute.


  1. For the discussion that convinced me to go this route after my initial skepticism about its necessity, see the Google Fonts GitHub issue, “GDPR compliance.” ↩︎