This page and its static resources loaded successfully.
Current state, controls, and known limits.
One place for service reachability, model identity, data handling, security practices, scientific limitations, and incident reporting.
System reachability
These checks confirm that the public gateway responds. They are not a synthetic model prediction or a performance guarantee.
Testing the same-origin account route without changing account state.
Reading the public version and configuration route; no profile is submitted.
What is being served
- Display model
- Provenance-2
- Scope
- RNA-seq site-of-origin research across 25 anatomical sites
- Coverage
- In-distribution calibration and conformal guarantees only
- Gateway version
- Checking live route…
- Agreement
- Checking live route…
What leaves your browser
- Readiness checker: nothing. Analysis is browser-local and the input is not retained.
- Model runner: the parsed gene-expression profile is submitted only when an entitled user chooses Run analysis.
- Project history: report outputs and an input fingerprint for matching runs are stored on the current device; raw profiles are not saved to history.
- Identifiable data: do not submit names, medical record numbers, dates of birth, or other direct patient identifiers.
Limits are part of the product.
These are not footnotes to be discovered after a result.
Mesothelioma is out of validated scope
Real mesothelioma is not reliably recognized. Pleura and Mediastinum outputs must not be relied upon.
Platform shift changes performance
Calibration and 90% conformal coverage do not transfer to arbitrary assays or processing pipelines.
Rare sites remain data-limited
Some rare classes are underpowered and can be overconfident despite calibration of the overall model.
Retrospective research only
No prospective clinical validation, independent clinical-site study, or completed demographic subgroup-equity audit.
Layered access
- Signed research agreement before model access.
- Account, organization, IP, daily, and weekly usage controls.
- Revocable API keys and account-bound output watermarking.
- Bounded requests, origin isolation, and model gateway resilience controls.
- Security headers and a public vulnerability-disclosure contact.
Security or service incident
If you find a vulnerability, a service interruption, or a result that appears scientifically unsafe, send the relevant time, page, and non-sensitive reproduction details. Do not email patient data.
Email the trust contactFor ordinary account or billing help, use the support center.