Privacy & data

What this website collects

Almost nothing, and that is by design.

• No analytics, no cookies, no trackers. There is no Google Analytics, no pixel, no fingerprinting script on this site. View the page source if you like; it is a few pages of plain HTML.
• No forms. The only way to contact me is email. When you email [email protected], I receive what you chose to send, and it is used to reply to you and for nothing else.
• Standard server logs. The site is served by Cloudflare, which processes visitor IP addresses in ordinary server logs as part of delivering any website. I do not analyze or export these.

Principles the product is being designed around

TrialWorkbench is being designed with working patient advocates, and these commitments are load-bearing, not decorative:

• Patient identity stays with the professional. The workbench operates on clinical profiles: diagnosis, stage, biomarkers, prior treatments, a location radius. It is being architected so that names, contact details, and anything that identifies a patient remain in the advocate's own records, not on my servers.
• No selling data. Not aggregated, not "anonymized," not ever. The business model is professionals paying for a tool. That is the whole model.
• No pharma sponsorship during the design phase. While founding members shape the product, its only revenue is founding members. If that ever changes after launch, it will be disclosed on this page in plain language before it happens.
• Registry data is public data. Trial information comes from ClinicalTrials.gov and from verification calls to trial sites. None of that involves patient information.

What this site is not

TrialWorkbench is an informational instrument for healthcare navigation professionals. It is not a medical device, it does not provide medical advice, and it is not a substitute for the judgment of a patient's care team. Treatment decisions belong with patients and their clinicians, always.

Questions

Ask me directly: [email protected]. If a promise on this page seems ambiguous, that is a bug in the page, and I would like to fix it.