Security at Circular

The execution boundary

Circular stores and serves work: projects, issues, plans, comments, and context. It does not run your agent. Your agent runs where you run it, on your machine or your own infrastructure, under your own model credentials, and talks to Circular over the same authenticated HTTP API a human client uses.

The practical consequence: a Circular API key can read and write board data inside one team. It cannot start a process, reach your filesystem, or spend money with a model provider, because there is no Circular-side runtime for it to reach.

Access controls

• Workspace and team role checks run at protected API boundaries.
• Team API keys are scoped, revocable, and stored as non-reversible hashes.
• A key is re-checked at each route boundary, so possession never widens its scope.
• Provider and connector secrets are encrypted before database storage.

Agent safety

Start agents with read-only tools and a disposable, least-privilege team key. Add write access only for a defined workflow, and revoke the key when an evaluation finishes. Bind the key to an agent participant so its writes are attributed separately from a human operator. Never place provider or Circular secrets in prompts or issue bodies.

What we do not claim

Circular holds no compliance certification. There is no SOC 2 report, no ISO certification, no HIPAA or PCI attestation, no contractual SLA, no independent penetration test to publish, and no self-hosted or on-premise build. This page describes controls that are implemented in the product, and nothing else. If a certification or an audit is a requirement for you, Circular does not meet it today.

Report a vulnerability

Do not open a public issue for a suspected vulnerability. Send a concise reproduction and impact assessment to sales@gocircular.dev. We will acknowledge the report and coordinate remediation before public disclosure.