Trust
Security
What a buyer’s IT team asks us, answered plainly. Everything on this page describes how the service runs today.
Where your data lives
Everything runs in the eastern United States. The Delegus Check service runs on Render in Virginia. Its database is Postgres on Neon, encrypted at rest. Its cache is Redis on Upstash. Both are in us-east-1, and every connection to and from the API uses TLS.
What we keep for each check
For each check we keep the signed receipt, the decision and its reason, the time, and the action that was checked: its type, the resource, and the amount and currency if there is one. We don't keep the request body, and we don't keep the grant or the agent's proof. The receipt carries their hashes instead.
Receipts are stored in an encrypted database that can be restored to any point in the last seven days. Longer backups under a seven-year lock are planned. Receipts are private. Only the service that asked, the company the receipt names, and Delegus staff can retrieve one. Anyone holding a receipt can check its signature offline, without asking us.
The keys, status lists and profiles a receipt depends on sit in write-once storage (Backblaze B2 with Object Lock in compliance mode) under a seven-year lock that no one, including Delegus, can lift. Everything stored before we moved to our current hosting on 4 November 2026 was copied over and checked by hash.
How keys are held
Our signing keys. Receipts are signed with Ed25519 keys held in Google Cloud KMS. The private key never leaves KMS, and only the API service can ask KMS to sign. No person signs receipts. We never remove an old signing key from our published list, so old receipts stay checkable.
Your API keys. We show a key once, when you create it, and store only a SHA-256 hash of it. Nobody at Delegus can read your key. You or we can revoke it.
Keys we hold for your company, if you choose. If your company lets Delegus hold its signing key, that key is an Ed25519 key in Google Cloud KMS, one per company. Delegus signs a grant with it only after one of your people approves those exact bytes with a passkey.
Subprocessors
These services process customer data for us:
- Render, Virginia: runs the Delegus Check API. Its network edge is Cloudflare, so API traffic passes through Cloudflare.
- Neon, us-east-1: the API’s database and the console’s database.
- Upstash, us-east-1: the API’s cache.
- Google Cloud, us-east4: our signing keys, and keys we hold for companies that choose it.
- Backblaze, us-east-005: write-once evidence storage.
- Vercel: hosts the console at app.delegus.ai.
- Resend: sends sign-in links and account email.
- Stripe: billing and payments.
- Anthropic: staff tools only, with credentials and the local part of email addresses masked before anything is sent.
For regions and anything this list doesn’t answer, write to hello@delegus.ai.
Contracts and certifications
A data-processing agreement is part of the Enterprise plan. We don't hold a SOC 2 report today. Getting one is a goal, and we'll say so here when we have it.
Reporting a problem
Write to hello@delegus.ai with the subject "Security", saying what you found and how to reproduce it. We reply as quickly as we can, and we keep you updated until it is fixed. Please test in the free sandbox in your own account, not against anyone else's data. Service status is at delegus.betteruptime.com.
The detail
Engineers and auditors can go deeper in the docs, starting with security controls, infrastructure security, the evidence layout and the threat model mapping.