Privacy
This collection records nothing about the people who read it. No accounts, no cookies, no analytics, no third-party requests. The rest of this page explains what "nothing" covers, names the one company that necessarily sees your request because it serves the page, is honest about the one place your own words enter a web address, and shows you how to check the whole claim yourself.
Someone reading a page about whether a drug does what its makers say is often deciding something about their own body, or someone else's. That is a bad moment to wonder who is watching. So the answer is built into the site rather than promised on a page: there is nothing here that could collect anything.
Nothing, and the specifics of nothing
There are no accounts and no way to make one. There is no newsletter, no comment form, no upload, and no way to submit anything to this site. Nothing here is behind a payment, because there is nothing to buy.
The site sets no cookies. It writes nothing to your browser's storage. It runs no analytics of any kind, first-party or third-party, and carries no advertising and no tracking pixel. It loads nothing at all from another company: no fonts, no scripts, no embeds, no tag manager, no content delivery network beyond the one serving the page itself. A page asks for its own text, its own stylesheet and its own logo, and nothing else. That is why these pages use the typefaces already on your computer rather than prettier ones from a font service — a request to a font service would tell that company you were here, so the site does not make one.
This is enforced rather than intended. A deployment check runs before every release and fails the release if any page references a resource outside this domain. The rule is not a promise someone remembers to keep; it is a gate the site has to pass.
Every study page links out to its original source, and the footer links to Field Assembly. Following a link takes you to someone else's site — a journal, PubMed, ClinicalTrials.gov, a regulator — where their rules apply and not ours. Several of them do track their readers. We have no control over that, and we would encourage the same skepticism there that we are inviting here.
The study filter puts your words in a web address
The studies page has a filter with a text box. It is worth being precise about this, because it is the only part of the site where something you typed leaves your computer.
The filter is an ordinary web form that works by putting your terms into the address bar, so a search for a drug name produces a URL containing that drug name. That address is part of the request, which means it reaches the company serving the page, described in the next section, and it is stored in your own browser history. It is not sent to a search company, not sent to us in any form we can read back, and not recorded anywhere on our side. The filter runs against the studies in this collection and nowhere else.
If that matters to you, the filter is optional: every page is reachable by ordinary links, and a private browsing window keeps the address out of your history.
There is one other address worth naming. /evidence.json publishes the study records as data, so anyone can take the collection and check it. It contains studies, not readers. Nothing about you is in it.
What Cloudflare necessarily sees
The pages are served by Cloudflare. Delivering a web page requires a server to receive the request, so Cloudflare's network sees the address you asked for, your IP address, and your browser's user agent, in the same way the postal service sees an envelope it carries. This is not a choice the site makes; it is what serving a page is. Cloudflare's handling of that traffic is governed by their privacy policy, not ours.
What we control is what we ask Cloudflare to keep and what we look at. Their Web Analytics product is switched off for this site, and we have set up no export and no live stream of request logs, so no record of an individual request reaches us or leaves Cloudflare. We hold no per-visitor log and have no means of consulting one.
Cloudflare does keep request data of its own, and that is what produces the single figure we can see: a count of how many requests the site served. It names nobody, we do not break it down further, and we could not identify a reader from it if we tried. How long Cloudflare keeps that underlying data, and what they do with it, is governed by their policy rather than ours, which is the honest limit of what this page can promise you.
If you write to us
The one way this site can learn anything about you is if you choose to tell us, by writing to hello@fieldassembly.net. That is ordinary email: it arrives in a mailbox, it sits there, and it is read by a person.
Please do not send us your medical history, your diagnosis, your test results, or your prescriptions. We do not need any of it, and we cannot advise you on it. A correction can be made from the sentence you are correcting and the paper that contradicts it, and a page can be fixed without knowing anything about the person who found the error. If you send those details anyway we will not repeat them, publish them, or record them in the change log, which names what was corrected and never who reported it.
Correspondence is used to answer you and to fix the page, and for nothing else. It is not added to a mailing list, because there is no mailing list. It is never shared with a drug manufacturer, journal, researcher, regulator or health-care provider. Correction threads are deleted within twelve months of the correction being made; the correction itself stays on the record permanently.
How to check this yourself
Every page in this collection is built on the principle that a reader can consult the source rather than trust the summary, and this page holds to the same standard. The claim above can be audited in about thirty seconds, on this page or any other.
In Chrome, Edge, or Firefox, press F12 and choose the Network tab, then reload the page. In Safari, enable the Develop menu in Settings, then Develop › Show Web Inspector and choose Network. You will see every request the page makes. All of them should point at this site and nowhere else. Check the Application tab (Storage in Firefox and Safari) for cookies and local storage; both should be empty.
If you ever find a request going somewhere we have not named on this page, that is a defect and we want to hear about it. It will be fixed and recorded like any other correction.
If this changes
A privacy policy that gains a tracking section without saying so is worse than no policy at all, so the commitment here is about sequence: this page changes before the site does. If anything on it stops being true, the page will say what changed and on what date, and the old wording stays legible in the record instead of disappearing.
Questions or corrections: hello@fieldassembly.net.
Last updated September 14, 2026. Verified against the live site on the same date.