Legal
Subprocessors
Third parties that may process customer data on Codexa's behalf. Each is used only when the operator of your Codexa instance has configured it; none is contacted otherwise.
Last revised
Current list
| Provider | Purpose | Data | Used when |
|---|---|---|---|
| PostgreSQL hosting (operator-defined) | Primary database | All application data | Always; the operator chooses the host |
| Anthropic | AI model provider | Prompts, conversation messages, project files the agent reads | Only when an Anthropic key is configured and you start a run |
| OpenAI | AI model provider | Prompts, conversation messages, project files the agent reads | Only when an OpenAI key is configured and you start a run |
| Resend | Transactional email | Email address, email content (verification, reset, invitations) | Only when a Resend key is configured; otherwise mail is queued in an outbox |
| Stripe | Payments (international) | Email, billing details you enter on Stripe's pages, subscription identifiers | Only when Stripe is configured and you check out in USD |
| Razorpay | Payments (India) | Email, billing details you enter on Razorpay's pages, subscription identifiers | Only when Razorpay is configured and you check out in INR |
| Vercel | Deployment target | Project build output, environment variables you choose to deploy | Only when a Vercel token is configured and you deploy to Vercel |
| GitHub | Sign-in, import, push | GitHub account id, repository contents you import or push | Only when GitHub OAuth is configured and you connect your account |
| E2B | Sandbox driver | Project files and commands executed in the sandbox | Only when the operator selects the E2B driver |
Codexa does not use third-party analytics, advertising, session replay, or error-tracking services.
Changes to this list
We update this page before a new subprocessor handles customer data. Team and Enterprise customers can ask to be notified by email.