Authenticated ownership
Scientific project records are associated with the authenticated user instead of being exposed as shared public state.
Security & cloud
Clear boundaries from sign-in to compute artifacts.
The public security page describes how user access, project data, validated requests, compute and resulting files are separated across the product flow.
Architecture controls
Security statements grounded in the platform design.
The page intentionally avoids unsupported certification claims and focuses on boundaries that are meaningful to users of the modelling workspace.
Project data boundaries
User-owned modelling data is kept within project ownership rules across the workspace.
Validated submissions
Compute requests pass through controlled application paths rather than trusting browser state alone.
Separated compute
The browser manages the workspace while supported modelling jobs execute independently and return state and artifacts.
Traceable artifacts
Processor versions, run state, storage references and generated outputs remain associated with the project workflow.
Operational release gates
Validation workflows are used to protect beta and production operations instead of presenting unverified compliance claims.