# Privacy Notice

> What readership telemetry and the contact form send, how self-hosted analytics work without cookies, and how to opt out or request deletion.

- **Kind:** Standing Legal Document
- **Author:** Colin Wolff
- **Effective:** 2026-11-20
- **Updated:** 2026-11-21
- **Canonical:** https://colinwolff.dev/legal/privacy
- **Markdown:** https://colinwolff.dev/legal/privacy.md

---

## The short version

This site uses first-party, cookieless analytics powered by self-hosted **Rotameter** (`analytics.wolff.industries`). No cookies are set, no cross-site tracking exists, no third-party scripts load on normal reading pages, and raw visitor IP addresses are never stored. Aggregate readership metrics appear publicly at [/analytics](https://colinwolff.dev/analytics).

For contact inquiries, the only personal data that ever arrives is what you type into the contact form, and it exists in two places afterwards: a mail service's relay and an inbox.

## What is kept on your device

Two optional keys in `localStorage`, both strictly local unless you opt out:

- `cw-theme` (`light` or `dark`): your colour-theme choice. Choosing automatic mode removes the key.
- `rotameter_ignore` (`true`): opt-out flag read before the analytics beacon fires. Toggle it in one click on [/analytics](https://colinwolff.dev/analytics) (or run `localStorage.setItem('rotameter_ignore', 'true')` in your browser console) to stop pageviews and link clicks from being sent.

No cookies are set by this site. Global Privacy Control (`Sec-GPC: 1`) is also honored server-side: matching requests are dropped before ingestion. The contact form carries a Cloudflare Turnstile challenge, which is Cloudflare's code running on this page and may set its own cookies under [Cloudflare's cookie policy](https://www.cloudflare.com/privacypolicy/).

## First-party readership analytics

Every HTML page includes an inline first-party beacon that sends pageviews, `404` hits, external link clicks (`outbound_click`), and file downloads (`file_download`) to same-origin `/api/e` on production hosts.

1. **Same-origin Worker proxy.** `/api/e` drops requests from local development or disallowed hosts, strips raw headers down to coarse Cloudflare metadata (`CF-IPCountry`, region code, connecting IP, `User-Agent`, `Sec-GPC`), and forwards the event over a private Cloudflare Tunnel gated by Zero Trust Access to self-hosted Rotameter.
2. **Daily HMAC-SHA256 visitor hashing.** Rotameter computes a one-way daily rotating `HMAC-SHA256(daily_salt, site_id || ip || user_agent)` purely in memory to count unique visitors per day and `30`-minute visits, then discards the IP address immediately. Raw IPs are never written to SQLite or application logs.
3. **Public aggregate reporting.** Only non-personal aggregates (visitors, pageviews, visits, referrers, paths, coarse country codes, browser/OS family) are retained and shown on [/analytics](https://colinwolff.dev/analytics).

## The contact form

When you submit the form, these fields travel to the server: **name** (up to 80 characters), **email**
(up to 120), **subject** (one of four fixed categories), and **message** (20 to 4000 characters).
There is also a hidden field for spam detection; if it has content the submission is accepted and
discarded without being read.

The submission is then:

1. **Verified by Cloudflare Turnstile.** The challenge token, this site's secret key and your IP
   address are sent to `challenges.cloudflare.com` so Cloudflare can answer whether the challenge
   passed. The IP address is part of that check and nothing else — it is not stored by this site.
2. **Relayed by Mailgun.** The four fields above are sent to Mailgun's API, which delivers one
   plain-text email to the address belonging to this site. Your email address is set as the reply-to.
3. **Delivered to an inbox and read.** That is the only place the message persists. Nothing is written
   to a database, a key-value store or a log by this site: the handler has no storage path and does not
   log message content.

If the submission fails, you are redirected to an error page whose URL carries a short reason code
(`input`, `challenge`, `transport` and so on). Reason codes are not personal data.

## Request metadata

The Worker receives the standard Cloudflare request headers — the data centre that answered, a request
identifier, the protocol, the country and network of the connecting address. The `/status` page shows
a subset of this **to you, about your own request**, because that is the point of the page: telling you
which edge answered and how long it took. It is served with `Cache-Control: private, no-store` and
`noindex`, is not written anywhere, and is not shown to anyone else.

## Who processes data

- **Cloudflare** — hosting, the Turnstile challenge, and the network in front of it.
  [Privacy policy](https://www.cloudflare.com/privacypolicy/)
- **Mailgun** — delivery of contact-form email.
  [Privacy policy](https://www.mailgun.com/privacy-policy/)

No other third party receives anything. Contact messages are not written to any CRM, and except for the Turnstile script on `/contact`, no script or asset ever loads from a third-party domain.

## How long it is kept

Contact email stays in the receiving mailbox until it is deleted, and in Mailgun's records for as long as their retention policy specifies. Aggregate readership rollups stay in self-hosted SQLite, while raw normalized events follow configured site retention (`365` days) with zero stored IP addresses or user-level profiles.

## Deleting it, or asking about it

Email [contact@colinwolff.dev](mailto:contact@colinwolff.dev) and ask. A message you sent can be
deleted; you will be told when it has been. If you want to know whether a particular message is still
held, that question is answerable the same way.

## Children

This site is written for adults working in engineering. It is not directed at children and knowingly
collects nothing from them.

## Changes

Material changes to how data is handled get a new effective date on this page.
