Trust center
Security at Brief
Brief is designed to give coding agents useful context without turning source code or connector credentials into casual cloud data. This page names the controls that exist today and the assurance claims we do not make.
Last updated July 19, 2026Local-first architecture
Repo scanning, maps, context selection, and diff review run in the customer's local connector. An account is not required for local use. The default hosted mode syncs derived records such as repo identity, paths, hashes, map summaries, receipts, and approved team guidance. It does not sync raw source text by default.
Richer team-cloud source sync is an explicit privacy-mode choice, not a hidden upgrade from derived sync.
Authentication and access
- Supabase Auth manages user sessions and magic-link sign-in.
- Workspace membership is role-based. Owner and admin actions are enforced again on the server.
- Public database tables use row-level security; privileged service credentials stay server-side.
- MCP connector secrets are shown once, stored as hashes, and can be revoked from workspace settings.
Software supply chain
The customer connector is distributed as a version-pinned npm package. Release checks install the packed artifact in a clean project, reject private workspace dependencies and machine-local paths, pin GitHub Actions by commit, and support npm provenance. Production readiness also checks that the exact package version is publicly readable before a workspace issues a connector credential.
Report a vulnerability
Send a private report to security@runbrief.ai. Include the affected surface, reproduction steps, impact, and whether active exploitation is suspected. Do not include live customer credentials or source code unless we request a secure transfer.
Brief does not currently claim SOC 2, ISO 27001, an external penetration test, or a formal bug bounty. Those claims will not appear here until independently supported.