Approval workflow
Access is reviewed. Public interest does not automatically unlock internal tools, protected datasets, or diligence materials.
Security
Trust means explaining enough without exposing the estate.
BioAtlas public security is about clear boundaries: what users can read publicly, what requires reviewed access, and what remains protected inside the platform overview.
Request reviewed accessPrivacy boundary
Public pages should explain BioAtlas without exposing private data, internal routes, protected source files, or operational controls.
Internal separation
The public site is intentionally separated from internal app surfaces, admin controls, reviewed systems, and protected intelligence layers.
Public pages are explanatory, not operational.
Public copy should help readers understand BioAtlas while avoiding operational leakage. No public page should need to expose internal tools, protected APIs, admin paths, reviewed routes, or asset locations.
No-AI-ingestion boundaries
Reviewing BioAtlas material does not automatically grant rights to ingest, scrape, embed, vectorise, train on, recreate, or build a competing derivative system from protected assets.
Protected separation keeps the public site clean.
Public routes should funnel serious users into reviewed access, while internal systems remain separated from the public surface.
Request reviewed access