Service Providers and Subprocessors
Published on 2026-10-17
Provider directory
The providers below support different parts of the service. A provider may be our processor, the customer’s authorised subprocessor or an independent controller for a separate activity. This directory is not a representation that every provider receives every customer’s content.
Our permitted processing regions are the EU, UK and US, depending on the service and account configuration. Our policy excludes processing in China. Account-specific regional restrictions cover the processing expressly identified in the Order.
The DPA governs customer-directed processing and subprocessor changes. Enterprise Orders may set an account-specific list.
Supplier information is based on suppliers’ published disclosures, contractual commitments and information they provide. The Provider uses reasonable efforts to keep that information current but does not represent that it has independently verified every disclosure or audited each supplier’s internal operations. This does not exclude the Provider’s obligations or liability under applicable data protection law, including required checks, transfer safeguards and responsibility for Subprocessors.
| Provider | Service | Scope |
|---|---|---|
| Clerk | Account authentication and session management | Account identity and authentication information; role and scope depend on the activity. |
| Stripe | Payments and billing | Payment-interface, transaction and billing information; separate controller activities are described in Stripe’s notice. |
| PostHog | Product and website analytics; PostHog Conversations support | Usage events and device information; support messages and account identity when using support. |
| Google Ads | Website and application advertising measurement | Advertising events and click identifiers; not a general customer-content model processor. |
| OpenRouter | Model routing, research, generation and embeddings | Necessary Inputs and content for model routing, generation, research and embeddings. Model routes are restricted to zero-data-retention endpoints and exclude providers based in China and endpoints hosted in China. Third-party tools such as web search follow their own providers' retention. |
| Hetzner | Hosting and infrastructure | Customer content, databases, application services and infrastructure records. |
| Twenty CRM (self-hosted) | Contact enquiries and customer relationship management | Operated on our own infrastructure. The software vendor is not listed as a recipient solely because we use its software. |
| Google Workspace | Hosted business email | Email addresses, message content, attachments and delivery metadata for business, service and support correspondence. |
| Google Fonts | Font delivery | Visitors’ IP addresses and request information are sent to Google when fonts load. |
Model routing and regional choices
Model routes are restricted to zero-data-retention endpoints and exclude providers based in China and endpoints hosted in China. Third-party tools such as web search follow their own providers' retention. Account-specific model-region restrictions are agreed in the Order.
We use Google Workspace for hosted business email. We may use an email delivery service for particular mailings. No delivery provider has been selected.
Changes and objections
For authorised Subprocessors, the DPA provides at least 15 days’ advance email notice to the registered administrator, without requiring a separate subscription, and a reasonable data-protection objection process. New or changed routes must first satisfy the applicable authorisation and transfer requirements. Substituting a model version within an already authorised route does not itself authorise a new recipient or purpose.
Full terms, including objection, suspension of affected processing and both parties’ termination rights: /dpa/#clause-9.