Legal
Security & Trust
Effective 14 August 2026 · Current state — no aspirational claims
This page lists only what is technically implemented today. We do not list aspirational measures or certifications we have not yet completed.
What we do today
AES-256-GCM field encryption at rest
Decision text and AI analysis stored in the database are encrypted at the field level using AES-256-GCM before storage. Encrypted fields are decrypted only at read time within the application.
Passwordless authentication (Google or magic link)
Quorum lets you sign in with Google or with a time-limited magic link sent to your email. No passwords are stored either way. Both are handled via Supabase Auth (OAuth and PKCE flows).
HTTPS / TLS in transit
All data between your browser and Quorum servers is transmitted over HTTPS using TLS. The application is served from Railway with TLS termination enforced.
Row-level security (RLS) on the database
Supabase PostgreSQL row-level security policies are enforced across all user-scoped tables. Authenticated users can only read and write rows associated with their own account.
US-based hosting infrastructure (Free and Elite)
On the Free and Elite plans, the Quorum application runs on Railway (US) and the database is hosted on Supabase (US). Private plan customers deploy on infrastructure of their own choosing (AWS, GCP, or Azure), so this does not apply to Private.
No advertising, no data selling
Quorum does not serve advertising, does not sell user data, and does not share decision content with any third party except the AI providers (OpenAI and Anthropic) used to generate analysis. No China-based provider is used on the Free or Elite plans.
AI processing with no training use
Your decision text is processed by OpenAI and/or Anthropic solely to generate your Council analysis, depending on your plan. Neither provider uses your submissions to train its models. On the Private plan, analysis runs entirely on infrastructure you control instead.
Encryption key rotation tooling
A rotation script (scripts/rotate-encryption-key.ts) re-encrypts all database columns from an old AES-256-GCM key to a new one without downtime. Rotation is performed manually on a deliberate schedule to ensure human oversight of a sensitive cryptographic operation.
Vulnerability disclosure programme
A machine-readable disclosure policy is published at /.well-known/security.txt per RFC 9116. Report issues to security@quorumvault.org. We acknowledge valid reports within 5 business days and target remediation of critical issues within 30 days.
What we do not yet have
We believe transparency about our current limitations is more valuable than unverifiable security claims. The following are not yet in place:
Reporting a security concern
If you discover a potential security issue, please report it to security@quorumvault.org (see our security.txt disclosure policy). We will acknowledge all valid reports within 5 business days and aim to remediate critical issues within 30 days.
Your data rights
You can export or delete your data at any time via the Privacy Center. For full details on how we handle your data, see the Privacy Policy.