Privacy policy

Nothing that identifies you. There is no sign-up, no login, no contact form and no mailing list on this site, so there is no personal data for us to store.

Our server keeps standard web server logs, which include the requested address, the time of the request, the browser identification string and a truncated network address. These are used to keep the site running and to see which pages are being read. They are not used to build a profile of a visitor and they are not sold.

The site itself sets no cookies. Google Analytics sets one, and that is the only cookie this site is responsible for. It holds a random identifier, nothing else: no name, no address, no record of what you read.

In the European Economic Area, the United Kingdom and Switzerland that cookie is not set until you accept it. Everywhere else it is set by default, and the banner lets you decline it. Declining is remembered in your browser and takes effect immediately, wherever you are.

Until 16 August 2026 this site ran its analytics without any browser storage at all, and this page said so. That configuration turned out to report nothing whatsoever, so it was replaced by the ordinary one described here. We would rather change the setup and say so than leave a claim standing that no longer matches the site.

This site is funded by advertising. Advertising is served by third-party networks, and those networks may set cookies or use similar technologies in your browser to select and measure the advertisements you see. This happens under the advertising network's own privacy policy, not ours, and we do not receive the data they collect.

Google, if used as an advertising vendor, uses cookies to serve advertisements based on prior visits to this and other websites. Advertising personalisation can be turned off in Google Ads Settings, and third-party vendor cookies can generally be managed in your browser settings.

We use two analytics tools. What we want to know is which pages are read, not who read them.

Cloudflare Web Analytics counts page views. It sets no cookies, does not use a device fingerprint, and does not track visitors between sites. It runs whether or not you accept the analytics cookie, because there is nothing about it to consent to.

Google Analytics 4 is used for the breakdowns Cloudflare does not provide, such as which search or site a visit came from. It sets a cookie holding a random identifier, which is what lets it tell a returning browser from a new one. If you decline, it is not used at all.

We do not use its advertising features. Ad storage, ad personalisation and ad user data stay switched off in every case, including for visitors who accept, because what we asked about was analytics.

What these tools record is the page address, the referring page, and coarse technical details such as approximate location, browser and device type. Google receives that data as a processor under its own terms; we do not send it anything else, we do not use its advertising features, and we do not upload any list of people to it, because we have none.

This is worth stating plainly on a site about medication: we do not ask what you are looking for, we do not ask what you take, and we have no way to associate any page view with a person. Reading a page here creates no health record anywhere in our systems.

The analytics cookie does not change that. It tells us that a browser came back, not who it belongs to, and we never send anything alongside it that could name you. We also keep the advertising features of Google Analytics switched off, so which page about which medication you opened is not used to follow you around afterwards.

Pages here link to DailyMed and to the FDA. Those are US government sites with their own privacy policies. We do not control them and we receive nothing back when you follow a link.

If this policy changes, the date at the bottom of this page changes with it. If a change means we start collecting something we did not collect before, it will be described here in plain terms rather than buried.