SECURITY & DATA

Your research deserves
a clear boundary.

Know who can access your workspace, how records are scoped, and what the current deployment supports.

Workspace permissions
Organization boundaryIdentity + membership + role checks
Owner / AdminManage the workspace
ScientistCreate, analyze, and export
ViewerInspect existing records
Permission model · every protected action is checked on the server.
LABVECTOR / SECURITY

Concrete controls, clearly stated

01

Authenticated access

Accounts use email verification and password sign-in. Server-side sessions identify each researcher, and every protected API operation checks organization membership.

02

Scoped permissions

Organization membership and roles control read, write, administration, and report exports. A researcher must verify the same email address before a pending membership becomes active.

03

Preserved source data

CSV imports are bounded and validated. Original data, hashes, dataset versions, result configuration, author identity, and audit events are stored on the server.

04

Compute and deployment boundary

The live analysis kernel runs in a browser worker; derived results are stored with their execution metadata. The supplied FastAPI/PostgreSQL service needs a separate trusted deployment for centralized compute and server-controlled job execution.

No security certification, regulatory compliance, external audit, enterprise SLA, or immutable legal audit guarantee is claimed. Enterprise controls and wider team access require deployment-specific configuration.

START WITH A QUESTION

Your next experiment.
A better starting point.

Explore the sample study, then bring your own research.