Skip to main content

Privacy policy

I collect some basic data about visits to my websites, to help me decide what to write about next. I gather statistics in aggregate, and I don’t collect any information about specific visitors.

For example, I can see that 100 people read a post, but I can’t see (a) who those 100 people were nor (b) if you were one of them.

What data I collect

Whenever you visit a page, I use a tracking pixel to record the following anonymised information:

I don’t record your IP address or user agent, because those might allow me to identify a specific person.

Anonymous session identifier

The session identifier is a tool to help me count unique visitors on the site. To do this, I need to be able to correlate hits within the same visitor. If I got three hits in quick succession, did they come from three people looking at one page each, or one person looking at three pages?

I create an anonymous session identifier which gets attached to each hit. This is a randomly-assigned UUID that’s attached to all requests coming from your (IP address, User-Agent) combination for the next 24 hours. At the end of the day, that identifier expires and your next visit will be attached to a different session identifier.

This means that I can see that there was a person who looked at a particular set of pages on one day, but (a) I don’t know who that person was and (b) I can’t see what that person looked at the previous or next days.

Third parties

The tracking pixel is served from my web server. I don’t share the information I get from it – that only lives on my web server and personal computers.

I don’t use any third-party analytics frameworks like Google Analytics, Piwik, and Fathom.

This site is hosted on a mixture of Netlify and Linode. They can see what pages you’re visiting, and they have separate privacy policies. (Netlify; Akamai, who own Linode.)


I don’t use any.