Subprocessors
Last updated: 31 October 2026
Subprocessors
Section titled “Subprocessors”These companies process personal data on our behalf to run WORK³. We give at least 30 days’ notice before adding or replacing one, as set out in the data processing agreement.
| Company | What for | Where the data is | Safeguard |
|---|---|---|---|
| Hetzner Online GmbH | Servers, database, file storage and backups | EU (Finland, Germany) | EU company |
| Google Ireland Ltd | Sign in with Google; sending emails such as sign-in codes, invitations and notifications | EU, may be processed in the US | Data processing terms, EU–US Data Privacy Framework, standard contractual clauses |
| Cloudflare, Inc. | Bot check (Turnstile) on the sign-in page, before a code is emailed | Global network, may be processed in the US | Data processing terms, EU–US Data Privacy Framework, standard contractual clauses |
| Anthropic, PBC | The built-in AI assistant when it runs on WORK³ AI credits: the question and what the assistant looks up for it | US | Commercial terms with data processing addendum, standard contractual clauses; not used for training |
Services you connect
Section titled “Services you connect”These are off until someone in your workspace connects them. When connected, WORK³ sends them only what the integration needs. They are not subprocessors of NOD³: your organisation (or you, for an AI assistant) chooses them and uses them under its own agreement with the provider, and can disconnect them at any time.
| Service | What WORK³ sends | Read more |
|---|---|---|
| Slack | Notifications and messages for the channels you choose | Slack |
| Attio, HubSpot, Pipedrive | Project and deal fields you map; WORK³ reads the client records you link | Attio, HubSpot, Pipedrive |
| Google Drive | Nothing: your browser opens Google’s file picker, and WORK³ keeps the name, type and link of the files you pick | Google Drive |
| Claude (Anthropic), ChatGPT (OpenAI) and other AI assistants | What the assistant asks for while you use it: projects, items and comments you can see, in the one workspace you picked | Claude and ChatGPT |
| Webhooks, REST API and calendar links | Whatever your own system asks for with the key or link you created | Webhooks, REST API, Calendar |
The built-in AI assistant is different: when it runs on WORK³ AI credits, Anthropic processes the data for us and is listed as a subprocessor above. If your workspace uses its own Anthropic or OpenAI key, that provider works under your organisation’s agreement instead. An admin can turn the assistant off under Settings → AI assistant.
Voice input in the assistant runs in your browser, and WORK³ never receives the audio. If your browser cannot turn speech into text on your device, it sends the audio to its own speech service (Google in Chrome, Microsoft in Edge, Apple in Safari) under your agreement with that browser. That provider is not a subprocessor of NOD³.
AI assistants in more detail
Section titled “AI assistants in more detail”- WORK³ does not send anything to an AI provider on its own. An assistant gets data only when a person has connected it and asks it something.
- The assistant acts as that person: it sees only what they can see, in one workspace, and can change things only if they allowed it.
- What the provider does with the data (storage, training, location) is governed by the person’s or organisation’s own agreement with Anthropic or OpenAI. Business plans of both providers do not train on your data by default; check your plan.
- Owners can see and revoke every connection under Settings → Integrations, and each connection is in the audit log.
WORK³ · powered by NOD³