Privacy
What Chorus stores and what it sends.
1. The scenario is in memory
All pharmacokinetic simulation runs inside your browser as compiled WebAssembly (WASM). Demographics, dosing events, drug levels and simulation results are held in memory for as long as the tab is open.
A trained selector is the one thing kept between sessions: it stays on this device, for your account, until you unload it. It holds the model and the ranges it was trained over, not the records it was trained on.
2. What the server receives
Apart from your account itself — your login, and the defaults you have changed for new scenarios, such as target ranges, dosing constraints, assay limits and which models to use — the server receives nothing about your work.
No demographics, drug levels, dosing histories or simulation outputs are ever transmitted, logged or stored server-side, under any configuration.
3. No tracking or analytics
Chorus does not use behavioral analytics, third-party tracking scripts, or advertising networks. Session cookies are used only for authentication and are not used to track activity within the application.
4. Email
Chorus sends only the email needed to operate your account — verification links and password resets.
5. Deleting your account
Deleting your Chorus account removes your login credentials from the server; there is no stored scenario data for it to affect, because none was ever kept.