Legals
The third parties Exenai uses to deliver its Services, and the business tools that may incidentally hold customer personal data. Forms Schedule A of the Privacy & Data Policy.
Update notice. This version (2026.9) was published on 15 November 2026 and takes effect on 16 December 2026. Until then, version 2026.7 applies. See what is changing.
This list forms Schedule A of the Exenai Privacy & Data Policy. Changes are notified under Section A5.4 of the Data Processing Addendum and may be objected to under Section A5.5.
These providers process Customer Data as part of delivering the Services. Exenai acts as processor and these are its sub-processors.
This section includes third-party services that Exenai provides under its own account as part of the Services. Services that a customer connects under its own subscription and credentials are the customer's Connected Systems under clause 14.12 of the Master Services Agreement and are not Exenai sub-processors.
Cloud hosting for the Exenai Platform and Automation as a Service, including the Toca platform operated by Exenai.
Processing location: Germany (Falkenstein and Nuremberg) for customers in the UK, the EU and any country other than the United States. Ashburn, Virginia, United States, for US customers, provided to Hetzner Online GmbH by its subsidiary Hetzner US LLC.
Cloud services underpinning Exenai Connect, the Connect App Host and the Candidate Experience Platform, and hosting the Exenai-operated Identity Server.
Processing location: Netherlands (Azure West Europe region), for all customers. Backups held within the UK or the EEA.
Licensor of the Toca platform used within Automation as a Service. Technical support access to Exenai-operated production environments, which may include access to Customer Data.
Processing location: United Kingdom.
Outbound email and messaging, including Exenai's service notifications and one-time passcodes, and email sent on a customer's behalf as part of Automation as a Service, such as messages to candidates and contacts and notifications to customer staff.
Processing location: United States, EU. Customer email is sent through an EU data resident sub-account where one is set up for that customer, and otherwise through the United States.
Generation of PDF documents from templates within Automation as a Service.
Processing location: Amazon Web Services, in the United States or the EU depending on the regional endpoint used.
Large language model API for Exenai AI Features, and an AI Client Exenai may use through Exenai Connect, as described in Section 4.
Processing location: United States.
Large language model API for Exenai AI Features, and an AI Client Exenai may use through Exenai Connect, as described in Section 4.
Processing location: United States, EU.
Large language model API for Exenai AI Features, and the AI Client used by Exenai through Exenai Connect to build, configure, support and troubleshoot customer applications, dashboards, reports and automations.
Processing location: United States.
Data residency. Exenai Connect, the Connect App Host, the Candidate Experience Platform and Identity Server are hosted on Microsoft Azure in the West Europe region (Netherlands) for all customers. Backups are held within the UK or the EEA, in a location Exenai selects. Automation as a Service environments are provisioned in the region matching the customer: on Hetzner in Germany for customers in the UK, the EU and any country other than the United States, and on Hetzner in Ashburn, Virginia for US customers, unless otherwise agreed in the Order Form. Their backups are held in the same region or within the UK or the EEA. A customer's environment is not moved between regions without agreement. The customer's connected systems (such as Bullhorn or Invenias) and its own AI Clients may be located anywhere, under the customer's own agreements, and transfers between them and Exenai Connect are the customer's responsibility. Transfer safeguards are set out in Section A10 of the Data Processing Addendum. Model Provider processing is the exception to the above and is described below.
Model Providers. OpenAI, Google and Anthropic are drawn from a pool. Exenai selects, combines and may change the provider used for any given feature at its discretion, and does not publish a per-feature mapping. Customer data processed by Model Providers is not used to train any public model; processing is limited to instance-based API processing to deliver the relevant feature.
These are tools Exenai uses to run its own business. Customer Data does not flow through them as part of delivering the Services, but customer personal data may be held in them incidentally, for example where it appears in correspondence or in notes of a meeting. They are listed for transparency.
Primary business email, calendar and document productivity.
Processing location: United States, EU.
Secondary productivity suite, including SharePoint and OneDrive for document storage. Used occasionally.
Processing location: EU, United Kingdom.
Customer relationship management, marketing, website visitor tracking and support ticketing.
Processing location: United States.
Project management and collaboration.
Processing location: United States.
Accounting and financial records, including customer billing contacts and invoicing.
Processing location: New Zealand, EU.
Usage analytics in Exenai applications. Cookieless. Does not store raw IP addresses or generate persistent identifiers.
Processing location: Estonia (EU), data hosted in the EU.
Website traffic analysis.
Processing location: United States.
Website hosting and website form submissions.
Processing location: United States.
AI assistant used by Exenai staff for drafting, research, email and customer relationship management work, and software development, and on a trial basis for notes of meetings held in Google Meet, on Exenai's business plan with model training disabled.
Processing location: United States.
Dictation and meeting notes used by Exenai staff, on Exenai's business plan with model training disabled. Dictation history is not stored on Wispr's servers. Meeting participants are told when a meeting is being transcribed.
Processing location: United States. Some meeting transcription is carried out by Wispr's own providers in other locations.
Password manager used by Exenai staff, including for credentials Exenai holds to access customer systems on a customer's behalf. Credentials are encrypted on the user's own device before they are stored, so Passbolt cannot read them. Access is protected by multi-factor authentication.
Processing location: EU (Belgium and Germany).
Sign-in to Exenai Connect surfaces and Community User portals is handled by Identity Server, which Exenai operates itself within its Azure environment. It is not a third-party service and is not a sub-processor.
Users may sign in with a Microsoft, Google, Apple or LinkedIn identity, or with a one-time passcode. Where a user signs in with an existing identity, they authenticate directly with that provider using their own credentials and Exenai receives only the resulting assertion. Those identity providers are not Exenai sub-processors. One-time passcodes are delivered by Twilio SendGrid, listed in Section 1.
There are two distinct cases, and they are treated differently.
The customer's own AI Client. Where a customer connects its own Claude, ChatGPT or Microsoft Copilot subscription through Exenai Connect, that AI Client is the customer's tool and is not an Exenai sub-processor. Exenai's processing is limited to the gateway: transporting the request, applying the customer's configured policy controls, and recording the audit log. Processing by that provider is governed by the customer's own agreement with it.
An AI Client operated by Exenai. Exenai also connects its own AI Client through Exenai Connect in order to build, configure, support and troubleshoot applications, dashboards, reports and automations for customers. The AI Client is drawn from Anthropic (Claude), OpenAI (ChatGPT) and Google (Gemini), each listed in Section 1, and Exenai may choose which it uses for a given task. Exenai uses only business plans for this, with model training disabled. Most of this work is done by customers themselves using their own AI Client; Exenai does it on request. In that case Exenai carries out the processing and the AI Client provider is an Exenai sub-processor, listed in Section 1.
Because Exenai Connect provides a live view of connected systems, this work is carried out against live customer data rather than a copy. It is confined to what is necessary for the task, subject to the customer's configured permissions and policy controls, and recorded in the customer's audit log in the same way as any other request through the gateway. Exenai maintains its AI Client subscriptions with model training disabled.
Exenai will give at least 30 days' notice before adding or replacing a sub-processor in Section 1, by updating this page and notifying the customer's registered contact. Customers may object on reasonable data protection grounds as set out in Section A5.5 of the Data Processing Addendum.
Questions about this list can be sent to privacy@exenai.com.
2026.9. Wispr Flow added to business tools for dictation and meeting notes. Anthropic business tool purpose widened to include a trial of meeting notes for Google Meet. ClickUp no longer used for meeting notes. Passbolt added to business tools on 17 November 2026.
2026.8. OpenAI and Google purposes widened to include an AI Client Exenai may use through Exenai Connect. The AI Client operated by Exenai is drawn from Anthropic, OpenAI and Google, on business plans with model training disabled. Anthropic added to business tools for Exenai's internal use of Claude.
2026.7. Twilio SendGrid purpose widened to cover email sent on a customer's behalf within Automation as a Service. Processing location corrected to the United States and the EU, reflecting customers on EU data resident sub-accounts. Actual Reports (PDF Generator API) and Artifex Software (PDF.co) removed; Exenai does not use them under its own account.
2026.6. Distinction added between third-party services Exenai provides under its own account, which are sub-processors, and services the customer connects under its own account, which are Connected Systems. APITemplate.io, Actual Reports (PDF Generator API) and Artifex Software (PDF.co) added; all were engaged but not previously listed.
2026.5. Hetzner United States location named as Ashburn, Virginia. Default Automation as a Service hosting for customers outside the UK, the EU and the United States set to Germany. Backup locations added. Customer responsibility for the location of connected systems and its own AI Clients stated. Reference to transfer safeguards in the Data Processing Addendum added.
2026.4. Webflow replaces Wix as the provider of website hosting and website form submissions. Plausible purpose corrected to usage analytics in Exenai applications.
2026.3. Azure processing location corrected to the West Europe region (Netherlands) for all customers; Exenai does not use Azure data centres in the United Kingdom or the United States. Data residency paragraph rewritten to match. Apple added to the identities users may sign in with.
2026.2. Twilio SendGrid, Tocalabs Limited, Plausible, Microsoft 365 and Xero added; all were engaged but not previously listed. List separated into service data path and business tools. Anthropic purpose widened to cover Exenai's own use of Claude through Exenai Connect for customer development and support work. Azure purpose updated to reflect Exenai Connect and the Connect App Host. Data residency by customer region documented, covering Hetzner and Azure in both EU/UK and US. HubSpot and Wix purposes widened to reflect website tracking and analytics. Authentication section added. AI Client section rewritten to distinguish a customer's own AI Client from one operated by Exenai. Change notice and objection mechanism added.
Questions about this document can go to privacy@exenai.com.