Sub-processors
Last updated: 27 February 2026
This page lists (1) subprocessors engaged by Tellagen to provide the core service and (2) customer-directed integrations that may receive personal data when enabled by a Customer.
1. Tellagen-appointed subprocessors
| Provider | Purpose | Data categories | Primary region | Transfer safeguards |
|---|---|---|---|---|
| Hetzner Online GmbH | Core hosting and infrastructure | Customer Data, account data, operational metadata | Germany (EU) | EU-hosted |
| Resend Inc. | Transactional email delivery | Email addresses, message metadata, email content | United States | SCCs and/or other lawful safeguards |
| Cloudflare, Inc. (Turnstile) | Bot and abuse protection | Verification token, IP, request metadata | Global | SCCs and/or other lawful safeguards |
| OpenAI, LLC (optional) | AI processing when OpenAI provider is enabled | AI prompt/response content chosen by Customer users | United States | SCCs and/or other lawful safeguards |
| Google LLC (Gemini optional) | AI processing when Gemini provider is enabled | AI prompt/response content chosen by Customer users | United States | SCCs and/or other lawful safeguards |
Website analytics is implemented using Umami and is loaded only when analytics consent is granted. If the Umami endpoint is hosted by a third party, that provider will be listed here before production use.
2. Customer-directed integrations
The following services are activated only when configured by the Customer. In these cases, the Customer controls whether data is sent and under what legal basis.
| Service | Purpose | Typical data shared |
|---|---|---|
| Slack | Incident channels and response messaging | User profile and incident communication data |
| Google Meet | Incident meeting creation and coordination | Meeting metadata and OAuth-linked account data |
| Intercom | Link customer conversations to incidents | Conversation content and contact metadata |
| PagerDuty / Opsgenie / Rootly | On-call schedule and escalation sync | Schedule and responder metadata |
| Stripe / Recurly | Billing-related customer enrichment features | Customer/account metadata queried by Customer config |
| Customer resolver endpoint | Customer-owned enrichment API integration | Data fields configured by the Customer |
3. Change management
We will update this list before new Tellagen-appointed subprocessors begin processing personal data and provide Customer notice as required by our DPA.