Privacy

daily.audio is a reading wall for audiophile publications. It has no accounts, no advertising, and no interest in who you are. This page says exactly what it does collect and how to stop it.

What is stored in your browser

Your own settings.The publications you follow and the card order you picked are kept in your browser's local storage, and that is the only copy. Which publications you follow never leaves your device. The card order is the one exception: which of the four modes is in use is counted along with the page views described below, so we know which modes earn their place. Like those counts it is anonymous, and it is subject to the same consent rules below - where analytics does not run, this is not counted either. It is the setting alone, never the reading it produces. Clearing your browser data removes both.

Buy links carry a tag, not your identity.Retail links on brand pages include this site’s Amazon affiliate tag. The tag tells Amazon which sitesent the click - it says nothing about who you are, and this site stores nothing for it. What happens next happens on amazon.com under Amazon’s own policy and consent controls: Amazon knows the visit was referred from here, and if you buy something it may credit this site - that is the whole mechanism - but who you are stays between you and Amazon. This site never learns who clicked, let alone who bought.

Analytics, only if you allow it.We use Google Analytics to count page views, see which pages get read, count which of the wall's display modes readers use, and count clicks that leave the site — the destination's domain and which page it was clicked from, since links out are the whole product. All of it is how the site is used, never who you are. It sets two cookies (_ga and _ga_<id>) holding a random identifier, kept for up to two years.

In the UK, the EEA, Switzerland and California, Google Analytics is not even loaded until you accept: decline, or simply ignore the banner, and your browser sends Google nothing at all. Elsewhere it runs by default and you can turn it off at any time below — the cookies stop, and at most an anonymous, cookieless count remains that cannot be tied to you or to a return visit.

A plain count that runs without asking. Because most readers never answer a consent banner, the numbers above are not a headcount. So the site also counts page views with Umami, which runs on this site's own server: the page views are stored here and nowhere else, and there is no analytics account at another company holding them. They do pass through Cloudflare on the way in, the same as every other request to this site — see below — but they stop here. It writes nothing to your device — no cookie, no stored identifier of any kind. That is not by itself why it runs without asking, and it would be glib to say it were: the rules cover reading information from your device as well as writing to it. It runs without asking because it is kept inside the narrow shape regulators set out for plain audience measurement — it belongs to this site alone, it is never combined with anything else, it cannot recognise you tomorrow let alone on another website, it keeps only a coarse location, and the records are deleted after 25 months. If any of that stopped being true, this would need your consent, and we would ask for it. You can switch it off regardless, at the bottom of this page. The consent rules that govern Google Analytics here are about what gets put on your machine, and this puts nothing there. The only thing it reads from your browser's storage is a switch you can set yourself to turn it off, and it reads that only in order to obey it — the switch is at the bottom of this page, and it works.

With each page view it records the page's address and title, the page you arrived from, your browser, operating system and device type, your screen size and your language, and the country and region the visit came from. That is the ordinary shape of a page-view count, and none of it names you. Two things are deliberately left out: the city, which is discarded before the analytics ever receives it rather than merely left unused, and anything you type into the search box — the query is stripped from the address before it is sent, so which pages get read is recorded and what you searched for is not.

To tell one reader's visit from another's without an identifier, it converts your IP address and browser version into a one-way hash, mixed with the current date and with a secret key of ours that is never shared with anyone else. Your IP address itself is not stored. The date part changes at midnight UTC, so yesterday's hashes cannot be matched against today's — the count genuinely cannot follow you from one day to the next. We would rather say that plainly than quote a “unique visitors” figure that quietly implies otherwise. These records are deleted after 25 months, automatically.

What we deliberately do not do

• No advertising features.Google Signals, ad personalisation and ad storage are switched off in the site's own code, not merely in a dashboard setting. Your browsing here does not feed ad profiles.
• No selling or sharing. We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are used in California law. There is nothing to opt out of because we do not do it.
• No tracking pixels in email, and no third-party pixels on the site.
• No cross-site anything. None of the three things that count visits here can recognise you on another website, and nothing is combined with data from anywhere else.
• No profiles, no accounts, no fingerprinting.

Email, if you subscribe

The digest is a confirmed opt-in: we store your address and the times you asked, confirmed and unsubscribed, so we can prove the subscription was yours. If you subscribed on the previous daily.audio site, your confirmed signup carried over when the newsletter relaunched: we keep your original signup date, and the confirmation time records when your subscription moved to this system. Mail is delivered by Resend, who process it on our behalf. Every issue carries a one-click unsubscribe link, and unsubscribing is immediate and permanent unless you sign up again.

Who else sees a request

Cloudflare Web Analytics. The site also counts visits and page views through Cloudflare, at their network rather than in your browser. It sets no cookies, stores nothing on your device and does not fingerprint you, so it cannot follow you between sites or recognise you on a later visit — which is why it is not something you are asked to consent to. It tells us which pages are read and how fast they loaded, and nothing about who read them.

The site is served through Cloudflare, which sees the IP address of every request in order to route it and block attacks, and which tells us only where a visit came from: the country and, inside the United States, the state. That is used for two things and no others — deciding which consent rules apply to you, which is not stored, and the country and region recorded with a page view as described above. The city is stripped before it reaches either. The server keeps short-lived access logs of the page requested, the response and how long it took. Those logs deliberately exclude request headers and strip subscription tokens from URLs.

Your rights

In the UK and EEA you can ask for a copy of anything we hold, ask us to correct or delete it, or object to it being processed. In California you can ask what has been collected, ask for it to be deleted, and correct it — and we will not treat you differently for asking. In practice the only thing we hold that identifies anyone is a subscriber's email address and its consent history.

Write to [email protected] and we will answer within 30 days.

Your choices

Questions about any of this go to the contact page. This page changes when the site does; there is no version history worth keeping because the answer has always been the same one.