Cookies

Nothing is stored on your device to tell you apart: no cookie, nothing in your browser's own storage, no fingerprint, no identifier another site could recognise. One cookie exists here, and it is not for counting.

The one cookie

It is called PHPSESSID and it arrives only when you are about to send us something — a demo, a message, a request to be told when a record comes out. The page asks our server for a security token first, and the cookie comes back with it. It holds that one visit together, so the form you started is the form you finish, and so the token that proves a submission came from this site rather than from another site borrowing your browser has somewhere to belong. The token itself is not a cookie: it stays on our side, inside the visit this one points at.

It carries a random reference and nothing else — no name, no email address, no page you have read — and it is gone when you close your browser. It needs no consent, and that is not our ruling to make: a cookie that does only the thing you have just asked for is the one kind the law has always exempted from asking.

Reading a page never sets it. You can go through the whole site — the catalogue, a record, an artist, the mixes, this page — and be given nothing at all.

Counting visits

We count which pages are read. Nothing about that count is put on your device: no cookie, no entry in your browser's own storage, no fingerprint taken so that we recognise you next time. There is nothing here for you to clear, and nothing to carry with you to anybody else's site. What the count is actually made of, how long any part of it is kept, and what our server writes down in its own logs simply to serve a page belong to the privacy notice rather than to this page, and that is where they are written: counting visits, and what the server writes down to run the site. This page will not summarise either of them, because a summary and a document disagree the first time one of them is edited and the summary is the version everybody reads. This page is about your device, and on your device there is nothing.

Why there is no banner

The cookie law is a law about your device. It governs putting information on it and taking information back off it, and consent — with every exemption from consent — hangs off that one act. We do it once, for the cookie above, in the case the law exempts. We do not do it to count you. There is nothing here to agree to, so there is nothing to put a banner in front of you about.

And why there is no switch

This half is harder, and it is worth saying plainly rather than leaving you to notice. An opt-out has to be remembered. A site can remember something about you in one of two places: on your own device, or against something that identifies you on ours. There is nothing here to sign in to, so the second does not exist — which leaves a cookie. A marker, set on your device, kept for a year, whose only purpose is to record that you asked not to be counted. That is more about you, kept far longer, than the counting it would switch off. A working switch on this page would have to break the first sentence of it in order to honour it.

So what you can do instead is this. If you would rather we did not count your visits, tell us and we will answer — an objection is a right you have, and it is ours to act on rather than yours to operate. Two things are worth knowing before you use it. We cannot pick you out when you come back, so we cannot take you out of the counting in advance without beginning to hold something that would recognise you, which is more than the counting holds now. And if your browser sends a Global Privacy Control signal, nothing on this site reads it, measured on 16 September 2026. The privacy notice says what the counting holds and how to ask about it; the contact form is the route either way.

Nobody else

No other company sets anything on this site and none is asked to: no advertising network, no analytics company, no consent vendor, no CAPTCHA, no embedded player. The player is the one that costs us something. A play button from a streaming service brings that service's cookies onto our page, so we do not embed one — every 'Listen on' link takes you to the service instead, where their rules are theirs and you can see that you have gone.

Your browser does fetch things from another address while you read this site: the sleeves and the audio come from content.jwhive.com and stream.jwhive.com. Those are ours. A different address is not a different party.

One company is genuinely in the middle, and it is ours to explain rather than yours to discover. The site is delivered through Cloudflare, which sits in front of our server. Two things follow. Cloudflare can set a cookie of its own to tell a browser from a robot: on 16 September 2026 it sets none here, and that is a setting rather than a rebuild, so read the date as part of the sentence. And it asks your browser to tell it when a request to this site fails — a header rather than a cookie, saying which address did not arrive and why, not what you read.