This site

Privacy

Reading this site is anonymous. No analytics, no cookies, no account, and nothing you read or open is recorded. Two things you send on purpose do reach the server: a correction, and, if you use the full results page rather than the quick panel, the term you searched for, which travels in the address as with any link.

The short version

  • No analytics of any kind, and no third-party tracking.
  • No cookies are set by this site, so there is no cookie banner to dismiss.
  • No account, no login, no advertising, and nothing is sold or shared.
  • One external service exists, the video, and it is contacted only after you press play.
  • The quick search panel matches inside your browser. The full results page is an ordinary form, so its term travels in the address, as with any link.
  • The correction form is the only thing the site keeps on purpose. It keeps what you type, the part and heading you arrived from, and the arrival time, reference and status field listed below.

No analytics and no third-party tracking

There is no analytics package on this site. No page view counter, no heat map, no session recorder, no advertising pixel, no social media widget, no third-party font service, no embedded comment system and no tag manager. No third-party script runs on any page.

Fonts, styles, images and the search index are all served from this site’s own domain. A content security policy is sent with every page which permits scripts, styles, fonts and connections from this origin only, so an accidental third-party request would be blocked by your browser rather than quietly allowed.

Like any web server, the hosting provider processes the network requests needed to deliver a page. That is unavoidable in order to serve a website at all, and no profile, analytics record or reading history is built from it by this site.

No cookies

This site sets no cookies. There is no consent banner because there is nothing to consent to, and no preference to remember about tracking that does not happen.

The video, and when YouTube is contacted

The overview video is hosted on YouTube. The player is not loaded when a page opens. What you see before you press play is a poster and a play control served from this site, so opening the watch page contacts nobody but this site.

When you press play, and only then, the player is loaded from www.youtube-nocookie.com, YouTube’s privacy-enhanced domain. From that point onward your interaction with the video is between you and YouTube, under their terms and their privacy policy rather than this one. This site receives nothing back: it is not told whether you played the video, how much you watched, or whether you stopped.

If you would rather not contact YouTube at all, the watch page carries the full transcript with chapter headings, and the whole argument is written out across the case pages.

The search index is a single file downloaded from this site the first time you open search. The quick panel matches inside that file, in your browser: what you type there is not transmitted, and it keeps working with no network connection once the index has been fetched.

The full results page is different, and deliberately so. It is an ordinary form that submits to this site, which is what lets it work with scripting disabled and lets a page of results be linked or bookmarked. The consequence is that the term is in the address, and reaches the server answering the request as any address does, where it may appear in ordinary request logs.

This site keeps no search history: nothing you search for is stored, counted or tied to you. If you would rather a term never left the machine at all, the quick panel answers the same index without ever loading that page.

Reading progress stays in your browser

The case index offers an optional record of which parts you have opened from it. It is stored in your browser’s local storage under a single key, ci:case-reading-progress, and it holds nothing but a list of permanent part identifiers such as S04.

It never leaves your device. It is not sent to this site, it is not synchronised between devices, and it is not used to build any profile. Clearing it changes nothing else about the site.

There is a Reset reading progress button on the case hub which removes the key entirely, and clearing site data in your browser has the same effect. Nothing else is stored in local storage, session storage or any other browser store.

The correction form

The corrections form is the only thing this site keeps on purpose. It keeps what you type into it, the part and heading you arrived from, and the three things it adds itself, all listed below. A search term from the full results page also reaches the server, in the address, and is not kept.

What it collects

  • Required: the feedback type, your message, and your choice about publication.
  • Optional: a source web address, your name, and your email address. Every one of these can be left empty, and a correction is taken just as seriously without them. If you leave a field empty, nothing is stored in its place.
  • Context: the part identifier of the page you came from, when you arrive from a link on a section page, and a heading anchor if the address you arrived with carries one. These are a short code such as S04 and an anchor such as in-brief, and they exist so that a correction can be matched to the place it is about. No link on this site puts a heading in the address today, and an anchor is read only when the address also names a part it belongs to.
  • Added by the server: the time the submission arrived and a reference for it, so that a submission can be found, answered and deleted, and a status field which is written once and is the same on every record. Nothing about you is derived from any of the three.

Your network address is used for one purpose: limiting how many submissions a single connection can send in a ten minute window, which is how the form survives without a CAPTCHA. It is held in the server’s memory for the length of that window and is never written to disk, never stored beside your submission, and never logged.

Submission contents are never written to a log file or sent to any monitoring service. There is no third party involved in receiving, storing or reading a submission.

Who sees it, and for how long

  • Submissions are read by Phil Welch alone. They are not shared, published in full, sold, or used for anything other than deciding whether to change a page.
  • A submission is kept while it is being considered and is deleted within twenty-four months of being resolved.
  • If a correction is accepted, the resulting change is published in the changelog as a description of the issue and the decision. Your name appears only if you asked for credit on the form, and your email address never appears.
  • If you gave an email address and want your submission deleted before then, send a second submission saying so and it will be removed.

There is no CAPTCHA on the form. A hidden field that only automated clients fill in and the rate limit described above do that job instead, because a visual puzzle would exclude some of the readers most likely to have something worth saying.

The author’s own contact details

The source document behind this site opens with a personal email address and phone number. Neither is published here, anywhere, and that is deliberate. A private address on a public page is harvested within days and stays harvested for years.

A check runs on every build and fails it if either detail ever appears in the output. The corrections form exists in their place, and the reasoning is recorded in the changelog and on the original document page.

Changes to this page

If this ever stops being accurate, the page will be changed and the change will appear in the changelog like any other. Last reviewed .