Privacy notice · 27 October 2026

What this site
knows about you.

Very little, and we'd rather show our working than write four pages of boilerplate. There are no cookies, no accounts, no forms and no advertising trackers on this site. What follows is the honest remainder, including the third parties your browser does contact.

Cookies None Accounts None Ad trackers None Data sold Never

Who "we" are

Warden is in pre-production in the United Kingdom and is not yet a registered company. The data controller for anything you send us is Joe Chapman, who runs Warden. Contact: joe@wardendfr.com

01 What we collect

If you browse Aggregate counts only

The home page and the disclosure page use cookieless analytics (Vercel Web Analytics): page views and referrers in aggregate. It sets no cookies, builds no profile, and does not follow you across sites.

If you email Your email

Contact is by mailto: — there is no contact form, and messages are not stored in any database. If you write to us we hold your message in an email inbox hosted by Porkbun, use it to reply, and nothing else.

Apart from the standard request logs our host keeps (which include IP addresses), we do not collect names, locations, device fingerprints or behavioural data, and we have no advertising relationships of any kind.

02 Third parties your browser contacts

The part most privacy notices leave out.

FontsGoogle Fonts & FontshareTypefaces load from these content delivery networks (CDNs), which means your IP address and user-agent reach them as a normal consequence of fetching a file. We send them nothing else. Removing this dependency is on our list.

HostingVercelServes the site and processes standard server request logs on our behalf.

DataSupabase — on /verify.html, /live.html and /status.htmlThese pages make read-only requests to Warden's database for public verification data only: the signing-key registry and the anchor log. The live feed on /live.html and /status.html also keeps a connection open (a WebSocket) to receive new key and anchor events. Supabase therefore receives your IP address and user-agent; the pages send nothing else about you and never read incident data. Warden's database is hosted by Supabase in Ireland (eu-west-1), not the UK.

Scriptesm.sh — the live feed on /live.html and /status.htmlThe live feed loads its database client from this CDN, which therefore receives your IP address. The feed opens on live data, so the client is fetched as soon as either page loads; switching to the synthetic demo stream does not undo a fetch already made.

NoneThe console at /dfr.htmlSelf-contained: it makes zero external network requests, so a data-protection officer can watch the network trace and see nothing leave. This is the browser demo; Warden's real console connects to its hosted backend.

03 Demonstration data

Nothing on this site is a real incident.

Every incident, address, record and thermal image in the demo and the documentation is synthetic — invented for illustration. No personal data from any real emergency has ever been processed by this system, because it has never been used at a real incident. Anything you enter into the demo, and the ticks on the data protection impact assessment (DPIA) checklist, stay in your own browser.

04 Retention and your rights

Keeping How long

Correspondence is kept while the conversation is live and for a reasonable period afterwards, then deleted. Aggregate analytics contain no personal data and are not tied to you.

Rights What you can ask for

Access, correction, deletion, restriction, objection and portability under the UK General Data Protection Regulation (UK GDPR). Email us and we will act — in practice this means finding and deleting an email thread.

Our lawful basis for replying to you is legitimate interests (responding to an enquiry you initiated). If you are unhappy with how we've handled your data you can complain to the Information Commissioner's Office at ico.org.uk.

05 Changes

This notice will change if Warden becomes a registered company, and again if a live deployment ever processes real operational data. In that case the fire & rescue service would be the controller, and Warden a processor (or a sub-processor to the service's existing supplier) under a written Article 28 agreement. The date at the top of this page is the last revision.