Sub-processors
Last updated: 2026-05-10
Coagentic engages the following third-party sub-processors to deliver the Services. We notify customers at least 14 days before adding or replacing a material sub-processor (see DPA, §6).
| Sub-processor | Purpose | Region | Status | DPA |
|---|---|---|---|---|
| Hetzner | Compute, managed Postgres host volumes, network — the hosting layer the platform runs on | EU (Germany / Finland) | Active | View → |
| Cloudflare | CDN, DNS, edge TLS, WAF, transactional email routing for *@coagentic.work | Global edge | Active | View → |
| Polar | Payment processing and subscription billing for paid Coagentic plans | US / EU | Active | View → |
| DeepSeek | LLM inference for the AI agent (flash + reasoner models on a single endpoint) | Configurable; default endpoint operated by DeepSeek | Active | On request |
| Sentry | Application error monitoring — active only when SENTRY_DSN is configured for the deployment | EU | Optional | View → |
Customer-connected providers
Services you connect to your own projects — payments (Polar), email (Resend), SMS (Twilio), analytics (Google Analytics), object storage (Cloudflare R2) — are processors engaged by you, not sub-processors of Coagentic. We pass data to them only when your project's workflow or live site calls them, using the credentials you supply.
You are responsible for executing any required agreements with those providers directly. Their published DPAs apply to that relationship.
Object to a sub-processor on reasonable data-protection grounds within 14 days of notice by emailing [email protected].