Security

Last updated October 20, 2026

If you'd paste a decision into an AI app, you can paste it here. A council is held to the same standard as using the AI companies' own APIs, with your councils locked away from the person who runs it. This page says what we do, what we don't do, and what we can't promise. Questions or a security problem: council@quorum.ceo.

What we don't do

• We don't read your councils. The admin page shows a council's status, seats, model versions and cost, never what's inside, unless you share it.
• We don't sell your data, use it for ads, or use it to train models.
• We don't send your council anywhere except the AI companies seated on it and the services listed below.
• We don't see or store your card. Stripe does.

What we do

• Encrypt your councils where they're stored. The title, brief, every model's answer, the report, images, files and links you attach, and your feedback are encrypted with AES-256-GCM before they're written to the database. The key lives in the app's server settings, apart from the database, so a copy of the database alone can't be read.
• Encrypt everything in transit. Every page and connector call uses HTTPS. The database is also encrypted on disk by Supabase.
• Lock down access. The app reaches the database through its own role, which can only see the council's tables. Justin Wills is the only person with admin access, and admin shows sealed councils as locked.
• Keep sign-in safe. Sign-in codes, links and connector tokens are stored only as one-way hashes. Codes work once, for 20 minutes. Connector access tokens last an hour.
• Keep less. Delete any council in one tap, or have yours delete themselves after 7, 30 or 90 days. The email when a council is done carries only a link.
• Ask the model companies to keep less. Our OpenAI and xAI calls are set not to be stored by them, and the open models run on Fireworks' US servers, which keep nothing by default.

What we can't promise

• The AI models have to read your brief to answer it. While they work on it, each company handles it under its own API terms. The vault covers what we store, not what they receive.
• The service runs the AI calls, so its servers can open your council to do that. The promise is that our admin tools don't, and that nobody but Justin has admin access.
• Quorum is run by one person. We don't have a SOC 2 or ISO 27001 audit yet. If your company needs one, ask us before you send anything sensitive.

Who handles your data

• AI model companies, to answer the council: Anthropic, OpenAI, Google, xAI, Mistral (France), and Fireworks AI (US), which runs the open models from Alibaba (Qwen), DeepSeek and NVIDIA (Nemotron).
• Vercel hosts the site and runs the code. Supabase hosts the database. Stripe handles payments. Resend sends our emails.

If something goes wrong

If we find that someone got at council data, we'll email the people affected as fast as we can, and within 72 hours of confirming it, with what happened and what we're doing about it.

Report a problem

Found a security hole? Email council@quorum.ceo. We'll answer within two business days, and we won't take action against anyone who reports in good faith and doesn't touch other people's data.

More detail: the privacy policy and terms.