THE WIRE

← Back to the news

Cookies & Storage Policy

Everything The Wire stores on your device, and why there's no banner asking about it.

Version 1.0 · In effect from 28 July 2026 · Read alongside the Privacy Policy

The short version

1. What this covers

UK law — the Privacy and Electronic Communications Regulations 2003 ("PECR"), regulation 6 — governs storing information on, or reading information from, your device. It applies to more than cookies: it covers local storage, service workers and anything similar. So this page lists everything The Wire places on your device, not just the things technically called cookies.

2. Cookies

Both are first-party (set by wire.databased.business, readable by nobody else), HttpOnly (JavaScript cannot read them, which blunts an entire class of attack), Secure (never sent over an unencrypted connection) and cryptographically signed (an altered cookie is rejected, not trusted).

NameWhat it doesLifetimeType
sess Keeps you signed in. Holds nothing but your account identifier — no name, no email address, because we never receive either — signed so it cannot be forged. 90 days, or until you sign out — at which point it stops working on our side too, not just in this browser Strictly necessary
aflow Set for the few seconds you spend on Apple's sign-in screen. Carries a one-time random value that ties Apple's response back to the request you started, which is what stops someone forging a sign-in on your behalf. Deleted the moment you land back on The Wire. 10 minutes, then expires by itself Strictly necessary
Why aflow is marked SameSite=None. Apple returns you to The Wire by sending a form from Apple's servers to ours — a cross-site request. A stricter setting makes the browser withhold the cookie, the security check fails, and sign-in breaks. It is set for ten minutes, contains a random value and nothing about you, and cannot be read by any other site.

3. Other on-device storage

Private reading — three values

You can read The Wire without an account at all. When you do, your preferences have nowhere to live except your own device, so they live here:

KeyWhat it holdsLifetime
wire_local_follows The topics you chose to follow and how strongly, so your edition can be ordered for you. This is what makes anonymous reading personal. Until you clear it
wire_local_read The identifiers of stories you've already opened — at most the last 300, oldest dropped — so the feed stops showing you the same thing twice. Until you clear it
wire_local_hint Whether you've dismissed the "you're reading privately" note, so it isn't shown again. Until you clear it
None of these three is ever sent to us, and there is nothing on our side to send them to. Reading without an account means there is no account, no profile and no identifier anywhere on our servers — so this on-device storage is not a copy of something we hold, it is the only place it exists. (Your IP address still reaches us with every request, as it does with every website — see Privacy Policy §2.) See Privacy Policy §2. ⚙ Topics → Clear all erases every one of them, along with the two values below, in one tap.

The calm check-in — two numbers

Set only after you sign in, and only in connection with an occasional one-tap check-in that asks whether The Wire is leaving you calmer than the news you had before.

KeyWhat it holdsLifetime
wire_survey_at The date you last answered or dismissed the check-in, so you are not asked again for at least a week. Until you clear site data
wire_editions_seen A count of editions you've opened, so a brand-new reader is never interrupted with a question. You are not asked before your third visit. Until you clear site data

Neither value is ever sent to us. They stay on your device and exist solely to make the app ask you less often. If your browser blocks local storage, The Wire simply never asks — nothing else changes.

Notes you've already read — two values

Two short notes explain themselves once and then get out of the way: one on your first edition, saying that the headline, summary and "why it matters" on each news card are written by AI from the outlet's own report — and that weather, flood, energy and planning alerts are not; and one the first time you open Catch-up, explaining that it is an edition that ends. Each has a "Got it" button, and these remember you pressed it.

KeyWhat it holdsLifetime
wire_ai_tip Whether you've dismissed the note about how these stories are written, so it isn't shown again. The same statement stays in the footer of every page, permanently, whether you dismiss this or not. Until you clear it
wire_catchup_tip Whether you've dismissed the note explaining what Catch-up does, so it isn't shown again. It holds nothing about what you read or when you caught up — only that the explanation has been seen. Until you clear it

Neither value is ever sent to us, and both are cleared along with everything else by ⚙ Topics → Clear all.

Service worker

If — and only if — you turn on notifications, a small background script is installed so alerts have somewhere to arrive. It is deliberately minimal: it caches nothing and intercepts no network requests. It cannot serve you a stale edition and it cannot see your browsing. Turn notifications off, or uninstall the app from your home screen, and it goes.

Push subscription

Turning on notifications also creates a subscription with your browser's push service (Apple, Google or Mozilla, depending on your device) and sends us its address and encryption keys. This is how web notifications work everywhere; it is covered in the Privacy Policy. Consent is the permission prompt your browser shows, and it is withdrawn by turning alerts off.

The iOS app

The iOS app is a thin shell around the same website, so it uses the same two cookies and the same two stored numbers, held in the app's own container. Deleting the app deletes all of it. The app contains no advertising identifier, requests no tracking permission, and uses no third-party SDKs.

4. What is not here

Under PECR regulation 6(4), consent is not required for storage that is strictly necessary to provide a service the user has explicitly requested. Everything above falls inside that exemption, and here is the reasoning for each, so you can judge it rather than take our word:

A banner is a request for permission. Requesting permission for storage that requires none — and that we would still need in order to run the Service — would be theatre, and irritating theatre at that. If we ever introduce storage that does require consent, you will get a real choice, with a genuine "reject" that is exactly as easy to click as "accept", before anything is stored.

If you disagree with our reading on the two local-storage values, you can clear them at any time — see below. The Wire behaves identically without them, save that it may ask you the check-in question again.

6. Controlling all of this

Do Not Track and Global Privacy Control. We do not need to honour these signals, because we do not do the thing they ask us to stop: there is no tracking to opt out of, for anyone, whether or not they send a signal.

7. Changes

If we add or change any storage, this page is updated and the version raised before the change ships. Adding anything that needs consent means adding a consent mechanism, not quietly extending this list.

VersionDateWhat changed
1.028 July 2026First published.

8. Questions

privacy@databased.business. If you think something is stored on your device that isn't listed here, please tell us — that would be a bug in this page, and we'd want to fix it.