Security answers for your vendor review
The questions a security team asks before approving Odile Gate, answered from the code that runs today. What Gate does not do yet is listed as plainly as what it does.
Implementation details were checked on 19 November 2026 against release 4ac89f2. For anything this page does not answer, a completed questionnaire (CAIQ, SIG Lite or your own) or a data processing agreement, write to hello@odilelabs.com.
Company and contact
- Vendor: OdileUSA L.L.C., a Wyoming limited liability company doing business as Odile Labs (terms).
- Security contact: hello@odilelabs.com with "Security" in the subject. The same contact is in /.well-known/security.txt.
- Company-wide security page: odilelabs.com/security covers every Odile product and how to report a vulnerability.
Where Gate runs and where data lives
- Gate runs on Cloudflare Workers. Each project's records are stored in its own Cloudflare Durable Object with SQLite storage, so one project's records are never in another project's store.
- Cloudflare chooses where each project's storage lives. Gate does not pin a region or jurisdiction today.
- Cloudflare Analytics Engine separately receives event names, the project id, the plan and counts.
What Gate keeps about your calls
- Bodies: request and response bodies of ordinary calls are never stored. Gate keeps the request's size and a SHA-256 of its body.
- Audit rows can include: time, app, method, the rule that matched, status, duration, request size, a reason code when a call is refused, country code, run and approval ids, a SHA-256 of the path and, where they apply, the acting member's id and name, the approver's name and the signing key id. When no rule matched, the first path segment is kept in clear. Query strings, headers and IP addresses are not in audit rows.
- A SHA-256 of a predictable path can be matched by guessing: treat it as a fingerprint, not as anonymization.
- Calls held for approval: path, query and body are sealed with AES-256-GCM (up to 1 MB) until someone decides or the hold expires, then cleared.
- Response filtering (optional): an allow-list of JSON fields per app, applied in memory; nothing is stored.
Keys, secrets and the change log
- Keys Gate issues (admin, app, member, approver, session and run keys) are stored as SHA-256 hashes and shown once.
- Your upstream API credential, the company sign-in client secret, the webhook signing secret, the SIEM header and approver phone numbers are sealed with AES-256-GCM under a Gate key, bound to the project id. Gate never shows them back.
- Alert webhook and SIEM addresses are kept as given so Gate can deliver to them; the dashboard, the API and the change log show only their origin.
- Gate attempts a change-log row for every admin or approver request that changes something: who, what, before and after (secrets appear as "saved"), the IP address and the browser user agent. The change log is kept 365 days on every plan.
- Projects bought through DigitalOcean also keep the owner key sealed, so DigitalOcean's dashboard can sign you in; rows created before 9 November 2026 are sealed the first time they are used.
Retention and deletion
- Audit rows are kept 30 days on Free and 365 days on Pro, then deleted by a daily sweep (plans).
- A legal hold (Pro, owner only) stops the deletion of audit rows, approval decisions, change-log rows and invalid-key counts until it is released (audit completeness and legal hold).
- With a SIEM configured, you can turn off local audit history; rows still pass through Gate's durable delivery outbox (up to 100,000 events) on their way to your SIEM.
- Not built yet: deleting a whole project yourself. If you need erasure at the end of a contract, ask us before you sign.
Encryption
- In transit: HTTPS only; gate.odilelabs.com sends HTTP Strict Transport Security for one year, subdomains included.
- At rest: Cloudflare encrypts stored data, and Gate seals the secrets listed above a second time.
- Not built yet: rotation of Gate's sealing key.
Who can reach your project
- Each app has its own key, an exact list of the calls it may make, a per-minute limit and a loop breaker.
- People: one owner admin key; team members with viewer, approver or admin roles; approvers with their own keys. Billing, members, legal hold and company sign-in settings are owner-only.
- Company sign-in through OpenID Connect (Google Workspace, Microsoft Entra ID, Okta or another compatible provider), with 8-hour sessions and an optional rule that stops member keys. No SCIM: a person disabled at the provider keeps an open session until it ends (8 hours at most); revoking the member in Gate ends it at once.
- Every call with a wrong key is counted; the first 20 per project per UTC clock hour get an audit row.
Audit integrity and monitoring
- Audit rows and change-log rows each form a SHA-256 hash chain. Exports carry an HMAC-SHA256 from project key material, and Gate checks an export through its verify endpoints. There is no public key, so that check runs through Gate (audit proof).
- Stream audit rows to your SIEM (JSON or Splunk HEC) through a durable outbox, with an optional sealed header.
- Alerts reach your webhook (optionally signed with HMAC-SHA256) for refusal spikes, loops and unusual traffic.
- Not offered: write-once (WORM) storage.
Availability and recovery
- Status shows the last 30 days of our 5-minute checks. Gate publishes no availability SLA.
- Gate fails closed: if it fails before forwarding a call, the call does not reach your API. What it adds to latency is measured on the home page (fail mode and latency).
- Recovery uses Cloudflare's point-in-time recovery for Durable Objects; we run a weekly restore drill on synthetic objects. This is not an offsite backup.
How changes reach production
- Releases go through our deploy lane: a named commit, the full test suite (921 tests at release 4ac89f2), checks before and after the deploy, and a rollback when a check fails.
- Security-relevant changes are reviewed by an independent model from another AI vendor. For company sign-in, 138 guards were each tested by removing them and confirming a test fails.
Odile's own access
- Odile's operator routes sit behind a separate key. They read aggregate usage counts, change a project's plan, add Machine Access credits, edit phone catalogue listings and run restore drills on synthetic objects; none of them returns audit rows, settings, keys or secrets.
- Gate's code can open the values it seals, so any release of Gate could; releases go through the lane above.
Who processes data for Gate
| Company | What it does for Gate | When |
|---|---|---|
| Cloudflare | Hosting, storage, usage analytics and usage emails | Always |
| Stripe | Card billing: project name and id, call counts | When you upgrade or pay by card |
| PayAI (facilitator.payai.network) | Settles USDC payments made by AI agents (x402): the payer's signed authorization | When Gate submits an x402 payment for settlement |
| Twilio and ElevenLabs, through Odile's voice service | Phone approvals: Odile's voice service receives the project id and name, the approver's number, the app and rule, and up to 6 fields of the held request (300 characters each), and calls the approver | Only when an approver turns phone approvals on |
| Amazon Web Services Marketplace, DigitalOcean | Accounts and billing for projects bought there | Only for those projects |
| Your own providers | Your SIEM, webhook, company sign-in provider, token key sets and agent key directories | Only when you set them |
Certifications, and what is not built yet
- Odile Labs holds no SOC 2 report or ISO 27001 certificate today. Cloudflare, Stripe, Twilio and ElevenLabs hold their own (listed here).
- Not built yet: a third-party penetration test, SCIM, region pinning, WORM storage, deleting a whole project yourself, rotation of Gate's sealing key, and an availability SLA.
- Gate is not offered under a HIPAA business associate agreement: do not send protected health information through it.