Subprocessors
Codi engages the third-party subprocessors below to help deliver the service. Each processes customer data only as needed for its stated purpose and under contractual data-protection obligations.
| Subprocessor | Purpose | Location |
|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting and managed services: Bedrock (model inference), S3 (object storage), SQS (queues), and OpenSearch (search). Image generation (Amazon Nova Canvas) and bulk knowledge-base embedding (Bedrock batch inference) run in us-east-1 — see the Privacy Policy §4. | eu-west-1 (Ireland); us-east-1 (United States) for image generation and bulk embedding |
| MongoDB Atlas | Primary application database and vector search for knowledge retrieval. | eu-west-1 (Ireland) |
| Stripe | Subscription billing, payment processing, and metered usage reporting. | United States / global |
| Infobip | Transactional email and messaging delivery. | European Union |
| ElevenLabs | Text-to-speech and voice generation for agent voice features. | United States |
| PostHog | Product analytics, session replay, and error tracking for the website, application, and API. | United States |
| Codified Development (Pty) Ltd | Outsourced engineering, support, and operations provider. Its staff may access customer data only as needed to operate and support the service, under contract and confidentiality obligations. | South Africa |
| Atlassian | Confluence content ingestion — engaged only when a customer connects a Confluence knowledge source. | As configured by the customer |
Customer-directed destinations. Custom MCP servers, SIEM sinks, and self-hosted or third-party model endpoints that a customer configures are destinations the customer directs data to, not Codi subprocessors. The customer controls those integrations and is the data controller for the data sent to them.
Changes to this list are announced on this page in advance of taking effect.