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.
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.
Cloud hosting for the Exenai Platform and Automation as a Service, including the Toca platform operated by Exenai.
Processing location: Germany (EU) for EU and UK customers. United States for US customers.
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.
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 service notifications and one-time passcodes.
Processing location: United States.
Large language model API for Exenai AI Features.
Processing location: United States.
Large language model API for Exenai AI Features.
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. Automation as a Service environments are provisioned in the region matching the customer: on Hetzner in Germany for EU and UK customers, and on Hetzner in the United States for US customers. A customer's environment is not moved between regions without agreement. 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, collaboration and meeting notes.
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.
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, currently Anthropic's Claude, through Exenai Connect in order to build, configure, support and troubleshoot applications, dashboards, reports and automations for customers. Most of this work is done by customers themselves using their own AI Client; Exenai does it on request. In that case Exenai is directing 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.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.
