Subprocessors
Caddy Technologies Inc (“Caddy”) may engage third-party service providers (“Subprocessors”) to support the operation of the Caddy Service.
These Subprocessors support the operation of the Caddy Service, including infrastructure, AI model processing, analytics, integrations, memory, search, browser automation, communications, and security. Where a Subprocessor processes Customer Data on behalf of Caddy, it does so subject to appropriate safeguards.
This list reflects subprocessors used by the Caddy Service in production environments.
Caddy requires Subprocessors to maintain appropriate security and confidentiality protections for Customer Data.
Infrastructure & Hosting
| Subprocessor | Purpose | Data Processed | Primary Processing Region |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting and managed access to AI models | Application infrastructure, storage, and prompts routed to hosted AI models | United States |
| Supabase | Database and authentication infrastructure | Application database storage and authentication data | United States |
| GitHub | Code repository, version control, and CI/CD | Application source code and deployment metadata | United States |
AI & Machine Learning Providers
| Subprocessor | Purpose | Data Processed | Primary Processing Region |
|---|---|---|---|
| Anthropic | AI model provider | Prompts and contextual inputs used to generate AI outputs | United States |
| OpenAI | AI model provider | Prompts and contextual inputs used to generate AI outputs | United States |
| Deepgram | Speech recognition | Audio input and transcription requests used for speech processing | United States |
| Exa | AI-powered web search | Search queries used to retrieve web results | United States |
Analytics, Observability & Evaluation
| Subprocessor | Purpose | Data Processed | Primary Processing Region |
|---|---|---|---|
| PostHog | Product analytics and feature flagging | Usage analytics and product interaction data | United States |
| Datadog | Monitoring, logging, and system observability | Application performance data, telemetry, and system logs | United States |
Integrations & Authentication
| Subprocessor | Purpose | Data Processed | Primary Processing Region |
|---|---|---|---|
| Nango | Integration authentication and OAuth management for connected third-party apps | Integration authentication and credential handling | United States |
Financial Account Connectivity
| Subprocessor | Purpose | Data Processed | Primary Processing Region |
|---|---|---|---|
| Plaid | Financial account connectivity and data aggregation | Financial account information accessed from your financial institution, such as account and routing numbers and transactions | United States |
Memory & Data Processing
| Subprocessor | Purpose | Data Processed | Primary Processing Region |
|---|---|---|---|
| Mem0 | Memory storage and retrieval | User-provided content and derived memory data | United States |
| Parse | Web scraping and structured data parsing | Web page content and parsing requests | United States |
Automation Infrastructure
| Subprocessor | Purpose | Data Processed | Primary Processing Region |
|---|---|---|---|
| Browserbase | Browser automation infrastructure | Data required to execute automated browser sessions | United States |
Security & Vulnerability Scanning
| Subprocessor | Purpose | Data Processed | Primary Processing Region |
|---|---|---|---|
| Veria Labs | Automated source-code vulnerability scanning | Application source code | United States |
Customer Communications
| Subprocessor | Purpose | Data Processed | Primary Processing Region |
|---|---|---|---|
| Loops | Lifecycle and transactional email delivery | Email address and communication preferences | United States |
| Linq | iMessage delivery infrastructure | Message content and metadata necessary to send and receive messages through the Service | United States |
| Photon | iMessage delivery infrastructure | Message content and metadata necessary to send and receive messages through the Service | United States |
AI Model Processing
Caddy may send prompts and related context to AI model providers in order to generate outputs for the Service.
Where supported by the provider, Caddy configures model providers to limit retention of prompts and outputs.
For example:
- Requests sent to Anthropic may be processed under zero data retention configurations where enabled.
Model providers may process prompts temporarily in order to generate responses.
Caddy does not train foundation models using Customer Data.
Changes to Subprocessors
Caddy may update this list of Subprocessors from time to time.
We will update the “Last Updated” date above when this list changes.
Contact
Questions regarding subprocessors or data processing practices may be submitted to contact@trycaddy.ai.