TRUST
Security
This is what we do today. We hold no SOC 2 or ISO certification and do not claim one.
What the proxy stores
- The local proxy forwards your provider API key upstream but never writes it to a receipt or a log.
- Receipts hold usage and cost metadata only: no prompts, no completions, no request bodies, no authorization headers.
- The proxy binds to 127.0.0.1. It is not an authentication boundary against other processes on the same machine.
Hosted workspace
- Sign-in uses a one-time email code behind a bot check. Codes, sessions, enrollment tokens, and agent credentials are stored only as SHA-256 hashes.
- Every query is scoped to your organization. A shared company email domain never grants access to another workspace.
- Browser mutations require a same-origin request. Session cookies are HttpOnly and SameSite=Strict.
- Pages use a strict Content-Security-Policy with no inline scripts.
- The Postgres backend, when the owner turns it on, uses separate migration and application roles and row-level security per organization.
Engineering
- Every change runs tests, a dependency audit, and a secret scan in CI before merge.
- Secrets live in deployment secrets, never in the repository.
Report a vulnerability
- Report privately through GitHub security advisories: https://github.com/persooninc/costcap/security/advisories/new. Please do not open a public issue for a vulnerability.
- We aim to acknowledge a report within three business days.
Last updated 2026-11-13.