Sub-processors

Who is on this list

These are the sub-processors of our Data Processing Agreement: the vendors we engage to run the hosted service that process personal data on our customers' behalf. We tell every organization's owners by email at least 30 days before a new one starts processing their data, and they may object (DPA, section 8).

The services you connect are not on this list. Google, Microsoft, Slack, the other integrations your people connect, the MCP servers they add, and the chat platforms where they talk to their assistant are your own chosen services: we connect to them on your instruction, with your people's own accounts and credentials, and their vendors act under your own agreements with them. Chat with Work Desktop on your computers and self-hosted installs on your servers run under your control, not ours.

Hetzner

Company: Hetzner Online GmbH, Gunzenhausen, Germany
What it does for us: Servers for the app, its database, stored files, malware scanning, and the sandbox code runs in; the off-site copy of our encrypted backups; the servers our error tracker, support desk, and analytics run on; and its Inference API for the free model.
Data it receives: Everything the service holds: accounts, chats, files, cached text, tokens, encrypted by the app where the DPA's annex says. For the free model: the question, the chat, and what tools returned, which Hetzner states it doesn't store.
Where: Germany (Nuremberg) and Finland (Helsinki: the off-site backups, support desk, and analytics).
Safeguard: In the EU. No transfer outside the EU/EEA.

Google Cloud (Vertex AI)

Company: Google, part of Alphabet Inc., USA
What it does for us: Gemini models when a chat uses one; summaries of long chats, text from scanned PDFs, and descriptions of images; transcribing dictation; holding files too large to send inline while a model reads them.
Data it receives: The question, the chat, files and tool results the answer needs, and dictation recordings.
Where: The EU (Vertex AI's eu multi-region, and a Cloud Storage bucket in the EU).
Safeguard: Processed in the EU. The provider belongs to a US group, so its data processing terms include the European Commission's standard contractual clauses, and the group is certified under the EU-US Data Privacy Framework, for any access from outside the EU.

Microsoft Azure (AI Foundry)

Company: Microsoft Corporation, USA
What it does for us: GPT models when a chat uses one; chat titles; the free model's answers while Hetzner is busy.
Data it receives: The question, the chat, and the files and tool results the answer needs. We ask Azure not to store responses.
Where: The EU (a resource in Germany West Central, EU Data Zone deployments).
Safeguard: Processed in the EU. The provider belongs to a US group, so its data processing terms include the European Commission's standard contractual clauses, and the group is certified under the EU-US Data Privacy Framework, for any access from outside the EU.

Amazon Web Services (Bedrock)

Company: Amazon Web Services, part of Amazon.com, Inc., USA
What it does for us: Claude models when a chat uses one, and in place of Gemini or Azure for a step they're too busy for. AWS runs these models in its own accounts, so Anthropic has no access.
Data it receives: The question, the chat, and the files and tool results the answer needs.
Where: The EU (EU cross-region inference profiles, called from Frankfurt).
Safeguard: Processed in the EU. The provider belongs to a US group, so its data processing terms include the European Commission's standard contractual clauses, and the group is certified under the EU-US Data Privacy Framework, for any access from outside the EU.

Amazon Web Services (SES and S3)

Company: Amazon Web Services, part of Amazon.com, Inc., USA
What it does for us: Sending account and notification emails; receiving mail sent to bots' trigger addresses, held in S3 until we read it, at most 7 days.
Data it receives: Recipients' email addresses and the emails we send, which never carry chat content; mail people send to a trigger's address, encrypted with our key.
Where: Germany (Frankfurt).
Safeguard: Processed in the EU. The provider belongs to a US group, so its data processing terms include the European Commission's standard contractual clauses, and the group is certified under the EU-US Data Privacy Framework, for any access from outside the EU.

Bunny CDN

Company: BunnyWay d.o.o., Ljubljana, Slovenia
What it does for us: Delivering the app's static files: scripts, styles, fonts, and images.
Data it receives: The IP address and browser details of whoever loads a page, as with any web request. Never chats, files, or account data.
Where: An EU company, serving from its edge location nearest the browser, which can be outside the EU.
Safeguard: The company is in the EU. Requests from browsers outside the EU may be served from edge locations outside it.

Stripe

Company: Stripe Payments Europe, Ltd., Ireland, part of Stripe, Inc., USA
What it does for us: Plans, top-ups, and payments.
Data it receives: Account and billing data only: the billing contact, organization, plan, and payments. Card details go to Stripe directly and never reach us. Never chats or files.
Where: The EU and the USA.
Safeguard: Stripe's data processing terms, with the standard contractual clauses and its EU-US Data Privacy Framework certification.

Odoo

Company: Odoo S.A., Belgium
What it does for us: Our accounting, and issuing invoices and credit notes.
Data it receives: Billing data only: billing name, address, country, VAT ID, what was bought, its price and VAT, and the payment's reference. Never chats or files.
Where: France (Odoo Online).
Safeguard: In the EU. No transfer outside the EU/EEA.

Push notification services

Company: Apple Inc. (Apple Push Notification service, and Safari's), Google LLC (Firebase Cloud Messaging, and Chrome's), Mozilla (Firefox's), Microsoft Corporation (Edge's), USA
What it does for us: Delivering notifications, only to people who turn them on.
Data it receives: A device's push address. Browser notifications are encrypted so the push service can't read them. Notifications to the phone apps carry no chat content: the organization's name, what happened, a link, and an encrypted identifier; the app fetches the words from our servers in Germany. While a phone follows an answer, the kind of step it's taking and in which service ("Searching Todoist"), never what it searches for.
Where: The USA and global.
Safeguard: No chat content passes through them in a form they can read. Apple, Google, and Microsoft are certified under the EU-US Data Privacy Framework; Firefox picks Mozilla's service itself, and it receives only encrypted notifications.

Web search, only when you turn it on

Web search is off unless your organization's owners or admins allow it and a person turns it on in a chat. Then the search queries the model writes, which can contain words from the chat, go to Google Search (Gemini models) or Microsoft Bing (GPT models), outside the EU, under those providers' own terms as search providers. Turning it on is your instruction to make that transfer; they aren't our sub-processors.

Run by us

These run on our own servers at Hetzner (above), so no other company receives what they hold: Bugsink, our error tracker, in Germany, whose reports carry ids and code locations, never content; Chatwoot, our support desk, and Plausible, our cookieless website analytics, in Finland. Our second backup copy is on a backup server PlentyLabs operates itself in Berlin, Germany, encrypted before it leaves production.

Other providers, without your data

Cloudflare answers DNS queries for chatwithwork.com, and sees no application data. GitHub holds our source code and builds our releases; it receives no customer content, and an issue we file there about a support request names the person only by an internal id.