Privacy Policy
This policy describes how Biosphere handles account data, uploaded scientific files, workflow outputs, and operational logs.
1. What we collect
Biosphere stores account information such as name, email address, role, and billing-related records. It also stores workflow inputs, uploaded files, generated artifacts, and execution metadata required to run and audit scientific jobs.
2. Why we collect it
We use this data to authenticate users, run workflows, reserve and charge credits, maintain audit trails, recover failed jobs, and expose results back to the workspace.
3. Scientific files and results
Uploaded scientific files and generated outputs may be stored in runtime storage, database-linked metadata, or external object storage depending on deployment configuration. Administrators are responsible for configuring durable storage and access controls for production deployments.
4. Security and access
Biosphere uses authenticated sessions, role checks, audit logs, and workflow authorization boundaries to restrict access. Local worker pairing, billing endpoints, and admin tooling should only be used by trusted operators under properly configured secrets.
5. Verification and account activation
Account activation may require a one-time verification code delivered to the user's email address. Deployment owners are responsible for configuring outbound mail delivery correctly so users can complete account activation and recovery flows safely.
6. Retention
Data retention depends on your deployment and storage policy. Workflow logs, audit events, and generated artifacts may remain available until deleted by administrators or removed by retention rules.
7. Contact
If you operate this deployment for a lab, company, or internal team, the deployment owner is responsible for publishing the correct contact and compliance details here.