Security

How access is controlled

Sign-in is email and password with email verification, Google OAuth, enterprise SSO (SAML/OIDC) for workspaces that configure it, and optional TOTP two-factor authentication in Settings. Every database table enforces owner-scoped row-level security, so application bugs cannot leak one customer's deals to another.

How data is protected

Databases are EU-hosted with AES-256 encryption at rest and TLS in transit. Secrets live in environment configuration, never in code. AI provider calls run server-side; browsers never hold provider keys. You can mask names, amounts, and counterparties in your browser before anything is sent.

How actions stay auditable

Signature ceremonies, version locks, redrafts, credit movements, and monitoring alerts are written to append-only records with content hashes. Invitation links are single-purpose tokens; signing binds the exact document version, and fully signed documents lock against edits.

Certifications and review

An independent SOC 2 Type II audit of our controls is in progress; this page will link the report when it lands. Enterprise customers receive a signed data processing agreement (see our DPA) and a live platform status at /status. Security questions: contact us through the help center and we respond within two business days.