Short answer
This site sets no cookies. Neither first- nor third-party: pages write no cookies to your browser and use no localStorage or similar persistent storage.
The same holds for the cookie's modern relatives: localStorage, sessionStorage, IndexedDB and similar browser stores are equally unused here. The policy does not hide behind the narrow word "cookie"; every kind of client-side persistent record is out of scope.
The sentence is complete in scope: no analytics cookies, no preference cookies, no session cookies, no third-party pixels. There is no need for an 'except strictly necessary' footnote either, because no session or form mechanism exists on the site to necessitate one.
Why cookie-free?
The site is fully static; it needs no sessions, carts, preferences or measurement. The principle the engine teaches in its own privacy/cookie readiness domain is applied here: where there is no tracking, none is pretended — showing a banner while measuring in the background is exactly what this site does not do.
Cookie-freedom has one more practical consequence: the site cannot even store a "cookie preference", because the very mechanism that would hold it does not exist. Your visit leaves no trace in your browser; close the tab and the relationship ends.
So where is the banner?
Because no cookies are used, there is no consent banner; asking consent for nothing would be misleading. This honest state is the cookie-layer counterpart of the site’s claim-safety principle.
Embedded content
Pages embed no external players, social widgets or iframes; hence there is no surface where third parties could drop cookies. Video-related sections consist only of text and downloadable files.
How does a measurement-free site improve, then? Through direct feedback (e-mail), server-side aggregate request counts, and the public measurements of independent tools. Improvement decisions are made by measuring the surface, not by following the individual — the site applying to itself the governance principle it describes.
Technical verification
Anyone can verify this independently: in browser dev-tools, Application → Cookies stays empty for this domain, and the Network tab shows requests to this domain only.
For those taking verification one step further: the page source contains no line writing document.cookie and no construct producing Set-Cookie; the JavaScript file does only interface work — menu, search, copy. Wherever doubt remains, the source code has the last word — and on this site, the source says the same thing the claim does.
For the more rigorous: not a single line in the page source writes document.cookie, and no Set-Cookie header originates from the site's files. The possibility of the hosting layer injecting a technical cookie of its own cannot be reduced to zero — that honest limit is stated here too; if you detect one, report it via the security page's channel and the configuration will be corrected.
What is a cookie? A short definition
A cookie is a small text file a site writes to your browser and reads back on later visits — used to keep sessions open, remember preferences or measure behaviour. The definition sits here only to make one thing plain: this site has none of those three needs and therefore runs none of that machinery.
Browser settings
Should you still wish to harden your browser against all sites: blocking cookies, clearing site data and private windows break nothing here — because there is no storage to break. That is the direct, visitor-facing benefit of a static, tracking-free architecture.
If this ever changes
Should a strictly necessary cookie ever be required, this page will be updated with its name, purpose and lifetime; per release discipline the change enters the manifest records.
The engine's cookie lens
On reviewed sites the engine asks: is there a visible cookie notice, does the notice match actual behaviour, which domains do third-party calls reach? This page is those questions answered for this site: the notice exists (this page), behaviour matches (no cookies), third-party calls are absent.
'Cookie-free' has a cost and we do not hide it: we measure no visitor counts, popular pages or conversions. It is a deliberate trade — the visitor's right not to be tracked was valued above the insight measurement would bring.
Two frequent questions
'How do you remember my language?' We don't: language travels in the address (/ and /en/), nothing is written to your browser. 'Are my downloads tracked?' No: download links are plain file addresses with no redirect or counter service in between.