Cookies and Measurement

One entry for each request: the IP address it came from, the address requested with any labels in it, the page that linked to it, the browser’s user-agent string and the time.

Amazon CloudFront writes it for us, and we keep it in AWS’s Mumbai region. It is deleted automatically after 90 days.

Three fields for each request: the date, the request’s random identifier and the country it came from, worked out from the IP address. It holds no IP address and is deleted after 14 days.

We use it only to count page views by broad region: India, the UK, the US and Canada, Europe, and the rest of the world. We never count by city. Only page views our script reports are counted, so opting out leaves you out.

Counts, such as how often each page is read and which sites and links sent visits. Also to keep the site secure, to filter out automated crawlers and to find errors. We do not use the logs to identify or follow anyone, and we do not combine them with any other source to do so.

Daily totals made from the logs, with no IP address or browser details, so we can compare over time.

An IP address can be personal data. We process it for our legitimate interests in running, securing and improving the website. You can object: see your rights.

How you reached the page: from another site or app, from another page on this site (and that page’s path, never its query), or by reloading or going back. We count moves between pages this way, never whole visits.

The link’s text (first 60 characters), the page it leads to, and where it sits on the page. For a contact card’s “Send a Message”, also its topic.

The site and page it leads to, with no query, plus the link’s text and where it sits. A link to the Chrome Web Store or the Edge Add-ons store is marked as such. For a Calendly link, also the labels that name our page and the link’s position.

The address, which is always one of ours, and where it sits on the page.

The file’s path, the link’s text and where it sits on the page.

The form’s name and the button’s text.

The form’s name.

The form’s name, and how long you actively used the page, rounded down to 0, 5, 15, 30, 60, 120 or 300 seconds. Also the topic you chose and, if you made one, your choice in “What best describes you?”. Never your name, email, company or message.

The form’s name, the field’s name and the type of problem, never what you entered.

The form’s name and the same rounded time.

The depth reached, and whole seconds since the page loaded.

The number of seconds.

The video’s short name, and the second it started from.

The video’s short name and the share reached.

The missing address, and what linked to it: a page on this site, only the other site’s domain, or “direct”.

The error message (first 180 characters), and the failing script’s address and line.

Each measure’s name, value and rating, and whether your device is touch-first (mobile) or not (desktop).

If your browser sends either signal, the script sends no events at all, with nothing to set here.

The script sends nothing. The pages work without it.

To object to the access log too, ask us.