Labs do not adopt tools that put a grant at risk. Proprietary protocols and bench observations are not used to train foundation models under our paid AI configuration; see /ai. We make no regulated-system validation claims.
When AI features are on, prompts go to Anthropic Claude by default, with Google Gemini as fallback and for audio and image reading. Both process requests under commercial API terms (see /ai). When AI is off, nothing is sent to either provider. Inference is ephemeral; providers may retain encrypted abuse metadata briefly — not a Zero Data Retention claim.
Encrypted in transit and at rest by our hosting providers. Lab-scoped tables use Row-Level Security and RBAC. The shared reagent catalog holds vendor catalog metadata (for example NEB, Thermo Fisher, ATCC), not lab data; signed-in users can read it but not write to it. It is shared by design, so we do not claim the catalog is tenant-isolated.
runline critiques and verifies methodology — it does not ghostwrite aims or invent experimental results. Diagnostics never labels a person with integrity accusations; those checks live only under /review.
Justin and generative surfaces are assistive aids. The executing scientist verifies volumes, containment, and chemical safety before pipetting.
Coming SoonSOC 2 Type II — coming soon. University SAML SSO is not shipped. DURC / dual-use screening is not productized. Draft DPA and security one-pager: download /dpa. Readiness stub: /soc2.
Privacy inquiries: support@runline.space
Counsel review — not legal sign-off. The controls below describe engineering facts as of 2026-10-17. They are not attorney-approved, not a signed DPA, and not a SOC 2 letter. Claim IDs map to the register in docs/legal/comparison-marketing-policy.md.
Lab audit events append through a hash-chained trail. Review can show chain verification and export CSV with chain status. Daily chain anchors and optional RFC 3161 timestamping depend on ops configuration — not a regulated Part 11 attestation.
Operator Sign & Lock binds a re-authenticated meaning and content hash on a run; edits after signing are detectable. Optional witness attestation is available. This is not a Part 11 / QES / ALCOA+ certification.
Self-serve Settings export: JSON and Markdown records plus byte-exact Storage files in a BagIt ZIP (SHA-256 manifest). Rate-limited; large exports use a short-lived signed download URL.
Account deletion is available in Settings / Privacy. Personal data is purged on the published retention schedule (verified deletion aim ≤ 30 days unless legal hold). Lab-owned content stays with the lab where the schedule says so.
TLS in transit and AES-256 at rest on the hosted store. Lab-scoped tables use Row-Level Security. Lab files on Supabase Storage support upload, download, and preview. The shared reagent catalog is not tenant-isolated.
Campus SSO is available on request per institution. No production identity provider is registered yet — sign-in today is Google or GitHub OAuth, or email.
SOC 2 Type II is coming soon. An observation period has not started and we do not have an auditor letter. Do not treat /security, /dpa, or /soc2 as an audit report.
You keep ownership of User Content you put in runline. Export and deletion paths are self-serve. We do not use User Content to train foundation models under the paid AI configuration (see /ai).
Lab files live on Supabase Storage: upload, download, and preview only. There is no in-browser Office editing.
Campus SSO is available on request per institution. No identity provider is registered yet — sign-in is Google or GitHub OAuth, or email.
SOC 2 Type II is coming soon. An observation period has not started and we do not have an auditor letter.
Draft DPA and security one-pager (print to PDF): /dpa. SOC 2 readiness stub: /soc2. Campus: /campus.
Questions: support@runline.space