DoseTrace

The exemption ends November 27, 2027, in 437 days.

Security

What DoseTrace stores, who else processes it, and how to report a vulnerability.

Reporting a vulnerability

Email hello@thecompound.tech. Include the URL, what you did, and what you saw. There is no bounty and no NDA to sign. We will confirm receipt, and we will tell you what we changed.

The same address, with a machine-readable expiry, is published at /.well-known/security.txt under RFC 9116.

Accounts

DoseTrace has no user accounts. There is nothing to sign in to, no password to reset and no session to steal, and a build gate fails the deploy if an authentication route ever appears in this repository while this page still says otherwise.

What is stored

  • The answers you give the exemption checker are used to answer it and are not written down unless you explicitly ask for the result by email
  • If you do ask for it, your email address and that result are stored on one row
  • If you buy, Stripe collects your billing address and your card
  • Anonymous usage analytics, page views and clicks. Form inputs are masked in session recordings and no profile is created for a visitor who never identifies themselves

Who else processes data

  • Stripe, takes the payment and holds the card details, we never see a card number
  • Supabase, the database that one opt-in row is written to
  • PostHog, anonymous product analytics, proxied through this domain
  • Vercel, serves this site and holds its access logs

Also true

  • The exemption checker stores nothing on its own. The email row exists only because you asked for the result to be sent, which is an explicit opt-in rather than a side effect of using the tool.
  • No patient data, prescription data or transaction data is ever sent to this site. The binder is assembled from what your pharmacy tells us directly.
  • Payment pages are Stripe's own hosted checkout on a Stripe domain, so a card number is never typed on this site.

DoseTrace is built and run by Compound Labs. The declarations on this page are part of this product's own configuration and are re-checked at every deploy against the repository they describe: a product that claims to have no accounts and ships an authentication route fails the build, and so does one that takes payment without naming its payment processor here.