Cookie policy

No cookies. No banner. Both on purpose.

You did not have to click anything to read this page, and that is not an oversight.

Last updated 10 September 2026.

What this site stores in your browser

Nothing. No cookie, no local storage, no session storage, no IndexedDB, no pixel, no fingerprint. Close the tab and there is no trace that you were here.

Why there is no consent banner

Under article 82 of the French Data Protection Act — the text that implements the ePrivacy directive — consent is required to read from or write to a visitor's device. We do neither, so there is nothing to consent to. The CNIL is explicit that a site using only exempt trackers, or none, should not display a consent request.

A banner here would ask you to approve nothing. That is not compliance, it is a click you pay for with your attention, and it teaches people to accept without reading — which is the opposite of what the rule exists to achieve.

The one thing we removed to be able to say that

Until 10 September 2026 this site loaded its typefaces from Google Fonts. That sets no cookie, but it does send your IP address to a third party before the first word renders. On a site whose whole argument is that nothing should leave your building, that was an own goal.

The three typefaces are now served from this domain. There is no external origin left anywhere on the site, which is precisely what makes the paragraph above true rather than merely well-intentioned.

How to check, in ten seconds

  • Open your browser's developer tools on any page here.
  • Application → Storage is empty. No cookies, no local storage.
  • Network shows every request going to this domain and nowhere else.

And so it stays: scripts/check-privacy.mjs fails our build if an external origin, a cookie or a browser-storage call appears anywhere in the built site. The claim is enforced by the thing that ships the site, not by our memory.

What the server records

Our host keeps ordinary web-server logs, and the demo form stores what you type plus a one-hour rate-limit counter keyed on your IP. That is described in full in the privacy policy. None of it is a cookie and none of it follows you to another site.

If this ever changes

If we ever add measurement, this page changes first, a real consent request appears before anything is set, and refusing will be exactly as easy as accepting. Until you see that, the answer to "what do you track?" is: nothing.

Next step

We hold the same line inside the product.

Local model by default, redaction before anything leaves, and every outbound call on a ledger you can hand to your DPO.