MedScry answers questions about public FDA and NIH records without learning anything about you. There is no account to create and nothing to opt out of, because there is no profile of you to begin with.
Last updated 29 October 2026
There is no sign-up, login or password. MedScry sets no cookies and runs no advertising or analytics trackers. We don't fingerprint your device, and we don't build a profile of you — so there's no consent banner to click through, because there's nothing non-essential to consent to.
A watch is a signed feed link plus a little bookkeeping (a count of what it last saw, and a log of changes) that MedScry saves in this browser's local storage. That data never reaches our servers, isn't synced across your devices, and disappears if you clear your browser data or press Stop on the watch.
A feed link contains only your search terms, the source you chose, and an expiry date, signed so it can't be tampered with. It carries nothing about you. Anyone you give the link to can read that feed, so treat it like a private bookmark.
When you run a search, your query is sent to our server to look it up and the results come back. We don't attach it to an identity — there isn't one — and we don't keep a search history tied to you.
Like any web service, MedScry keeps short-lived operational logs, described under Hosting and logs. They are used only to run and protect the service and never to profile you.
Results are public records published by the FDA and NIH — adverse-event reports, recalls, labels, trials, and chemical and structural references. MedScry aggregates them and links back to the primary source. These reports are unverified signals, not proof that a product caused an event, and nothing here is medical advice.
Every page, script and font is served from medscry.com itself — your browser makes no requests to Google, font services or any other third party while you use the site. We don't embed ads, social buttons, or third-party analytics. If you add a feed link to an outside reader or a Slack or Teams channel, that service — not MedScry — then handles the link under its own policy.
MedScry runs on Cloudflare, which delivers the site and processes each request on our behalf. To do that, Cloudflare necessarily sees your IP address, your browser's user-agent, and the page or search you asked for. Request logs (which can include those details) are kept for at most 7 days and are used only to keep the service running, debug errors and stop abuse. The search index itself runs on our own server in the United States; it receives the search, never your IP address, and logs only timing and status — not what you searched for.
For visitors in the EU, EEA, UK and Switzerland: the legal basis for these logs is our legitimate interest in operating a secure service (GDPR Art. 6(1)(f)). Requests are processed in the United States and on Cloudflare's global network.
Depending on where you live, you have rights over personal data about you — under the GDPR and UK GDPR to access, correct, erase, restrict or object to its processing, and under the CCPA/CPRA and similar US state laws to know, delete and correct it and to opt out of its sale or sharing. Because we have no accounts and keep logs only briefly, we usually hold nothing that can be tied to you; if you think we do, email us and we'll answer within 30 days. EU/EEA and UK visitors can also complain to their data-protection authority.
We do not sell or share personal information, and we don't use it for targeted advertising. There is therefore nothing to opt out of — but MedScry treats a browser's Global Privacy Control signal as an opt-out all the same. MedScry is not directed at children and doesn't knowingly collect data about them.
MedScry (medscry.com) operates this site. The records you search are public data published by the FDA, NIH and the other sources we index; they belong to those agencies and organizations, which remain responsible for their content. For privacy questions or to exercise any of the rights above, write to privacy@medscry.com.
If this ever changes — a new feature that would need to store or send more — we'll update this page and date it above, and we'll keep the default the privacy-preserving one.