security · what the vault enforces
Plain words.No adjectives.
What the vault enforces, where, and how you would know if it did not. We do not claim compliance we have not had audited.
What the vault enforces, where, and how you would know if it did not. We do not claim compliance we have not had audited.
Your own Postgres, row-level secured. Supabase in your region. Every table has row-level security; a user sees only their organisation's rows, and the service role is never used from an AI path.
Invisible to AI, not redacted. A sealed record is absent from every model context. An attempt to read it is written to the trail as denied, with the actor, surface and time.
Pointers, never plaintext. API keys you bring are encrypted at rest with a per-organisation key; tokens we mint are stored as hashes and revealed exactly once.
OAuth 2.1 and proof of possession. MCP clients connect through PKCE or a scoped token. Every tool call is owner-scoped: a token reaches only its owner's rows.
Loopback first, then a tunnel you own. The bridge listens on 127.0.0.1. Through the tunnel it requires an OpVault origin, a paired device token, and rate-limits pairing. Remote IPs are logged.
Append-only, kept forever. Reads, writes, denials, sign-ins and pairings. Exportable anytime. Nothing is ever deleted from it, including by us.
A sealed record returns its title and nothing else, to any AI path, through any integration. The attempt lands on the trail with the actor and the time. Enforced by views in the database, so a lock applied a moment ago is honoured on the next call.
Certifications listed are the providers' own. OpVault itself has not been audited; the status will change here when it has.