Privacy

This is a personal engineering blog. Here's what's collected and why.

First-party analytics

For a successful, non-prefetch GET that serves an HTML page, this site records the page path, referring hostname, country, a daily pseudonymous client ID, a heuristic traffic class (browser, bot, or AI User-Agent), the matched User-Agent rule name when available, device type, the request's network (autonomous system number and organization name, such as an internet provider or cloud host), the values of the Fetch Metadata headers Sec-Fetch-Mode, Sec-Fetch-Dest, Sec-Fetch-Site, and Sec-Fetch-User when a browser sends them, whether the Accept header included HTML, and whether an Accept-Language header was present (the Accept and Accept-Language values themselves are not stored), whether the request is mine, and the UTC observation time. It does not record query strings, full referrer URLs, city, continent, raw IP addresses, or raw User-Agent strings for these edge observations. This request evidence has been collected since September 3, 2026.

The edge daily client ID is the first 128 bits of an HMAC-SHA-256 value derived from the site host, UTC date, IP address, and User-Agent using a secret key. The IP address and User-Agent are processed transiently to create it but are not stored. The ID can link requests within one UTC day; it is not anonymous, does not identify a person, and cannot establish the same client across dates, devices, or networks. Public stats exclude rows marked as mine; owner marking depends on server-side configuration and may not identify every request I make. Recording is best effort and uses no cookies.

New page observations also distinguish external, internal, absent, and unusable referrers. For an internal referrer, only a recognized public blog page path is retained, without query strings or fragments. This supports aggregate reports of movement between pages. Arbitrary internal URLs, API paths, and confirmation or unsubscribe tokens are not retained as referring paths. Older records did not preserve this distinction and remain unknown where the original value was discarded.

The browser-beacon dataset collected before August 26, 2026 remains intact. Its source table stores page path, cleaned referrer host/path, country, city, continent, a daily date-derived IP + User-Agent hash, heuristic traffic and device classes, owner status, and UTC time; it never stored raw IP addresses or raw User-Agent strings. A minimized, source-marked copy is included in public stats so the historical trends are not lost.

First-party analytics rows are retained until I delete them; there is currently no automatic expiration. The source marker distinguishes historical beacon events from newer edge observations.

Cloudflare Web Analytics

Cloudflare Web Analytics is separate from the first-party dataset above. Its JavaScript beacon supplies Cloudflare's performance dashboard and does not feed this site's public stats. Cloudflare may process request and browser data for that service; see Cloudflare's Privacy Policy.

If you request a subscription, your email address is stored in a Cloudflare D1 database and sent to Resend to deliver confirmation and newsletter emails. You become a subscriber after opening the confirmation link and pressing the confirmation button. The signup record may also include the page where you subscribed, an allowlisted campaign source and campaign name, the referring site's hostname, a truncated request IP address, a browser user agent, and request and confirmation times.

To limit unwanted confirmation emails and diagnose delivery failures, the site retains confirmation reservations for seven days. These records contain the email address, a random request identifier, a hashed confirmation token, timestamps, send outcome, and any returned provider message identifier and HTTP status. They are private operational records. An accepted send does not establish that an email reached the inbox. Routine confirmation diagnostics use the request identifier and outcome, without the address, form contents, or tokens.

You can unsubscribe via the link in every newsletter. Confirmation emails also offer a way to block further confirmation requests for up to 90 days. Unsubscribed and bounced addresses, including their suppression state, are purged after 90 days; expired pending signup records are removed by nightly cleanup. An already admitted email may still arrive after an opt-out.

Bot protection

The newsletter signup form uses Cloudflare Turnstile when you submit a request. Turnstile analyses browser and network signals to assess automated abuse. Verification may require interaction and can fail; the form reports a problem and lets you retry. Cloudflare may process data as part of this assessment — see Cloudflare's Privacy Policy.

Error diagnostics

If something breaks in the browser, a small first-party error report may be sent to help debug the problem. Reports include the page path, error message, component name, browser user agent, and coarse Cloudflare request metadata. They do not include email addresses, form contents, cookies, localStorage values, Turnstile tokens, or full URLs with query strings. Error reports are deleted after 30 days.

Other services

No advertising networks, social tracking pixels, or session recording are used. Cloudflare provides site infrastructure, Cloudflare Web Analytics, and Turnstile; Google Fonts supplies fonts.

Contact

Questions? Reach out on X or LinkedIn.

The license for everything published here is on the license page.