A cookie policy with almost nothing on it

The tools write nothing. No cookie, no local storage entry, no session storage entry. Nothing you paste is preserved between visits, and no preference, draft or usage history is kept on your device by any tool here.

A single third-party service sets cookies: Google Analytics, loaded on every page to measure page views. Two cookies, named individually in the next section, are the entire footprint.

There are no advertising cookies, no retargeting pixels, no social embeds and no data broker tags on any page. Nothing loaded here follows you to another site.

Both are first-party, stored against this site's own domain rather than a shared advertising domain, which is what limits their reach to this site alone.

_ga

Distinguishes browsers so a returning visit is not counted as a distinct person. Google's default lifetime for it is two years.

_ga_ followed by a stream identifier

Maintains analytics session state for this specific property. The same default lifetime applies.

Contents

A randomly generated identifier and session timestamps. No name, no address, and nothing entered into a tool.

This site is a large collection of narrow tools, and analytics resolves the one question that determines what gets built next: which of them are actually used. A page nobody opens does not warrant expansion. A page with sustained traffic warrants being written properly.

That is the complete purpose. The measurement is of pages, not of people. No profile is constructed, no audience segment is exported, and nothing is sold. The distinction between measuring a page and profiling a visitor is the one that matters here, and this site stays firmly on the first side of it.

Two things sound similar and are structurally separate. Analytics records that a page was requested. Text entered into a tool is not part of that record under either processing model.

Under local processing the text never leaves your device, so no third party has any opportunity to observe it. Under server processing it travels in its own request to this site's endpoint, which the analytics library has no visibility into. Neither path places submitted text in an analytics event, and this is a consequence of how the requests are structured rather than a configuration choice that could drift.

Typefaces are loaded from Google Fonts. That sets no cookie, but it is a request to an external server, which means those servers observe the connection in the ordinary way any web server observes a request for a file.

It appears here because a cookie policy listing only cookies can leave a materially incomplete impression of what a page loads. Analytics and fonts together are the complete set of external requests any page on this site issues.

Every tool on this site operates identically with these cookies blocked. Nothing is gated behind analytics and no capability degrades without it, so blocking carries no functional cost to you.

Clear

Use your browser's clear site data control and select this site. Both cookies are removed immediately.

Block

Block third-party scripts in browser settings, which prevents the analytics library loading in the first place.

Content blocker

An extension of that kind covers analytics generally across every site rather than this one alone.

Opt out at source

Google publishes a browser add-on that opts you out of Google Analytics measurement on every site that uses it.

It would be easy to present a first-party cookie as harmless by definition. The more accurate account is narrower. The identifier in _ga is random and carries no name, address or submitted text, but it is still an identifier: for as long as it persists, requests carrying it are recognisable as coming from the same browser.

What bounds that is scope rather than content. Because the cookie is first-party, it is readable only on this site's own domain, so it cannot be used to recognise you on a different site. Because nothing here collects a name, an email or an account, there is no record on this side for that identifier to be joined to. And because the data is used to count page views rather than to build a profile, nothing is assembled against it.

Those are properties of how this site is built, not assurances about what identifiers can do in general. On a site that also collected an email address, the same cookie would carry very different weight, which is precisely why the absences described in the privacy policy matter more than the cookie list does.

This page describes what the site loads as it stands. If a further service is introduced, or analytics is removed, this page is revised in the same change. A cookie policy that does not match the page it appears on is a defect rather than a formality.

The separate question of what happens to text submitted to a tool is covered by the privacy policy. Questions about either go through the contact page.