How Quorum protects your code.
Quorum Terminal is a desktop application. The most important sentence on this page is: your code never leaves your machine. The rest is detail.
Threat model
Quorum's threat model assumes the device itself is trusted. We protect against the following classes of risk:
- Supply-chain tampering — addressed by Apple notarization, signed releases, and pinned dependency hashes.
- Provider credential leakage — addressed by OS-keychain storage and zero proxying.
- Cross-agent contamination — addressed by Git worktree isolation per terminal.
- Unintended data exfiltration — addressed by zero default telemetry and a fully local execution model.
Data flow at a glance
| Data | Where it lives | Sent to Quorum? |
|---|---|---|
| Your source code | Your disk only | Never |
| Terminal output | Your machine + (optional) AI provider | Never |
| Saved prompts | Your machine | Never |
| Provider API keys | macOS Keychain | Never |
| Account email + license | EU region | Yes — for billing |
| Anonymous usage stats | EU region | Only if opted in |
Release integrity
Every signed release ships with a SHA-256 checksum published in the release manifest on our release CDN. You can verify before installing:
$ shasum -a 256 Quorum-Terminal.dmg # compare the output with the sha256 field in the release manifest $ codesign --verify --verbose Quorum\ Terminal.app Quorum Terminal.app: valid on disk Quorum Terminal.app: satisfies its Designated Requirement
Responsible disclosure
Found a vulnerability? Email [email protected] with details. We acknowledge within 24 hours and prioritize fixes by severity.
Sub-processors
Stripe (billing), Cloudflare (CDN, bot protection), MailerLite (newsletter & waitlist emails), Google & Meta (consent-gated analytics/ads measurement). Account infrastructure and transactional email run on EU-hosted providers — final selection is being completed. Full list with DPA details available on request.
Compliance roadmap
- Now — GDPR aligned, EU-region account data, Apple notarization, hardened runtime.
- Next — SOC 2 audit, reproducible builds, and third-party penetration testing are on our roadmap.
Last updated 6 July 2026 · [email protected]