Draft — pending legal review. Describes the architecture as implemented today; not yet reviewed as a formal security statement (CUTOVER-RUNBOOK.md §2.4).

Security

Tenant isolation

Every organization's data is isolated with Postgres row-level security, enforced on every table, not just in application code. org_id is immutable on every row a client can update, closing off cross-tenant data movement even from a compromised admin session in a second organization.

Encryption

All traffic to Fulfilra is served over HTTPS. Data at rest is encrypted by our infrastructure providers (Supabase, Vercel).

Backups

Point-in-time recovery is enabled on the production database, rehearsed against a scratch project before go-live (CUTOVER-RUNBOOK.md §2.2).

Jira integration

The Jira connection is authenticated with signed, expiring tokens verified on every request. We request only the OAuth scopes the integration actually uses.

What's not true yet

No third-party penetration test or SOC 2 report exists yet. Error monitoring (Sentry) is planned but not yet wired into production. This section will be updated as each lands.

Reporting a vulnerability

support@itsm-ltd.com