Home /Page
Privacy policy
What this site collects, which is almost nothing, and why.
This is a static site. It is generated in advance as plain HTML files and served as they are. There is no application, no database and no user account system behind it.
What the site does not do
- No cookies are set. The site does not use cookies for any purpose, so there is no consent banner, because there is nothing to consent to.
- No analytics. There is no analytics package, no tag manager and no visitor tracking of any kind.
- No third-party requests. Pages load nothing from other domains — no external fonts, no scripts, no advertising, no embedded video or maps, no social widgets. Opening a page here contacts this site and nothing else.
- No forms. There is no contact form, no newsletter sign-up, no search box that posts anywhere, and no comments. Nothing on the site collects personal data.
- No accounts. Nothing to register for, nothing to log in to.
Server logs
The hosting provider serving these files will, like any web server, record ordinary request information — IP address, timestamp, requested path, user agent — for the purpose of delivering the site and protecting it from abuse. That processing is the hosting provider’s, and it is generic to web hosting rather than specific to this site.
If you email the address on the contact page, that message and your email address are held in an ordinary mailbox for as long as needed to answer you. They are not added to any list, not used for marketing, and not passed to anyone else. Ask and the correspondence will be deleted.
External links
Pages link to external sources — legislation, standards bodies, HSE guidance, museums and
technical publishers. Those sites have their own privacy practices and this policy does not cover
them. All external links carry rel="nofollow noopener" and open in a new tab. Nothing is loaded
from those sites until you choose to follow a link.
Changes
If any of the above ever stops being true — if, for example, analytics were ever added — this page would be updated before the change went live.