Trust Center · English
Security you can verify, limits we state plainly
Fail-closed by principle
If a status cannot be checked, the answer is deny(unavailable) — never a stale allow from cache. The revocation path runs on a separate minimal endpoint and stays up in degraded mode.
Cryptographic discipline
Timing-safe comparison, Ed25519 agent signatures with proof-of-possession freshness (60 s), replay-protected presentations (single-use jti), signed receipts on every decision. Agent private keys are encrypted at rest (AES-256-GCM); customer-managed keys (KMS/BYOK) are prepared, not live.
Evidence integrity in the database
Append-only enforced by triggers: updates and deletes are blocked even for admins; every entry binds the previous hash. Later modification is therefore cryptographically detectable — which is not the same as impossible, and we do not claim otherwise.
Identity & access
Magic link, Google OAuth, SSO via domain routing, TOTP 2FA. API keys per verifier, scoped, with per-key rate limits and instant revocation.
Data residency & GDPR
EU/Swiss hosting, data export (Art. 20), account deletion with anonymization that preserves the legally required evidence chain.
Enforcement: what is real today
The MCP gateway holds the target credential and consumes a one-time, operation-bound capability before it calls the target system — no capability, no call. This protects systems whose credentials live exclusively in the gateway. Where an agent keeps its own access alongside, only traffic through the gateway is covered. We state this boundary rather than implying universal enforcement.
Honest go-live list
Qualified timestamps through an accredited trust service, customer-managed key custody (KMS/BYOK), multi-region redundancy, an external penetration test and EUDI/E-ID wallet connections are architecture-ready but not live. Until the trust service is connected, timestamps come from our own database and are not independently attested to third parties.