Privacy: Cookies, Server Logs and the Correction Form

No cookie is set by this site, for any purpose, including the ones a consent banner normally asks about. Nothing is written to browser storage: not local storage, not session storage, not an indexed database. There is no analytics package of any kind, so no page view, session, scroll depth or click is counted anywhere.

No script on any page makes a network request. The interactive parts of this record (the course-handicap calculator, the odds calculator, the founding-claims comparison and the plotted map) all do their arithmetic in the browser on data that arrived with the page. None of them sends a value anywhere, which is also why they keep working with the network disconnected.

Nothing is loaded from another company's servers either. The typefaces are served from this domain rather than from a font network, so opening a page does not tell a font provider which page was opened. There is no embedded video player, no social widget, no comment system, no tag manager and no advertising script.

That list is not a promise about intent; it is a description of the code that ships. The distinction matters, because a privacy notice that describes an ambition rather than a build is worth nothing to the person reading it.

Asking a web server for a page necessarily tells that server something, and this is the one place where data about a reader exists at all. The hosting provider's web server writes an access log in the ordinary way: the address the request came from, the moment it arrived, the path asked for, the status returned, the number of bytes sent, and the browser's own self-description.

That log is what keeps a site serviceable: it is how a broken link, a failing image or an attack is found at all. It is not read as an audience measure, it is not joined to anything else, it is not used to build a profile, and it is not passed to a third party for either purpose.

How long the log is kept is set by the hosting provider rather than by this publication, and no figure is printed here for it, because a number invented for the sake of completeness is worse than an acknowledged gap. Anyone who needs the exact retention can ask, and the answer will be the host's, quoted as the host's.

The correction form on the contact page has no server behind it, and that is a design decision rather than an omission. Submitting it opens the reader's own mail programme with the fields already written into a message. Nothing is transmitted until the reader sends that message themselves, and it goes by ordinary email rather than through this site.

The practical consequence is worth spelling out. A form that posts to a server means trusting the server; a form that composes a message means the reader can read exactly what is about to be sent, edit it, or close the window. It also means no database of submissions exists here to be lost or requested.

A message that does arrive is treated as correspondence: it is read, it may be acted on by changing a page, and it is kept only as long as that takes. Correspondence is not added to a mailing list, because there is no mailing list.

One figure on this site, the plotted record of historic courses, is published in a form other sites may embed. Two things follow from that, in opposite directions.

When the figure appears on somebody else's page, this server receives a request for it in the normal way, and the access log above is the whole of what results. The figure itself carries no tracking of any kind, so it cannot be used to observe a reader across the sites that embed it, which is the usual reason to be wary of an embedded thing.

The framed figure reports one number back to the page around it: its own height, so the frame can be sized to fit. The message is checked against the expected origin before it is accepted, and it contains nothing except that measurement.

Two links on this site lead to another company's website. Following either one takes the reader to a site with its own privacy practices, which this record has neither sight of nor influence over. Both are ordinary links: nothing about the reader is passed along with the click beyond what any browser sends when it follows a link.

The betting section is the part where this matters most, because a reader who acts on it will end up with an operator rather than here. That section is written to explain how markets settle rather than to recommend a place to bet, and the same section carries the reasons to be careful about doing so at all.

Questions about this page, and requests about anything in the access log, go to [email protected], the same address the contact page uses.

A request about a server log needs enough detail to find the entries (a rough time and the address the requests came from) because a log is indexed by neither name nor account, there being neither. Where the retention period has already passed, the honest answer is that there is nothing left to find.

If any statement on this page stops being true of the code, the page is the thing that is wrong, and a note saying so is the most useful message this address can receive.