Why this site has no cookie banner
No analytics, no pixels, no session recorder. The public pages set zero cookies, which means there is nothing to ask consent for — and one fewer thing between a reader and the content.
Consent banners exist because sites set cookies that are not strictly necessary. Remove the cookies and the banner stops being required — not hidden, not made smaller, not required.
What we do not run
No analytics platform. No advertising or conversion pixels. No session recorder, heatmap tool, A/B testing framework or embedded social widget. Each of these sets identifiers under Article 5(3) of the ePrivacy Directive, and each would oblige us to interrupt every first visit with a dialogue.
What that costs
It costs us the funnel. We do not know which section a reader stopped at or which page preceded an enquiry. That is a genuine loss and it is worth naming honestly rather than pretending analytics were never useful.
What we get back is a page that renders its content immediately, with no third-party script in the critical path and no modal between a reader and the first paragraph. For a site whose job is to be read and believed, that is the better trade.
The one cookie that exists
Signing in to the administration area sets a single session cookie: HTTP-only, Secure, SameSite=Lax, expiring after eight hours. It is strictly necessary — the console cannot function without it — so it needs no consent, and it is never set for a visitor who does not sign in.
Server logs
Our server keeps standard access logs: IP address, path, status code, timestamp, retained for thirty days. That is processing under legitimate interest for security and troubleshooting, not a cookie, and it is disclosed in the privacy policy rather than buried.
The general point
Most consent banners are a symptom. Before adding one, it is worth asking which of the tools that made it necessary is genuinely earning its place — and for a small site the answer is often none of them.