Privacy
Privacy
A static site with no tracker, no analytics script and no advertising. Here is what remains, described plainly.
This page describes what The Burn-In Desk records about the people who read it. The short answer is almost nothing, and the reason is structural: the desk is a set of static pages, and a static page runs no code between the reader and the text.
What a static page can even record
The desk operates no reader accounts, no comment fields and no signup forms, because a static page has nothing server-side to process them with. A visit consists of a request for a file, and the page itself is the whole exchange the desk controls. The machinery that delivers the file may keep its own request records. This page does not describe that machinery, because the desk writes pages and does not document the layer in front of them.
No downloads, no download trail
The desk serves no disk images, no checksums and no torrents. It is not the Overclockix project and does not distribute that project, and the front page figure states it plainly: zero disk images served here. A download is a transaction that leaves a record at both ends. There is no download on this site to leave one, and the release record page treats published releases as history, not as files on offer.
Where do the front page numbers come from?
From archives, not from readers. The four figures on the front page come from the DistroWatch record for Overclockix, whose own last update is dated February 8, 2026 and which the desk consulted on September 5, 2026, corroborated against the Internet Archive capture index for this domain. Those dates describe what the desk read and when. Nothing in that process counts visits, because counting visits is not what the desk does with numbers.
What the desk keeps, act by act
| Act | What the desk keeps | What leaves the reader's machine |
|---|---|---|
| Reading any page | Nothing keyed to a reader; the page is the exchange | A file request, handled by machinery this page does not document |
| Following an external link | No list of who left | A direct connection to a site with its own rules |
| Writing to the contact address | The site has no reader database to add a name to | A message the reader chose to send |
A mail exchange is the one act here where a reader identifies themselves, and it happens because they decided to write, not because a page required it.
What happens when you follow a link out?
The desk's statements stop at its own pages. When a subject calls for an outside tool, the desk points at the tool's own site and stops there; from the first click onward, that site's rules govern. The SystemRescue homepage describes a Linux rescue toolkit, formerly SystemRescueCd, that runs from a CD, DVD or USB stick instead of requiring an installation, though installing it to the hard disk is possible. The project states that its sources sit on GitLab under the GPLv3 license, which means anyone can read the code; the license does not do the reading for them. What that homepage publishes is documentation, a quick start guide, usage chapters, partitioning and LVM guides, and a tool list. A statement about what that site records about its visitors is not among the pages it lists, and this desk does not describe one on its behalf. Tools of this kind sit alongside the desk's maintained live toolkits notes.
How to check this page against its sources
Do not take this page's word for its own thinness. The sources and method page says where each figure on this desk came from; pick the DistroWatch record and read both dates yourself. If a claim here is wrong, the contact page takes a plain correction, and a correction that arrives becomes a change to a public page rather than a line in a private file.
system-rescue.org is the homepage of SystemRescue, a Linux rescue toolkit formerly called SystemRescueCd, run from a CD, DVD or USB stick to administer or repair a system and its data after a crash. The site publishes a quick start guide, chapters on basic and advanced use, disk partitioning and LVM guides, and a list of the included system tools. The project's sources are on GitLab under the GPLv3 license.