Security

Written by the Pressroom team from the code as it stands; no outside party has audited it yet.

Keeping offices apart

Every office is a separate workspace; every record carries the office’s identifier and every query is scoped to it, checked by automated lint in our build. One person with roles in two offices has two separate accounts.

Signing in

Password sign-in with two-step verification (authenticator app and backup codes) and passkeys; single sign-on through an identity provider; invitation-only accounts, no public sign-up.

What we keep safe and how

Integration credentials encrypted at rest (AES-256-GCM); per-request security headers and a content-security policy; an append-only audit log with a daily hash chain; daily backups; dependency, secret and container scanning on every change.

What we do not have yet

No SOC 2, no GovRAMP; no external penetration test (scoped, not yet booked); one operator, with a named backup operator in preparation. We say this plainly because an office should know it before it buys.

Ask for more

The full security overview, our answered short questionnaire (CAIQ-style), the threat model and the data processing agreement template are available on request. Contact us to ask for them.