You can read every page on this site without creating an account, accepting cookies or handing over any personal detail. This page explains the little that happens behind the scenes when you visit, what that activity is used for, and where this site's responsibility ends.

What can this page tell you, and what can't it?

This page describes only what has been checked in the way this site is actually built. It does not name an organisation behind the site, and it does not state how long visit counts or hosting records are kept, because no retention period has been verified. Where a detail is not set out below, treat it as unconfirmed rather than assuming it.

The site also has no contact channels. There is no form, no mailing list, no comment box and no account sign-up. Because of this, please don't send personal information in response to anything that appears to come from this site through another channel. Nothing here asks you for it.

Several things are confirmed to be absent. No third-party analytics service is used. No files are loaded from outside hosts. No cookies are set. Visitor data is not shared with advertising networks, data brokers or outside analytics services. These absences are why this site asks for no consent, no account and no personal detail.

How does this site actually work when you visit?

  • Self-contained pages. Every file a page needs to display comes from this site's own domain. While you read, your browser is not sending requests to outside hosts.
  • Locally embedded fonts. The typefaces are served from this domain rather than fetched from an external font service. As a result, no outside party learns that you opened a page.
  • First-party visit beacon. This runs only when you arrive from a search engine. It records the page path, the type of event, the name of the referring search engine and the text of any outbound button you click. The data is used only to count page views and outbound clicks, and for nothing else. It uses no cookies and is not passed to outside analytics services.
  • First-party outbound redirect. When you follow an outbound link, it first goes to an address on this domain and is then redirected to the partner. No stored visitor data is handed to the partner along the way.
  • Outbound links to third-party sites. Following a link opens a separate site. That site receives the request directly from your browser and keeps its own record of it. This site does not control that site's privacy practices, so check its own policy before you share anything there.
  • Static hosting on a content delivery network. The site is a set of static files served by a content delivery network. As the hosting provider, the network processes the technical data of every request, such as the information your browser sends to fetch a page.

In practice, browsing this site exposes only routine request data to the hosting network. It also produces a simple visit count when you arrive from a search engine. Once you click through to a partner, you are on someone else's site, and their own practices apply from that point on.