This site sets no cookie
A cookie policy usually runs to several tables. This one fits in a sentence, and the rest of the page explains how that sentence is kept.
This site sets no cookie
No cookie, and nothing standing in for one
This site sets no cookie: none technical, none for analytics, none for advertising. Nor does it write to your browser's local or session storage, and it reads nothing from them.
It embeds no analytics tool, no tracking script, no pixel, and builds no browser fingerprint meant to recognise you.
Why you saw no banner
Consent is required to read or write information on your device when that operation is not strictly necessary to the service you asked for. This site does neither: it has nothing to obtain consent for.
A banner on a site that tracks nothing is not a precaution, it is decoration — and it teaches visitors to click without reading.
The only cookie that ever existed, and why it was removed
The site's internationalisation library set a language cookie, NEXT_LOCALE, by default. It was observed in production on 13 September 2026, then disabled: it contradicted the commitment made on the Privacy page, and the commitment was worth more than the cookie.
What that costs, precisely: since the language is always present in the address — /fr/… or /en/… —, the cookie only served to direct a visit arriving at the root address. Without it, that choice follows the language header sent by your browser, that is, the preference you actually declared, rather than the memory of an earlier visit.
What the site uses instead
The language is carried by the address of every page. Fonts are served from this domain, and no image, script or stylesheet comes from another domain: your browser contacts no third party while you read this site.
Rate limiting on the forms has to recognise a caller from one request to the next. It sets no cookie for that: the server computes a truncated fingerprint, salted with a value drawn at start-up and never stored. Nothing is written in your browser, and the fingerprint disappears on restart.
How this promise is verified
It is not merely stated, it is measured. An automated check inspects the site's real responses and fails if any of them sets a cookie; another fails if a third-party resource appears in a page. Both are blocking: they stop the release.
That is the difference between a policy and a control. A policy contradicts itself quietly; a control refuses the delivery.
If a cookie became necessary
This page would be changed before it was set, not after. A strictly necessary cookie would be named here, with its purpose and its lifetime; any other use, analytics included, would require prior consent, as easy to refuse as to give.