Cookies Policy
This site sets no cookies. Not strictly-necessary ones, not analytics ones, none. There is no consent banner because there is nothing to consent to.
How traffic is counted instead
Every request is written to the server's log with a visitor identifier: a short hash of the requesting address, the browser's user-agent string, and the current UTC day, keyed by a secret the server generates at startup and keeps only in memory.
Two properties follow, and they are the reason for doing it this way:
- It cannot follow you between days. The day is part of what is hashed, so the same visitor gets an unrelated identifier tomorrow. Counting unique visitors works within a day and is meaningless across days — by construction, not by policy.
- It cannot be reversed. The key is never written down and is discarded when the server restarts, so nobody can take an old log and work out which addresses produced which identifiers.
The trade-off is honest: this measures roughly, and a restart starts a fresh count. That is the cost of not tracking people, and it is worth paying.
What this does not cover
Page-performance measurements sent by your browser, and anything you type into the contact form, are covered by the Privacy Policy.