Privacy

Audience measurement

When audience measurement is enabled, this blog uses a small, cookieless pageview beacon operated by this site and hosted on Cloudflare to understand which public pages are read, how readers arrive, and the approximate regions and device types represented. The resulting dashboard is private and is used only by the site owner to understand the blog’s audience.

The browser beacon sends:

• the current page path and public page title;
• a random event ID used to reject duplicate submissions; and
• either a same-site referrer path, an external referrer hostname, or direct.

It does not send URL query strings, URL fragments, advertising identifiers, screen details, fonts, or form contents. This blog does not use this analytics system for advertising, cross-site tracking, or the sale of reader data.

Approximate location and visitor counts

The collection service runs on Cloudflare. When the beacon is enabled, Cloudflare necessarily processes the connection IP address and ordinary request headers while serving it. The service uses that transient information to derive:

• an approximate country, region, and city;
• an ASN and network organization;
• coarse browser, operating-system, and device categories; and
• a pseudonymous identifier that is valid only for the current Asia/Tokyo calendar day.

The analytics database does not store the raw IP address, full User-Agent, precise coordinates, or postal code. Daily identifiers are not linked across days. They are estimates rather than identities: shared networks can merge different readers, while VPNs, privacy relays, mobile networks, and address changes can split or relocate one reader.

City and network aggregate groups are retained only when at least three estimated daily visitors share the group. Individual recent-client rows in the private dashboard show country and region, not city or network organization.

Retention

Detailed pageview records are scheduled for deletion after 90 days. Cleanup runs in bounded batches; an operational or provider-quota failure can create a temporary backlog, which is monitored in the private system dashboard. Daily aggregate statistics may be kept indefinitely. Old daily identifier material is removed after it is no longer needed.

Cloudflare D1’s Free plan currently provides a seven-day point-in-time recovery window. Data removed from active tables can therefore remain recoverable by the account owner through Cloudflare’s managed recovery system for up to that additional period.

Opt out on this browser

The beacon honors Global Privacy Control (GPC), the browser’s Do Not Track signal, and the local preference below. Opting out stores only the value 1 under blog.analytics.optout in this site’s local storage. It stops future pageviews from this browser profile; it does not delete previously collected detailed records or aggregates.

Clearing site storage, using private browsing, or switching browser profiles or devices removes this local preference, so opt out again in those cases.