Sub-processor List
Last updated: 2026-10-08
Version 05ea68b207da
We publish this list so customers can see exactly who processes their data. We give 30 days’ notice before adding a new sub-processor.
Current sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Amazon Web Services EMEA | Application hosting — eu-central-1 | Frankfurt, Germany |
| Supabase | Database, authentication, file storage — eu-central-1 | Frankfurt, Germany |
| Cloudflare | DNS, and off-site storage of encrypted backups | Germany / United States |
| Resend | Transactional email — account, billing and notification messages | United States |
| Anthropic | The AI-assisted features, when a user invokes one | United States |
| Sign-in with Google; website analytics where the visitor has consented; the website translation widget where the visitor requests it | United States | |
| None | Payment processing | Not applicable — see below |
No card payment processor appears on this list because there is none. Subscriptions are paid by bank transfer; the card gateway is built but not enabled, so no card data reaches us or anybody acting for us. If that changes, a processor is added here with the 30 days’ notice the next section describes.
Two rows a reader may have seen open before are now filled. The regions are stated as the provider reports them, not as we assume them: eu-central-1 was read from the hosting account rather than inferred from the word “Frankfurt”. Where a provider operates globally and we cannot pin a single region, both countries are named rather than one guessed. The off-site backup copies are encrypted before they leave this server; the storage provider is named above and the product it runs on is not, deliberately — see /legal/security, which states the same property without handing anyone a target.
A customer-specific exception: a tenant that supplies its own key for a third-party voice or messaging service — ElevenLabs, or a Telegram bot — directs data to that service on its own instruction. Those are not our sub-processors and are not listed here, because we neither choose them nor hold the relationship; they are named in the Data Processing Addendum as customer-directed recipients.
Changes to this list
We give at least 30 days’ notice before adding a sub-processor, and a customer may object on reasonable grounds. Notice is given by email to the account’s billing contact.