Legals
What changes in our Master Services Agreement, Privacy & Data Policy and Subprocessor List on 16 December 2026, with the new wording for each change.
On 15 November 2026 we published updated versions of three documents: the Master Services Agreement (2026.5), the Privacy & Data Policy including the Data Processing Addendum (2026.8), and the Subprocessor List (2026.9). Under clause 2.8 of the Master Services Agreement, they take effect on 16 December 2026. Until then, the previous versions apply. A copy of any previous version is available on request.
You do not need to do anything. If an update materially disadvantages you, clause 2.8 lets you end the affected Services without penalty by telling us before it takes effect. You can also object to the subprocessor changes under Section A5.5 of the Data Processing Addendum. Questions go to privacy@exenai.com.
Makes clear that the Data Processing Addendum takes priority over the Master Services Agreement on data protection matters, matching what the Addendum already says.
New wording, with added words in bold: 2.6 If there is a conflict or inconsistency between the documents forming the Agreement, they shall be interpreted in the following order of precedence: (a) the terms specified in the Order Form; (b) any Special Terms or Statement of Work appended to or referenced in the Order Form; (c) the terms of this Master Services Agreement; (d) the applicable Privacy & Data Policy and Acceptable Use Policy and Schedule 1, Support Services herein, except that on matters of data protection the Data Processing Addendum prevails over this Master Services Agreement.
Adds that an update to our terms can never reduce the overall protection given to personal data under the Data Processing Addendum.
New wording, with added words in bold: 2.8 Changes to this Agreement. Exenai may update this Agreement and the documents it incorporates by publishing the updated version at exenai.com/legals and giving the Customer at least 30 days' notice by email. The update takes effect at the end of the notice period. If an update materially disadvantages the Customer, the Customer may terminate the affected Services without penalty by written notice given before the update takes effect. Updates under this clause cannot change the Fees, any agreed price commitment, or the Customer's term, and cannot reduce the overall level of protection given to personal data under the Data Processing Addendum. Exenai keeps a copy of each version and will provide it on request. Changes required by law, or that do not disadvantage the Customer, may take effect sooner.
Links changes to the Privacy & Data Policy to the 30-day notice process in clause 2.8.
New wording, with added words in bold: Privacy Policy means the Exenai Privacy & Data Policy (including the incorporated Data Processing Addendum), as updated under clause 2.8.
Removed: "amended from time to time."
Separates the AI tools you connect yourself, which remain under your own agreements, from the AI tool Exenai uses to build and support for you, which is an Exenai subprocessor.
New wording, with added words in bold: AI Client means a third-party artificial intelligence application or model interface (including, for example, Claude, ChatGPT, or Microsoft Copilot) connected by the Customer, its Users or anyone acting for it, other than Exenai, to send requests through Exenai Connect. AI Clients are not part of the Services.
Removed: "or on behalf of"
New wording: Exenai AI Client means an artificial intelligence application that Exenai connects through Exenai Connect to build, configure, support or troubleshoot for the Customer, as described in Section A5.7 of the Data Processing Addendum. An Exenai AI Client is not an AI Client, and its provider is an Exenai subprocessor.
Confirms that applications we build for you with our own AI tool are still yours.
New wording, with added words in bold: Customer Artefact means any application, dashboard, Agent configuration, workflow, or similar item created by or on behalf of the Customer using an AI Client or an Exenai AI Client through Exenai Connect (also referred to as a "Connect Application").
Points to the published Subprocessor List instead of Schedule 2.
New wording, with added words in bold: Model Providers means the third-party large language model providers whose APIs Exenai uses to deliver Exenai AI Features, as listed in the Subprocessor List. Exenai may select, combine, and change Model Providers for any Exenai AI Feature at its discretion and does not publish which Model Provider serves which feature.
Removed: "Schedule 2"
A new clause. You configure the self-service parts of the Services, such as Candidate forms, field mappings, candidate profiles and job adverts, and Connect permissions, rate limits, guardrails and alerts, and you decide what that configuration captures and displays. Work we build for you as Professional Services stays under clause 5.
New wording: 4.11 Customer configuration. The Services include functionality that the Customer configures for itself, including forms, field mappings, candidate profiles, job advertisements and generated documents in the Candidate Experience Platform, and Connected Systems, Customer Artefacts, API permissions, rate limits, policy controls, guardrails and alerts in Exenai Connect. Exenai provides, operates and secures that functionality. The Customer decides how it is configured, including which data is captured, mapped to its Connected Systems, held in the Services or displayed to Users and Community Users, and who receives alerts, and the Customer is responsible for that configuration and its results. Exenai does not review the content of the Customer's configuration and is not obliged to do so. Onboarding, training and support provided by Exenai do not change this. Where Exenai builds or configures something for the Customer as Professional Services, clause 5 applies to that work.
Replaces a short list of processor commitments with a reference to the full Data Processing Addendum, so there is one set of processor terms.
Previous wording: 7.5 Where Exenai processes personal data on behalf of the Customer, it shall: act only on documented instructions from the Customer; ensure that persons authorised to process personal data are under appropriate obligations of confidentiality; assist the Customer in responding to data subject rights and complying with legal obligations under applicable data protection laws; make available information necessary to demonstrate compliance and allow for audits (subject to reasonable notice and safeguards); and upon termination of the Agreement, delete or return Customer personal data, except where retention is required by law.
New wording: 7.5 Where Exenai processes personal data on behalf of the Customer, it does so as processor on the terms of the Data Processing Addendum, which sets out Exenai's obligations under Article 28 of the UK GDPR and the EU GDPR, including acting only on the Customer's documented instructions, confidentiality, security, subprocessors, assistance with data subject rights and compliance, breach notification, deletion or return of personal data, and audits.
Confirms that the disclaimer for your own AI tools does not apply to the AI tool Exenai operates, which is our subprocessor.
New wording, with added words in bold: 14.3 AI Clients (the Customer's tools). AI Clients are not part of the Services. The Customer's use of an AI Client is governed by its own agreement with the relevant provider, and the Customer is responsible for maintaining appropriate terms with that provider, including data processing terms. Exenai is not responsible or liable for the acts, outputs, availability, or data handling of any AI Client or its underlying model provider. Once data has passed through the gateway to an AI Client, it is outside the scope of Exenai's processing. All charges for AI Clients and their underlying models are payable by the Customer under its own agreements with those providers and are not included in the Fees. This clause does not apply to an Exenai AI Client, whose provider acts as Exenai's subprocessor under Section A5.7 of the Data Processing Addendum.
Points to the published Subprocessor List.
New wording, with added words in bold: 14.4 Exenai AI Features (Exenai's providers). Exenai AI Features are delivered using Model Providers under Exenai's own agreements. Model Providers act as Exenai's subprocessors and are listed in the Subprocessor List. Exenai commits that Customer Data processed through Exenai AI Features is not used to train any public models; processing is limited to instance-based API processing to deliver the feature. Exenai may select, combine, and change Model Providers at its discretion in accordance with the subprocessor change mechanism in the Privacy Policy.
Removed: "Schedule 2 and Exenai's published subprocessor list"
Replaced with a pointer to the published Subprocessor List, which already includes everything Schedule 2 listed and is kept up to date.
Previous wording: Schedule 2 listed Hetzner and Microsoft Azure with their details, the Model Providers (OpenAI, Google and Anthropic) for Exenai AI Features, other subprocessors by category, data transfers and compliance.
New wording: Schedule 2: Subprocessors. The subprocessors Exenai uses to provide the Services, including its hosting providers and Model Providers, are listed with their roles and processing locations in the Subprocessor List published at exenai.com/legal/subprocessor-list, which forms Schedule A to the Privacy Policy. Hosting locations are set out in clause 7.6. Subprocessors are engaged, and changes notified, under Section A5 of the Data Processing Addendum, and transfers outside the UK and the EEA are made under Section A10.
Adds keeping our business contact records accurate, including with HubSpot data enrichment, to the purposes for which we process personal data as a controller.
New wording, with added words in bold: ... keeping a record that users of our platforms have accepted our User Notice and Acceptable Use Policy; keeping our business contact and company records accurate and complete, including with business information from HubSpot's data enrichment service (see Section 4.3); and maintaining system security and preventing fraud. The legal bases include legitimate interests (e.g. business analytics, service improvement, keeping business contact records accurate, and keeping records of notice acceptance).
A new section explaining where the personal data we hold as a controller comes from, including HubSpot data enrichment, what HubSpot adds, that HubSpot acts as an independent controller, and how to object.
New wording: 4.3 Where We Get Personal Data From. Most of the personal data we hold as a controller comes directly from you, from your employer where it is our customer or prospective customer, or from your use of our website and services.
HubSpot data enrichment. We use HubSpot as our customer relationship management (CRM) system. For business contacts and companies in our CRM, we use HubSpot's data enrichment service, which adds business information from HubSpot's own commercial dataset to fill gaps in our records. For individuals, this may include job title, role and seniority, employer, business location, business phone number and links to professional social media profiles. It does not include special categories of personal data. We use this information to keep our business records accurate and to understand the organisations and people we work with, on the basis of our legitimate interests.
To match records, business contact and company details from our CRM (such as name, business email address, employer and website domain) are shared with HubSpot, Inc. For this service HubSpot acts as an independent controller, not as our processor, and may use that information to maintain and develop its own commercial dataset, as described in HubSpot's privacy policy. HubSpot, Inc. is in the United States; see Section 7.
You can object to enrichment at any time by contacting privacy@exenai.com. We will stop enriching your record and remove the enriched information from it. Data enrichment applies only to Exenai's own business records. It is never applied to Customer Data we process on behalf of our customers.
A new section on recording and transcribing meetings: the tools we use, what participants are told, what is captured, who can see it, model training, our lawful basis, where it is processed, retention, and how to object or ask for deletion. Section 4.1 adds meeting recordings, transcripts and notes to the data we collect, Section 3.1 adds meeting notes to our purposes and legitimate interests, and Sections 7 and 8.1 point to Section 4.4. Added on 16 November 2026; it applies from that date because it describes how we already work and does not change our obligations to you.
New wording: See Section 4.4 of the Privacy & Data Policy.
Names HubSpot as an independent controller for data enrichment.
New wording: 5.4 Independent Controllers. HubSpot, Inc. receives business contact and company details from our CRM for its data enrichment service, and acts as an independent controller for that purpose, as described in Section 4.3.
Adds the transfer to HubSpot for data enrichment and the safeguards that apply.
New wording, added: Business contact and company details from our CRM are also transferred to HubSpot, Inc. in the United States for data enrichment (Section 4.3), under the UK Extension to the EU–US Data Privacy Framework, with Standard Contractual Clauses and the UK Addendum also in place.
Says that your configuration of the Services, including what your forms, profiles and apps capture and display, is part of your instructions to us.
Previous wording: A2.2 The Order Form, this Policy, the Master Services Agreement, the Customer's configuration of the Services, and the Customer's use of the Services together constitute the Customer's documented instructions.
New wording: A2.2 The Order Form, this Policy, the Master Services Agreement, the Customer's configuration of the Services, and the Customer's use of the Services together constitute the Customer's documented instructions. The Customer's configuration includes the forms, field mappings, candidate profiles, job advertisements, Customer Artefacts, Connected Systems, permissions and policy controls it sets up, and so determines which personal data the Services capture, hold and display.
We will tell you immediately if we think an instruction breaks data protection law.
New wording, with added words in bold: A2.3 Exenai will immediately inform the Customer if, in its opinion, an instruction infringes Data Protection Law.
Says Exenai "carries out" rather than "directs" processing when it uses its own AI tool for you, which better reflects that we act on your instructions.
New wording, with added words in bold: A5.7 Where Exenai connects its own AI Client through Exenai Connect in order to build, configure, support or troubleshoot applications, dashboards, reports or automations for the Customer, Exenai carries out that processing and the AI Client provider is an Exenai sub-processor, listed in the published sub-processor list. Such work is carried out under the Customer's instructions, within the Customer's configured permissions and policy controls, and is recorded in the Customer's audit log.
Removed: "directs"
Makes clear that you decide what your forms, profiles, adverts, apps and automations capture or display, and that we do not review that content.
Previous wording: Special categories of personal data. Exenai does not intentionally process special category data. Where the Customer configures the Services to record such data, the Customer is responsible for establishing a lawful basis and an Article 9 condition, and for applying appropriate safeguards. The Acceptable Use Policy prohibits using prompts, Agents or applications to infer, derive or surface special category data or protected characteristics.
New wording: Special categories of personal data. Exenai does not intentionally process special category data. The Customer decides which data its forms, field mappings, candidate profiles, job advertisements, Customer Artefacts and automations capture, hold or display, and Exenai does not review the content of those configurations. Where the Customer configures the Services to record or display such data, the Customer is responsible for establishing a lawful basis and an Article 9 condition, and for applying appropriate safeguards. The Acceptable Use Policy prohibits using prompts, Agents or applications to infer, derive or surface special category data or protected characteristics.
Confirms that returning your data to you, and passing it to the systems and AI tools you choose, is done on your instructions.
New wording, with added words in bold: A10.8 Customers outside the United Kingdom and the European Economic Area. Where the Customer is established outside the United Kingdom and the European Economic Area, including in the United States, its Customer Data may be hosted in the European Economic Area as described in A10.1. The Customer is responsible for any requirements of the law of its own country that apply to sending its data to those locations. Returning Customer Data to the Customer, and passing it to Connected Systems and AI Clients the Customer chooses, is carried out on the Customer's instructions and is not a transfer initiated by Exenai.
OpenAI and Google may now also be used as the AI tool Exenai operates through Connect, alongside Anthropic.
Previous wording: OpenAI. Large language model API for Exenai AI Features. Processing location: United States.
New wording: OpenAI. Large language model API for Exenai AI Features, and an AI Client Exenai may use through Exenai Connect, as described below. Processing location: United States.
Previous wording: Google LLC (Gemini API). Large language model API for Exenai AI Features. Processing location: United States, EU.
New wording: Google LLC (Gemini). Large language model API for Exenai AI Features, and an AI Client Exenai may use through Exenai Connect, as described below. Processing location: United States, EU.
Names the three providers we may use for our own AI tool, and commits that we use them only on business plans with model training disabled.
Previous wording: 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.
New wording: 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.
Lists our internal use of Claude for business tasks, including a trial of meeting notes for Google Meet, alongside our other business tools.
New wording: Anthropic (Claude for Work). 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.
Lists our use of Wispr Flow for dictation and meeting notes alongside our other business tools.
New wording: Wispr AI, Inc. (Wispr Flow). 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.
We no longer use ClickUp for meeting notes.
Previous wording: ClickUp. Project management, collaboration and meeting notes. Processing location: United States.
New wording: ClickUp. Project management and collaboration. Processing location: United States.
Questions about this document can go to privacy@exenai.com.