Security, stated plainly.

A clear account of the safeguards we build into Labrix, without implying certifications or guarantees we have not published.

Protected accounts and sessions

Passwords are stored as one-way hashes, not readable passwords. Authenticated requests use signed tokens, and login and registration endpoints are rate-limited.

Workspace access checks

Labrix checks access to private papers and team resources. Sharing is deliberate: your work is private unless you invite collaborators or use an integration.

Production safeguards

Production startup validation requires critical secrets and rejects insecure defaults. Payment-webhook verification fails closed when its signing secret is unavailable.

Data controls

You can export your work and request deletion. Read the Privacy Policy for data categories, external processing, retention, and your rights.

Our limits and your role

No online service can promise zero risk. Keep your account credentials private, review collaborator access, and verify research outputs before relying on them. We will update this page as controls and independently validated assurances change.

Report a concern

Send security questions or responsible disclosures to security@labrix.app.