Cookies

Not necessary ones, not functional ones, not analytics or advertising ones.

There is no session to keep, no account to stay signed in to, no basket, no personalisation and no advertising network. Nothing needs a cookie, so none is set — which is also why there is no consent banner. A banner asking permission for cookies that do not exist would be theatre.

You can verify this rather than take it on trust. Open your browser’s developer tools, look under Application or Storage, and the cookie list for CHAINPRESS will be empty.

No local storage, no session storage, no IndexedDB, no device identifier. The site renders the same for every reader and keeps no preference, so there is nothing for it to remember between visits.

That is stricter than the law requires — storage a reader has actively asked for by operating a control needs no consent prompt — but this site has no such control, so it stores nothing at all.

Cards for aggregated headlines load the publisher’s own share image from their servers. Those servers may attempt to set a cookie on their own domain as part of serving the image. Whether they do is theirs to control, not this site’s — it is the same request your browser would make visiting their page. It is covered in more detail in the privacy notice.

Blocking third-party cookies in your browser stops this, and costs you nothing here beyond the images themselves.

Adding analytics or advertising would mean cookies or equivalent identifiers, and a real consent mechanism before either runs — not a banner added afterwards. This page would be rewritten first.