Sub-processors

Last updated September 9, 2026

TourMan uses the following sub-processors to provide the Service. We'll update this page — and, for a material change, notify every organization Admin by email — before adding a new one, giving you a chance to object (see the Data Processing Agreement, §4.2).

Current sub-processors

Sub-processorWhat it does for usWhere
Google WorkspaceHosts info@tourman.app and each organization's dedicated booking mailbox; Gmail API access to parse forwarded booking emailsEU
StripeBilling and payment processingUS, with EU safeguards (Data Privacy Framework + Standard Contractual Clauses)
ResendSends transactional emails (password resets, notifications)US, with EU safeguards (Standard Contractual Clauses + Data Privacy Framework)
HetznerHosts the application and databaseGermany (EU)

What's not on this list, and why

Meta / WhatsApp isn't a TourMan sub-processor. Each organization creates and controls its own WhatsApp Business Account directly with Meta — including paying Meta directly — and simply authorizes TourMan to send messages through it. Meta is each organization's own vendor, not one TourMan selected. See the DPA, §4.4, for the full reasoning.

Anthropic (for the optional AI Concierge feature) isn't a TourMan sub-processor either. An organization that enables AI Concierge supplies its own Anthropic API key and account, billed directly to that organization — Anthropic is that organization's own vendor for this feature, not one TourMan selected. See the DPA, §4, for the full reasoning.

Sub-processors — TourMan