This page describes what this site collects about the people who read it. The short answer is that it collects very little, because it runs no analytics, sets no advertising cookies and has no accounts, forms or comments. The longer answer below says what is left, which is mostly what any web server records in order to serve a page at all.
What is collected
Server logs. Like every web server, the one serving this site records requests: the address requested, the time, an HTTP status, the browser’s user-agent string and the requesting IP address. This is what makes it possible to serve a page, notice that a page is broken, and see that something is being hammered by a badly behaved crawler.
Nothing else. There is no analytics script, no tag manager, no advertising network, no embedded social widget and no tracking pixel on any page. That is a build decision rather than a configuration one: those things are not present in the pages at all.
Cookies
The site sets no cookies for reading it. There is no consent banner because there is nothing to consent to, and a banner asking permission to do nothing would be theatre.
No banner, because there is nothing to ask about.
The one exception is administrative. The publishing system sets a session cookie when somebody signs in to edit the site, which applies to nobody who is only reading it and expires with the session.
What the logs are used for, and for how long
Keeping the site working. Finding pages that return an error, spotting a link that leads nowhere, and noticing abnormal traffic. Logs are not analysed to build a picture of individual visitors, and they are not combined with anything else.
They are kept for a short operational period and then discarded. They are not sold, not shared with an advertising network, and not passed to anybody except where a hosting provider necessarily processes them in order to run the server.
Links that leave this site
Pages here link out, and one page carries a banner that links to a third-party site. Following any outbound link takes a reader somewhere with its own privacy practices, which this site neither controls nor can describe. Nothing about a reader is passed along with the click beyond what a browser sends by default when following any link.
No content is embedded from elsewhere. There are no third-party fonts loaded at request time, no external image hosts and no video embeds, which means no other company receives a request simply because somebody opened a page here.
Why it is built this way
Partly because the alternative would have to be described here, and a privacy page is much easier to write honestly when there is nothing to disclose. Mostly because none of it would be used: a reference site does not need to know which paragraph somebody stopped reading at, and collecting it anyway would be gathering data for no purpose, which is the thing data protection law is most concerned about.
The practical cost of the decision is that there are no visitor numbers for this site. Nobody here knows how many people read any given page, which pages are the popular ones, or where readers arrive from. That is a real loss and it was accepted deliberately.
Rights over data
Where data protection law applies to a reader, the rights it grants apply here in the ordinary way: to ask what is held, to ask for it to be corrected or deleted, and to complain to a supervisory authority.
In practice the answer to the first will usually be that nothing identifiable is held beyond short-lived server logs, which cannot be searched by person. Requests can be sent to the address on the contact page.
Changes to this page
If this site ever starts collecting something it does not collect today, this page changes first and says what and why. A privacy page that describes an earlier version of a site is worse than no page at all, because it is actively misleading rather than merely absent.
The terms covering the material itself, rather than the reader, are on the legal notice.
Questions
Does this site use analytics?
No. There is no analytics script, tag manager, advertising network, social widget or tracking pixel on any page. Those are absent from the pages rather than switched off somewhere in a setting.
Why is there no cookie banner?
Because reading the site sets no cookies, so there is nothing to ask permission for. The only cookie involved is a session cookie for signing in to edit, which never reaches anybody who is only reading.
What is in the server logs?
The address requested, the time, an HTTP status, the browser’s user-agent string and the requesting IP address. They are used to keep the site working, kept for a short operational period and then discarded.
Is anything loaded from other companies?
No. No external fonts at request time, no external image hosts, no video embeds. No other company receives a request simply because somebody opened a page here. Following an outbound link is a separate matter, governed by wherever it leads.
How can data rights be exercised?
By email, through the contact page. The answer will usually be that nothing identifiable is held beyond short-lived server logs, which cannot be searched by person, but the request will be answered.