Cookie policy
The short answer is that this site sets no cookies. Not one. What it does store is two small values in your browser's local storage, and because most readers would reasonably call those cookies, they are documented here in full detail.
Last revised 20 July 2026, when the second value was added.
1. Cookies proper
07.1 · NoneA cookie is a small file that a site asks your browser to store and then sends back to the server with every subsequent request. That last part is what makes cookies useful for tracking, and it is why we do not use them. There is no Set-Cookie header anywhere in this site's responses, and you can verify that yourself in your browser's network inspector inside about thirty seconds.
Because we set no cookies, there is no first-party cookie table on this sheet, no third-party cookie table, and no consent management platform. The box you saw when you arrived is not a cookie banner in the legal sense. It is a notice about local storage, shown once, because we would rather over-explain than assume.
2. What is stored instead
07.2 · Local storageLocal storage is a browser feature that keeps named values on your own device. Unlike a cookie, nothing stored there is transmitted with your requests — the only way it can reach a server is if a script deliberately sends it, and no script on this site does. Both values below are written and read entirely by motion/sheetwork.js, which is served from this domain.
| Key | Example value | What it does | Lifetime |
|---|---|---|---|
cv.consent.mode |
all or essential |
Records that you have dismissed the arrival notice, so it does not appear again on every page. The value reflects which button you pressed, though in practice both behave identically because there is no optional processing to switch off. | Until you clear site data |
cv.pages.seen |
7 |
A plain integer that increases by one each time you open a page here, capped at 9999. It exists so we can say honestly that we have some idea whether the site is read, without collecting anything about who is reading it. The number never leaves your browser and we have no way of seeing it. | Until you clear site data |
That is the complete inventory. No identifier is generated, no timestamp is recorded, no page path is stored and no session is reconstructed. If you open the storage inspector in your browser you will find two entries and nothing else.
3. What is not here
07.3 · AbsencesIt is worth listing the things a site of this kind usually contains, because their absence is the point.
- No analytics. No commercial platform, no self-hosted instance, no privacy-respecting alternative. We do not know how many people read the flight sim teardown and we have made peace with that.
- No advertising and no affiliate links. Nothing on this site earns us money when you click it, which also means there is no advertising network with a reason to identify you.
- No content delivery networks. The stylesheet framework, the icon set, both typefaces and every illustration are files on our own server. Your browser makes no request to any other domain while reading this page.
- No embedded video or social widgets. Where we would otherwise embed a clip, we describe what happens in it instead. This is occasionally worse for the reader and always better for the reader's privacy.
- No fingerprinting. We do not read your screen dimensions, installed fonts, canvas output, timezone or anything else that could substitute for an identifier.
- No session recording or heatmaps. Nothing observes your scrolling, your cursor or your clicks.
4. Removing the two values
07.4 · ClearingBoth values can be deleted at any time and the site will work perfectly well without them — the arrival notice will simply appear once more and the counter will restart from one. Nothing breaks and nothing is lost.
| Browser | Route |
|---|---|
| Firefox | Settings, then Privacy & Security, then Cookies and Site Data, then Manage Data. Search for this domain and remove it. |
| Chrome and Edge | Settings, then Privacy and security, then Third-party cookies, then See all site data and permissions. Find this domain and delete. |
| Safari on macOS | Settings, then Privacy, then Manage Website Data. Select this domain and remove. |
| Safari on iOS | Settings app, then Safari, then Advanced, then Website Data. Swipe to delete this domain. |
| Any browser, quickest route | Open the developer tools on this page, go to the storage or application panel, select Local Storage for this domain and delete both entries by hand. |
Private browsing works too. Read the site in a private or incognito window and both values are discarded when you close it. Because we have no analytics, there is no difference whatsoever in what we learn about you either way — which is nothing.
5. Blocking storage entirely
07.5 · RefusalIf your browser blocks local storage for this domain, or if you have disabled it globally, the site still functions. The script that writes these values catches the resulting error and carries on. The only visible consequence is that the arrival notice appears on every page you open, because there is nowhere to record that you have already dismissed it. That is mildly annoying and entirely your right.
Disabling JavaScript altogether also works. Navigation, all seven sheets, every table and every teardown remain readable. You lose the genre filter on the teardowns sheet, the expanding panels on the procedure sheet and the validation on the dispatch form — the form was never going to send anything in any case, as that sheet explains.
6. Server request logs
07.6 · HostingSeparately from anything stored in your browser, our hosting provider records ordinary web server logs: a truncated IP address, a timestamp, the page requested and the response code. This is a function of running a web server rather than a choice we made, and the logs are deleted after fourteen days. We access them only when something is broken. They are described more fully in section three of the privacy policy.
7. Changes and questions
07.7 · ContactIf we ever add a third stored value, this sheet will list it before the value is written, and the revision date at the top will change. The last revision, on 20 July 2026, added cv.pages.seen; before that only the consent value existed. We consider the current arrangement close to the minimum a site can store while still remembering that you have dismissed a notice.
Questions about any of this go to [email protected]. If you find a request to a domain other than ours while reading this site, we would genuinely like to know, because it would be a mistake rather than a decision.