Odile Gate

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

Where Gate runs and where data lives

What Gate keeps about your calls

Keys, secrets and the change log

Retention and deletion

Encryption

Who can reach your project

Audit integrity and monitoring

Availability and recovery

How changes reach production

Odile's own access

Who processes data for Gate

CompanyWhat it does for GateWhen
CloudflareHosting, storage, usage analytics and usage emailsAlways
StripeCard billing: project name and id, call countsWhen you upgrade or pay by card
PayAI (facilitator.payai.network)Settles USDC payments made by AI agents (x402): the payer's signed authorizationWhen Gate submits an x402 payment for settlement
Twilio and ElevenLabs, through Odile's voice servicePhone 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 approverOnly when an approver turns phone approvals on
Amazon Web Services Marketplace, DigitalOceanAccounts and billing for projects bought thereOnly for those projects
Your own providersYour SIEM, webhook, company sign-in provider, token key sets and agent key directoriesOnly when you set them

Certifications, and what is not built yet