Contact us
← All legal documents

Legals

Privacy & Data Policy

How we collect, use, store, and protect personal data — covering our roles as both data controller and processor.

2026.8
December 16, 2026

Update notice. This version (2026.8) was published on 15 November 2026 and updated on 16 November 2026 to add Section 4.4 on meeting recording and transcription. Section 4.4 applies from 16 November 2026. The rest of this version takes effect on 16 December 2026, and until then version 2026.6 applies. See what is changing.

This Privacy & Data Policy ("Policy") sets out how Exenai Limited ("Exenai", "we", "our") collects, uses, stores, and protects personal data in the course of providing our services. It also includes our role as a data processor for our customers, and our compliance with the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018, and other applicable laws. This Policy forms part of the contractual agreement between Exenai and our customers and should be read in conjunction with the Master Services Agreement. The Data Processing Addendum referred to in the Master Services Agreement is set out in Annex 1 to this Policy.

1. Scope

This Policy applies to:

  • All personal data we collect from users, customers, or visitors through our website, applications, platforms, or in the course of our business activities;
  • Personal data processed on behalf of our customers as part of providing services including the Exenai Platform, Candidate Experience Platform, Exenai Connect (including the Connect App Host), and Automation-as-a-Service offerings.

This Policy applies to Exenai as both a data controller (when we collect personal data for our own purposes, e.g. website analytics, support contact) and a data processor (when we process personal data on behalf of our customers, e.g. candidate records, CRM data, or data transiting the Exenai Connect gateway).

2. Definitions

"Personal data" means any information that relates to an identified or identifiable individual. "Customer Data" means the data input, uploaded, or shared by our customers or their users, including Community Users (e.g. candidates and client representatives). "Services" refers to our software, platforms, APIs, applications, integrations, portals, support, and any associated professional or automation services provided to customers. "Community Users" means individuals who are authorised by our customers to access Exenai portals or interfaces, including candidates, clients, or other CRM-related users.

"AI Client" means a third-party AI application or model interface (e.g. Claude, ChatGPT, Microsoft Copilot) connected to send requests through Exenai Connect. An AI Client may be connected by a customer, in which case it is the customer's own tool and not part of our Services, or by Exenai, as described in Section 3.2. "Exenai AI Features" means AI functionality we provide within our Services using Model Providers, such as AI-generated summaries of candidate experience. "Model Providers" means the third-party large language model providers whose APIs we use to deliver Exenai AI Features, as listed in the Subprocessor List (Schedule A). "Usage Data" means logs, telemetry, and metadata generated by the use and operation of our Services, including audit log records and request metadata.

"Data Protection Law" means UK GDPR, the Data Protection Act 2018, and any applicable privacy regulations in the jurisdictions where we operate. "Processor", "Controller", "Data Subject", "Supervisory Authority" and other relevant terms shall have the meanings given in UK GDPR.

3. How We Process Personal Data

3.1 As a Data Controller

We collect and process personal data for our own legitimate business purposes, including: managing customer accounts and subscriptions; responding to support enquiries or demo requests; sending updates about our services and policies; monitoring website usage and improving user experience; 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); keeping accurate notes of meetings by recording and transcribing them (see Section 4.4); and maintaining system security and preventing fraud.

The legal bases for processing include: performance of a contract (e.g. user registration and account access); legitimate interests (e.g. business analytics, service improvement, keeping business contact records accurate, keeping records of notice acceptance, and recording and transcribing meetings); legal obligation (e.g. complying with regulatory or tax requirements); and consent, where required for marketing or cookies (see Section 10).

3.2 As a Data Processor

When our customers use our services, they may upload or input personal data (e.g. candidate records, CRM or ATS data) into the Exenai Platform. In such cases the customer acts as the controller and Exenai acts as the processor, processing such data strictly on the customer's written instructions.

We process Customer Data to:

  • Provide and operate the Exenai Platform, including Community User portals;
  • Support user access, permissions, and record updates;
  • Enable automation, analytics, and integrations with other systems;
  • Operate the Exenai Connect gateway, including evaluating requests against the customer's configured policy controls (allow-listing, interception, rate and cost caps, approvals) and maintaining audit log records of requests and actions;
  • Deliver Exenai AI Features (see Section 11);
  • Serve customer-created applications and dashboards on the Connect App Host with the customer's configured authentication and permissions;
  • Build, configure, support and troubleshoot applications, dashboards, reports and automations for the customer, including where we do so using an AI Client we operate;
  • Maintain backups, monitor performance, and ensure data integrity.

Where a customer connects its own AI Client through Exenai Connect, our processing is limited to the gateway itself: transporting the request, applying the customer's configured controls, and recording the audit log. Once data has passed through the gateway to the customer's AI Client, it is processed by that provider under the customer's own agreement with them; the customer is responsible for its arrangements with its AI Client providers.

Where Exenai connects its own AI Client through Exenai Connect in order to build, configure, support or troubleshoot for a customer, our processing is not limited to the gateway. In that case we carry out the processing and the AI Client provider is one of our subprocessors, listed in Schedule A. Most work of this kind is carried out by customers themselves using their own AI Client; we do it on request. 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. We maintain our AI Client subscriptions with model training disabled.

Where we act as a processor, we do not: access or use Customer Data for our own purposes; share Customer Data with third parties, except as necessary for service provision and under contractual safeguards; or retain Customer Data beyond the term of service (see Section 8: Retention).

4. Categories of Personal Data

4.1 Data We Collect as Controller

  • Contact details: name, job title, company, email address, phone number
  • Account information: usernames, access logs, support tickets
  • Notice acceptance records: the user's identity, the date and time, the version of the User Notice accepted, where it was accepted (sign-in or AI agent connection), and the IP address and browser used
  • Marketing preferences and communication history
  • Meeting recordings, transcripts and notes: what participants say in meetings we record, and their names as shown in the meeting (see Section 4.4)
  • Website usage data (e.g. IP address, browser, device type, location data)
  • Financial and billing details (e.g. invoicing contact, bank/payment information)

4.2 Data Processed on Behalf of Customers (as Processor)

  • Candidate data: CV/resume, contact details, work history, interview notes
  • Client contact data: names, emails, communication history, job order details
  • CRM data: status, tags, notes, compliance documentation, and interaction logs
  • Community User portal activity: login timestamps, form submissions, data updates
  • Exenai Connect gateway data: prompts and responses in transit, request metadata, and audit log records (user or agent identity, action, timestamp, outcome)
  • Optional integrations: LinkedIn data, job board interactions, or third-party service data (as configured by the customer)

We do not intentionally collect or process special categories of personal data (e.g. health, political views, biometric data) unless explicitly instructed by the customer and subject to appropriate safeguards under the customer's responsibility.

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.

4.4 Meeting Recording and Transcription

We may record and transcribe online meetings that Exenai people hold or attend, including meetings with customers, prospective customers, partners and suppliers, so that we keep accurate notes and can follow up properly. We do this as a controller.

Tools we use. We use Wispr Notetaker, part of Wispr Flow, supplied by Wispr AI, Inc., which joins the meetings in our people's Google Calendars. It is listed in our Subprocessor List.

What you are told. When Wispr Notetaker joins a meeting, it posts a message saying that the meeting is being transcribed, with a link to this Policy.

What is captured. The audio of the meeting, which is turned into a transcript and notes. These include what participants say and their names as shown in the meeting. We do not record candidate interviews, and we ask our people not to record conversations about health, finances or other sensitive matters.

Who can see it. Transcripts and notes are available only to Exenai staff. The tools do not share them outside Exenai. Decisions and actions from a meeting may be copied into our customer relationship management and project tools.

AI training. Model training is switched off for our account, so recordings, transcripts and notes are not used to train Wispr's AI models.

Lawful basis. We rely on our legitimate interests in keeping an accurate record of what was discussed and agreed, so that we can follow up and deliver what we have committed to. We tell everyone at the start of the meeting, and we turn recording off if anyone objects.

Where it is processed. In the United States. Wispr may use its own service providers in other locations for some transcription. These transfers are covered by the EU Standard Contractual Clauses (Module 2) with the UK Addendum, in Wispr's data processing agreement. See also Section 7.

How long we keep it. Wispr deletes the audio of a meeting within 7 days. Transcripts and notes are deleted when we delete the meeting from Wispr Flow, which we do every six months. Decisions and actions from a meeting may be kept longer in our customer relationship management and project tools. You can ask us to delete the transcript or notes of any meeting you took part in sooner, as set out below.

Your choices. You can ask us to turn the notetaker off before or during any meeting, and we will. You can also ask us to delete the recording, transcript or notes of a meeting you took part in, or use any of your other rights in Section 9, by telling the Exenai person you met or emailing privacy@exenai.com.

5. Data Sharing and Subprocessors

We do not sell personal data. However, we may share personal data with third parties as follows:

5.1 Subprocessors and Service Providers

We use trusted third-party providers (subprocessors) to help us deliver and support our services. These include providers of: hosting infrastructure (e.g. Hetzner, Microsoft Azure); platform software licensed to us and operated by us (e.g. Tocalabs); large language model APIs used to deliver Exenai AI Features, and the AI Client we operate through Exenai Connect (our Model Providers — see below); communication, email and messaging platforms; analytics, monitoring, and security tools; identity and access management systems; and integrations, plug-ins, and automation services.

Model Providers. Exenai AI Features are delivered using large language model APIs drawn from a pool of providers currently comprising OpenAI, Google (Gemini API), and Anthropic (Claude API). We select, combine, and may change the Model Provider used for any given feature at our discretion and do not publish a per-feature mapping. Customer data processed by Model Providers is not used to train any public models; processing is limited to instance-based API processing to deliver the relevant feature. The same applies to the AI Client we operate through Exenai Connect.

For clarity: a customer's own AI Client (e.g. its Claude, ChatGPT, or Copilot subscription connected through Exenai Connect) is not an Exenai subprocessor. The customer's agreement with its AI Client provider governs that processing. An AI Client operated by Exenai is a different case and is treated as a subprocessor, as described in Section 3.2.

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, with backups held within the United Kingdom or the European Economic Area. Automation as a Service environments are hosted on Hetzner in Germany for customers in the United Kingdom, the European Economic Area and any country other than the United States, and on Hetzner in Ashburn, Virginia for customers established in the United States, unless otherwise agreed. A customer's environment is not moved between regions without agreement. Full details are in Section A10 of Annex 1 and in Schedule A.

Each subprocessor is contractually bound to only process data in accordance with Exenai's written instructions, and subject to appropriate confidentiality, security, and data protection obligations. A current list of subprocessors is provided in Schedule A to this Privacy & Data Policy and is also available upon request. We will provide notice of changes to our subprocessors (including changes within the Model Provider pool) in accordance with our agreements with customers, and customers may object on reasonable data protection grounds in accordance with the Master Services Agreement and Section A5.5 of Annex 1.

5.2 Legal and Regulatory Disclosures

We may disclose personal data to courts, regulators, law enforcement, or other authorities: when required by applicable law or regulation; to comply with legal process or respond to valid requests; or to enforce our legal rights or investigate potential violations of our terms.

5.3 Business Transfers

If we are involved in a merger, acquisition, restructuring or sale of assets, personal data may be transferred as part of that transaction, subject to confidentiality and continued protection under this Policy.

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.

6. Security Measures

We are committed to protecting the confidentiality, integrity and availability of personal data. Our first principle is minimisation: our customers' data lives in their own systems of record, and we hold only what the Services need, for as long as they need it. We implement appropriate technical and organisational measures, including: encryption of all data in transit, and at rest in Exenai Connect and the Candidate Experience Platform; individual, role-based access with single sign-on; access to the automation platform's build and administration environment only through a secured VPN; segregation of each customer's data and workflows; CrowdStrike Falcon endpoint protection on our servers and devices; regular automated backups; secure, certified data centres; and staff training and internal access governance.

Access to personal data is limited to authorised personnel and subprocessors with a legitimate operational need, and is logged. Where required under applicable law, we will notify customers of any personal data breach without undue delay, and in accordance with Section A7 of Annex 1. A fuller description of these measures is set out in Appendix 2 to Annex 1.

7. International Data Transfers

We may process and store personal data outside of the country in which it was collected, including outside the UK or European Economic Area (EEA), particularly when using trusted hosting providers or subprocessors. In particular, personal data may be transferred to the United States in the cases set out in Section A10.3 of Annex 1: to Model Providers and the AI Client we operate, to our messaging provider, where a US customer's Automation as a Service environment is hosted there, and where customer data is held incidentally in our business tools. 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. Meeting recordings, transcripts and notes are processed in the United States by Wispr AI, Inc., as described in Section 4.4. Customer environments themselves are provisioned by region, as described in Section 5.1 and Section A10 of Annex 1.

Whenever we transfer personal data internationally, we ensure that appropriate safeguards are in place in compliance with Data Protection Law, such as: transfers to countries deemed to have adequate protection by the UK government or European Commission; use of Standard Contractual Clauses (SCCs) approved by the UK ICO or EU Commission, or the UK International Data Transfer Agreement or Addendum, or the Swiss addendum to the EU SCCs where Swiss law applies; reliance on the UK–US Data Bridge / EU–US Data Privacy Framework where the recipient is certified; and additional contractual, technical, or organisational measures as necessary. Where we rely on the Data Privacy Framework, Standard Contractual Clauses are also in place as a fallback, as described in Section A10.4 of Annex 1. Details of specific international transfers and the safeguards applied can be requested via Section 12.

8. Data Retention

8.1 Data We Control

Data collected by Exenai as a controller (e.g. contact, account, billing, or support data) is retained: for the duration of the customer relationship; for up to 7 years thereafter, where required for legal, regulatory, or contractual reasons; or until a valid request for erasure is received, subject to our legal obligations. Meeting recordings, transcripts and notes are kept as set out in Section 4.4.

Records of acceptance of our User Notice are kept for as long as the user has access to the relevant service, and for six years after that access ends, so that we can show which terms applied at the time. They are not deleted on a request for erasure while they are needed to establish or defend legal claims.

8.2 Customer Data (Processed on Behalf of Customers)

Where we act as a processor, the Customer's data lives in its own systems of record, such as Bullhorn or Invenias. We hold Customer Data only where the Services need it, and only for as long as they need it, using the periods below. In no case do we keep it beyond the end of the agreement, except for up to 60 days after termination so that the customer can export its data, unless otherwise agreed. At the end of that window, Customer Data, including audit log records and customer-created application definitions, is securely deleted from our live systems.

These are our current retention standards. We are rolling out automated deletion to these periods across the Services, and will update this Section as each is completed.

Candidate Experience Platform

  • Completed onboarding, applications and uploads (profile uploads, job applications, documents and onboarding answers): deleted within 72 hours of being handed off to the customer's system of record.
  • Incomplete onboarding: deleted after 30 days. The candidate then starts again.
  • Candidate profile cache: deleted after 72 hours.
  • Candidate activity records (for example sign-ins and document downloads, holding the candidate's email, ID and action): kept in full for 120 days, then reduced to aggregated records.

Exenai Connect

  • Connect audit log (requests and actions through the gateway, including prompts and responses): kept in full for 120 days, then reduced to aggregated records of activity.
  • Connected system request logs (requests to systems such as Bullhorn and Invenias): kept for 30 days.

Data deleted on the customer's instruction is removed from our live systems when the instruction is carried out, subject to the backup periods below.

Backups. For Exenai Connect and the Candidate Experience Platform, point-in-time backups cover the previous five weeks. Immutable copies, which cannot be altered or deleted before they expire, are kept weekly for three months and monthly for twelve months. Deleted files can be recovered for two weeks. Automation as a Service server backups are kept for one week, under a delete lock. Data deleted from Exenai Connect or the Candidate Experience Platform can therefore remain in backups for up to twelve months. Backups are used only to recover from a loss of data and are not accessed for any other purpose. If data must be restored from a backup, we take reasonable steps to ensure that data deleted since the backup was taken is not returned to use.

9. Data Subject Rights

We respect the rights of individuals over their personal data. Where we act as a controller, individuals may exercise the following rights under UK GDPR: access; rectification — to correct inaccurate or incomplete data, including AI-generated content about them such as candidate experience summaries (see Section 11); erasure; restriction; objection; and portability.

Requests may be submitted to privacy@exenai.com or using our contact details in Section 12. We will respond within the timeframes required by applicable law. Where we act as a processor, data subjects should direct their requests to the relevant customer (the data controller). Exenai will support its customers in responding to such requests as required under our agreement and applicable law, and as set out in Section A6 of Annex 1.

10. Cookies and Website Tracking

We use cookies and similar tracking technologies on our websites and applications to improve user experience, analyse site traffic, and deliver relevant marketing. We use: essential cookies (core website functionality); analytics cookies (Google Analytics on our website); functionality cookies (saved preferences); and marketing cookies (targeted advertising, including through our CRM and marketing platform). In our applications we measure usage with Plausible, which is cookieless and does not store raw IP addresses or generate persistent identifiers. Where required by law, we seek user consent before placing non-essential cookies. Users can manage or withdraw consent at any time using our cookie consent tool or browser settings. We honour Do Not Track signals where technically feasible. More detailed information is available in our Cookie Policy.

11. AI Usage and Automated Processing

Some of our Services include features powered by artificial intelligence (AI), and our Exenai Connect product provides a governed gateway through which customers connect their own AI tools to their systems. This section explains both.

11.1 Exenai AI Features (AI we provide)

Exenai AI Features are AI capabilities we build into our Services — for example, AI-generated summaries of a candidate's experience within the Candidate Experience Platform. These features are delivered using our Model Providers (see Section 5.1). Our commitments:

  • Customer data is not used to train any public models. Processing by Model Providers is limited to instance-based API processing to deliver the feature;
  • AI-generated content (including candidate summaries) is produced by statistical inference and may contain errors or omissions. It is an aid to human assessment, not a substitute for it;
  • Customers are responsible for reviewing and validating AI-generated content before using it in any hiring, outreach, or business decision;
  • Where an individual (such as a candidate) believes AI-generated content about them is inaccurate, it can be corrected or regenerated — individuals should contact the customer (controller) who manages their data, or us at privacy@exenai.com where we are the controller;
  • Any training, tuning or fine-tuning of Exenai's own models is limited to anonymised and aggregated data where legally permissible.

11.2 Exenai Connect (AI tools our customers bring)

Where a customer connects its own AI Client through Exenai Connect, we operate the governed gateway: enforcing the customer's configured controls and recording audit logs. The AI Client itself is the customer's tool, governed by the customer's own agreement with that provider. Exenai Connect is designed to support responsible AI use, including policy controls that can block bulk data extraction, require human approval for consequential actions, and prevent AI-driven automated decision-making about individuals.

11.3 AI Clients we operate

Where we connect our own AI Client through Exenai Connect to build, configure, support or troubleshoot for a customer, the commitments in Section 11.1 apply equally, the AI Client provider is a subprocessor, and the work is confined to what is necessary for the task and recorded in the customer's audit log. See Section 3.2 and Section A11.7 of Annex 1.

11.4 Automated Decision-Making

Customers must not use Exenai's Services to make solely automated decisions that produce legal or similarly significant effects on individuals unless compliant with Articles 22A to 22D of the UK GDPR (as amended by the Data (Use and Access) Act 2025), Article 22 of the EU GDPR, or equivalent laws. Our Services are designed on the principle that AI outputs inform human decisions — in recruitment contexts, a human decides. Customers remain responsible for their use of AI features and AI Clients within our platform and must ensure that such use complies with applicable laws (including the EU AI Act where applicable), ethics, and fairness obligations.

12. Contact and Complaints

If you have any questions about this Privacy & Data Policy, or if you would like to make a request or raise a concern about how your data is being handled, you can contact us at: Email: privacy@exenai.com · Post: Data Protection Officer, Exenai Limited, 167–169 Great Portland Street, London, W1W 5PF, United Kingdom.

We aim to respond to all requests within the timeframes required by law. If you are not satisfied with our response or believe that your data has not been processed in accordance with applicable data protection laws, you have the right to lodge a complaint with the Information Commissioner's Office (ICO) in the UK or your local supervisory authority.

Annex 1: Data Processing Addendum

A1. Status and scope

A1.1 This Annex is the Data Processing Addendum ("DPA") referred to in the Exenai Master Services Agreement. It forms part of this Privacy & Data Policy and, through it, part of the agreement between Exenai Limited ("Exenai") and the customer ("Customer").

A1.2 This DPA applies where Exenai processes personal data on behalf of the Customer in the course of providing the Services. In that processing the Customer is the controller and Exenai is the processor. Where Exenai processes personal data for its own purposes, as described in Section 3.1, Exenai is the controller and this DPA does not apply.

A1.3 This DPA is written to meet the requirements of Article 28 of the UK GDPR and the EU GDPR, the Data Protection Act 2018, the Swiss Federal Act on Data Protection (FADP), and the California Consumer Privacy Act as amended by the California Privacy Rights Act and other US state privacy laws, as set out in A13, in each case to the extent applicable to the processing.

A1.4 Where this DPA conflicts with the body of this Policy, this DPA prevails in respect of processing carried out by Exenai as processor. Where it conflicts with the Master Services Agreement, the Master Services Agreement prevails except on matters of data protection, where this DPA prevails.

A1.5 No separate signature is required. This DPA takes effect on the effective date of the Customer's Order Form and continues for as long as Exenai processes personal data on the Customer's behalf. Exenai will provide a separately executed copy on request.

A2. Processing on documented instructions

A2.1 Exenai processes personal data only on the Customer's documented instructions, including in relation to transfers to a third country, unless required to do otherwise by law to which Exenai is subject. Where such a legal requirement applies, Exenai will inform the Customer before processing unless the law prohibits it on important grounds of public interest.

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.

A2.3 Exenai will immediately inform the Customer if, in its opinion, an instruction infringes Data Protection Law.

A2.4 The subject matter, duration, nature and purpose of the processing, the types of personal data, and the categories of data subjects are set out in Appendix 1.

A3. Confidentiality

A3.1 Exenai ensures that persons authorised to process personal data are bound by confidentiality obligations, whether contractual or statutory, and are subject to appropriate training and access governance.

A3.2 Access to personal data is limited to personnel with a legitimate operational need, and access is logged, as described in Section 6.

A4. Security

A4.1 Exenai implements and maintains appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking account of the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing.

A4.2 Those measures are described in Section 6 and set out in Appendix 2.

A4.3 Exenai regularly tests, assesses and evaluates the effectiveness of those measures. Exenai may change specific measures provided the overall level of security is not reduced.

A5. Sub-processors

A5.1 The Customer grants Exenai general written authorisation to engage sub-processors to process personal data on the Customer's behalf, subject to this Section A5.

A5.2 The current list of sub-processors is published at exenai.com/legal/subprocessor-list and forms Schedule A to this Policy.

A5.3 Exenai imposes on each sub-processor data protection obligations no less protective than those in this DPA, and remains fully liable to the Customer for the performance of each sub-processor's obligations.

A5.4 Exenai will give the Customer at least 30 days' notice before adding or replacing a sub-processor. Notice is given by updating the published sub-processor list and notifying the Customer's registered contact.

A5.5 The Customer may object to a proposed change on reasonable data protection grounds within that 30 day period. Exenai and the Customer will discuss the objection in good faith. If it cannot be resolved, and Exenai is unable to provide the affected Service without the sub-processor, the Customer may terminate the affected Service on written notice without penalty, with a pro rata refund of any prepaid fees for the unused period.

A5.6 A Customer's own AI Client connected through Exenai Connect is not an Exenai sub-processor. Processing by that provider is governed by the Customer's own agreement with it.

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.

A6. Assisting the Customer

A6.1 Data subject rights. Taking account of the nature of the processing, Exenai will assist the Customer by appropriate technical and organisational measures, insofar as possible, in fulfilling the Customer's obligation to respond to requests to exercise data subject rights. Where Exenai receives such a request directly, it will not respond to it other than to acknowledge receipt, and will inform the Customer without undue delay.

A6.2 Wider obligations. Exenai will assist the Customer in ensuring compliance with its obligations under Articles 32 to 36 of the UK GDPR, taking into account the nature of the processing and the information available to Exenai. This includes reasonable assistance with data protection impact assessments and prior consultation with a supervisory authority.

A7. Personal data breach

A7.1 Exenai will notify the Customer without undue delay, and in any event within 48 hours of becoming aware, of a personal data breach affecting personal data processed on the Customer's behalf. For these purposes Exenai becomes aware when a member of its personnel has a reasonable degree of certainty that a security incident has occurred that led to personal data being compromised. Initial detection of an anomaly, alert or suspected incident does not by itself constitute awareness, and Exenai may take a short and reasonable period to establish whether a breach has in fact occurred.

A7.2 The notification will describe, to the extent known at the time and updated as further information becomes available: the nature of the breach, including where possible the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed to address it and to mitigate its effects; and a contact point for further information.

A7.3 Exenai will take reasonable steps to investigate and mitigate the breach, and will cooperate with the Customer in the Customer's own notification obligations to supervisory authorities and data subjects.

A7.4 Notification under this Section is not an acknowledgement of fault or liability.

A8. Return or deletion

A8.1 On termination or expiry of the agreement, Exenai will, at the Customer's choice, return the personal data to the Customer or securely delete it, and delete existing copies, unless retention is required by law.

A8.2 The Customer has 60 days from termination to export data and to make its choice, as described in Section 8.2. If the Customer has made no election by the end of that period, Exenai will securely delete the data.

A8.3 Data held in backups is deleted on the ordinary backup expiry cycle described in Section 8.2. Until then it remains protected by the measures in Appendix 2 and is not accessed for any purpose other than recovery from a loss of data.

A9. Audit and information

A9.1 Exenai will make available to the Customer all information reasonably necessary to demonstrate compliance with this DPA.

A9.2 In the first instance Exenai will satisfy a request under A9.1 by providing its current security documentation and responses to reasonable security questionnaires, subject to confidentiality obligations.

A9.3 Where that documentation is not sufficient to demonstrate compliance, the Customer may, on at least 30 days' written notice and no more than once in any 12 month period, conduct an audit of Exenai's processing. The Customer may appoint an independent third-party auditor, who must not be a competitor of Exenai and must be bound by confidentiality.

A9.4 Audits take place during business hours, must not unreasonably disrupt Exenai's operations, and are limited to systems and records relevant to the processing of the Customer's personal data. Exenai will not be required to disclose information relating to other customers or information subject to legal privilege.

A9.5 The Customer bears its own costs and Exenai's reasonable costs of an audit under A9.3, except where the audit reveals a material breach of this DPA, in which case Exenai bears its own costs.

A9.6 The frequency limit in A9.3 does not apply where an audit is required by a supervisory authority or follows a confirmed personal data breach affecting the Customer's personal data.

A10. Hosting locations and international transfers

A10.1 Hosting. 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, with backups held within the United Kingdom or the European Economic Area in a location Exenai selects. Automation as a Service environments are hosted on Hetzner in Germany for a Customer established in the United Kingdom, the European Economic Area or any country other than the United States, and on Hetzner in Ashburn, Virginia, United States, for a Customer established in the United States, unless otherwise agreed in the Order Form. Their backups are held in the same region as the environment or within the United Kingdom or the European Economic Area. Personal data is not moved to another region without the Customer's agreement.

A10.2 Exenai in the United Kingdom. Exenai is established in the United Kingdom. Transfers of personal data from the European Economic Area to Exenai rely on the European Commission's adequacy decision for the United Kingdom. Transfers from the United Kingdom to the European Economic Area rely on the United Kingdom's adequacy regulations for the European Economic Area.

A10.3 Transfers that arise in practice. Subject to A10.9, personal data subject to UK or EU Data Protection Law is transferred by Exenai outside the United Kingdom and the European Economic Area in the following cases: (a) to Model Providers, and to the provider of the AI Client Exenai operates under A5.7, in the United States; (b) to Exenai's messaging provider for outbound email, notifications and one-time passcodes, in the United States; (c) where Automation as a Service is hosted in the United States for a Customer established there; and (d) where customer personal data is held incidentally in the business tools listed in Section 2 of Schedule A, some of which process data in the United States.

A10.4 Safeguards. Exenai will not make a transfer under A10.3 unless an appropriate safeguard under Data Protection Law is in place. For transfers under A10.3(a), (b) and (d): where the recipient is certified to the EU-US Data Privacy Framework (and, for UK personal data, the UK Extension, and for Swiss personal data, the Swiss-US Data Privacy Framework), Exenai may rely on that certification; and in every case Standard Contractual Clauses (Module Two or Module Three, as applicable), together with the UK Addendum and the Swiss addendum, are also in place, either directly or through the recipient's data processing terms, so that a valid safeguard remains if a Data Privacy Framework adequacy finding ceases to apply. For transfers under A10.3(c), the environment is provided by Hetzner Online GmbH through its United States subsidiary under Hetzner's data processing terms, and the Customer, as controller, decides what personal data its United States environment holds. Other safeguards that may be relied on are a UK adequacy regulation or EU adequacy decision for the destination country and the UK International Data Transfer Agreement.

A10.5 Transfer assessments. Exenai will provide the Customer with reasonable information about the transfers in A10.3 and their safeguards to support the Customer's own transfer risk assessment, as part of its obligations under A9.

A10.6 The Customer authorises Exenai to enter into the transfer mechanisms in A10.4 with sub-processors on the Customer's behalf.

A10.7 Where the Customer requires them, Exenai will enter into the Standard Contractual Clauses directly with the Customer. In that case Module Two (controller to processor) applies, the governing law and forum are those of England and Wales for UK transfers and of Ireland for EU transfers, the optional docking clause applies, and the appendices are completed by Appendix 1 and Appendix 2 of this DPA.

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.

A10.9 Connected systems and the Customer's AI Clients. Exenai Connect provides pass-through access between the Customer's connected systems, such as Bullhorn or Invenias, and the Customer's own AI Clients. Connected systems may be hosted anywhere in the world under the Customer's own agreements with their providers, and the Customer chooses which AI Client, and which plan or package of that AI Client, it connects. The location of those systems and AI Clients, and any transfer of personal data between them and the Exenai Connect gateway, are determined by the Customer and its providers, and the Customer is responsible for the safeguards those transfers require. The transfers for which Exenai is responsible are those in A10.3.

A11. Artificial intelligence

A11.1 No training on Customer personal data. Exenai does not use personal data processed on the Customer's behalf to train, tune or fine-tune any model, and its Model Providers do not use it to train any public model. This applies equally where personal data is processed through an AI Client operated by Exenai under A5.7, and Exenai maintains its AI Client subscriptions with model training disabled. Processing by Model Providers is limited to instance-based API processing to deliver the relevant feature. Training of Exenai's own models uses only anonymised and aggregated data where legally permissible.

A11.2 No solely automated decisions. Exenai AI Features are designed to inform human assessment. Exenai does not make, and its Services are not designed to make, decisions producing legal or similarly significant effects on individuals without human involvement. The Customer is responsible for ensuring meaningful human review, as set out in Section 11.4.

A11.3 Purpose limitation. Exenai uses AI models only for the purposes identified in this Policy and the Master Services Agreement. Any materially new use of AI affecting the Customer's personal data requires prior notice to the Customer.

A11.4 Explainability. Exenai will provide reasonable assistance to the Customer in explaining to a data subject the logic and outputs of Exenai AI Features applied to that data subject's personal data.

A11.5 Accuracy. Where AI-generated content about an individual is inaccurate, it can be corrected or regenerated, as described in Section 11.1.

A11.6 Gateway processing. Where the Customer connects its own AI Client through Exenai Connect, Exenai's processing is limited to transporting the request, applying the Customer's configured controls, and recording the audit log, as described in Section 3.2.

A11.7 Exenai's own use of an AI Client. Where Exenai connects its own AI Client to build, configure, support or troubleshoot for the Customer, as described in A5.7, Exenai's processing is not limited to the gateway. Because Exenai Connect provides a live view of the Customer's 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, remains subject to the Customer's configured permissions and policy controls, is recorded in the Customer's audit log, and is subject to the commitments in A11.1 to A11.5.

A12. Liability and term

A12.1 Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Master Services Agreement.

A12.2 This DPA takes effect on the effective date of the Order Form and terminates automatically when Exenai ceases to process personal data on the Customer's behalf, save that Sections A8 and A9 survive termination.

A12.3 This DPA is governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction, without prejudice to any mandatory jurisdiction under Data Protection Law or to A10.7.

A13. US state privacy laws

A13.1 This Section applies where Exenai processes personal data on the Customer's behalf that is subject to the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA") or another US state consumer privacy law (together, "US State Privacy Laws"). For those purposes Exenai is a "service provider", "contractor" or "processor", as the relevant law defines those terms, and the Customer is the "business" or "controller".

A13.2 Exenai processes such personal data only for the limited and specified business purposes of providing the Services described in the Agreement, the Order Form and Appendix 1.

A13.3 Exenai will not: (a) sell or share the personal data, as "sell" and "share" are defined in the CCPA; (b) retain, use or disclose it for any purpose, including any commercial purpose, other than the business purposes in A13.2 or as otherwise permitted by US State Privacy Laws; (c) retain, use or disclose it outside the direct business relationship between Exenai and the Customer; or (d) combine it with personal data Exenai receives from or on behalf of another person, or collects from its own interactions with individuals, except as US State Privacy Laws permit.

A13.4 Exenai will comply with its obligations under US State Privacy Laws and will provide the same level of privacy protection as US State Privacy Laws require of the Customer. Exenai will notify the Customer if it determines that it can no longer meet those obligations.

A13.5 The Customer may take reasonable and appropriate steps to ensure that Exenai uses the personal data in a manner consistent with the Customer's obligations under US State Privacy Laws and, on notice to Exenai, to stop and remediate any unauthorised use, including through the rights in A9.

A13.6 Exenai binds its sub-processors to written terms no less protective than this Section. The confidentiality, assistance, breach notification, and return and deletion provisions of this DPA apply equally to personal data subject to US State Privacy Laws.

A13.7 Where Exenai uses anonymised or aggregated data as permitted by A11.1 and the Agreement, that data is deidentified within the meaning of US State Privacy Laws. Exenai will maintain it in deidentified form, will not attempt to reidentify it, and will require any recipient of it to do the same.

A13.8 Exenai certifies that it understands the restrictions in this Section and will comply with them.

Appendix 1: Details of the Processing

Controller. The Customer identified in the Order Form.

Processor. Exenai Limited, 167–169 Great Portland Street, London, W1W 5PF, United Kingdom. Registered in England and Wales, company number 14571809.

Subject matter. Provision of the Services described in the Order Form, comprising the Exenai Platform, the Candidate Experience Platform, Exenai Connect including the Connect App Host, and Automation as a Service.

Duration. For the term of the agreement, plus the retention window in Section 8.2.

Frequency. Continuous, for the duration of the agreement.

Nature and purpose of the processing.

  • Hosting, storage, backup and transmission of Customer Data
  • Creating, reading, updating and synchronising records in the Customer's connected ATS, CRM and other systems
  • Parsing CVs and application materials and mapping the extracted data onto the Customer's taxonomies
  • Generating AI summaries of candidate experience where the Customer uses that feature
  • Operating the Exenai Connect gateway: evaluating requests against the Customer's configured policy controls, transporting requests and responses, and recording audit log entries
  • Serving customer-created applications and dashboards on the Connect App Host under the Customer's configured authentication and permissions
  • Building, configuring, supporting and troubleshooting applications, dashboards, reports and automations for the Customer, including where Exenai does so using its own AI Client connected through Exenai Connect
  • Operating automations configured for the Customer, including scheduled and event-driven processing
  • Providing Community User portals, including candidate and client interfaces
  • Support, monitoring, performance management and data integrity

Categories of data subjects.

  • Candidates and applicants of the Customer
  • Client and prospect contacts of the Customer
  • The Customer's own personnel and authorised users
  • Community Users authorised by the Customer, including candidates and client representatives
  • Referees, emergency contacts and other third parties whose data the Customer records

Types of personal data. As set out in Section 4.2, comprising in particular:

  • Identity and contact data: name, email address, telephone number, postal address, LinkedIn or other profile URL
  • Candidate data: CV or resume content, work history, education, qualifications, certifications, skills, languages, salary and availability, interview notes
  • Where the Customer records them: date of birth, nationality and sex
  • Client contact data: name, role, employer, communication history, job order details
  • CRM and workflow data: status, tags, notes, compliance documentation, interaction logs
  • Portal activity: login timestamps, form submissions, record updates
  • Exenai Connect gateway data: prompts and responses in transit, request metadata, and audit log records comprising user or agent identity, action, timestamp and outcome
  • AI-generated content about a data subject, including candidate experience summaries

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.

Criminal offence data. Processed only where the Customer records it as part of its own compliance or vetting processes, on the same basis as the paragraph above.

Appendix 2: Technical and Organisational Measures

Measures in force as at the effective date of this Policy. Exenai may vary specific measures provided the overall level of security is not reduced.

Data minimisation. The Services are designed so that Customer Data remains in the Customer's own systems of record. Exenai holds personal data only where the Services require it, for example in audit logs, automation run logs, reports and API request logs, and only for as long as the Services need it, within the periods set out in Section 8.2.

Encryption. All data is encrypted in transit using TLS. In Exenai Connect and the Candidate Experience Platform, data is also encrypted at rest on Microsoft Azure, using keys managed by the hosting provider and kept separately from the data.

Hosting provider security. The automation platform is hosted by Hetzner, which holds ISO/IEC 27001:2022 certification and BSI C5 Type 2 certification for its cloud services. Hetzner's data centres have logged access control, perimeter fencing and video monitoring, and storage is securely erased or physically destroyed at the end of its life. Microsoft Azure holds ISO/IEC 27001, ISO/IEC 27018 and SOC 1, 2 and 3 certifications.

Access control. Exenai's business systems, Exenai Connect and the Candidate Experience Platform use individual named accounts through Microsoft or Google single sign-on, with role-based access and least privilege. The automation platform's build and administration environment can only be reached through a secured VPN, with an individual VPN account for each member of staff, covering both the European and the United States data centres. Only the production app host, which serves the applications published for customers and their users, is accessible outside the VPN. Within the platform, each customer's environment is accessed through a customer-specific login, which keeps that customer's data and automations separate. Its credentials are held in Passbolt, an encrypted password vault for which Exenai holds the encryption keys; they are released only to staff working on that customer, rotated, and removed when staff change. Access is reviewed periodically and removed promptly when someone changes role or leaves. Customers can configure role-based permissions within the Services.

Segregation. Exenai Connect and the Candidate Experience Platform are multi-tenant services on Microsoft Azure, in which each customer's data is logically separated behind Exenai's authentication. In Automation as a Service, each customer has its own dedicated environment login on the automation platform, holding that customer's workflows, data stores, connectors and applications. Production is separated from development and test. Personal data and Customer Data are not used to develop or test Exenai's products. Automations are built and tested within the Customer's own environment, using designated test records, until the Customer signs them off.

Resilience and availability. Automated backups are taken regularly for the Azure databases and services, including immutable copies that cannot be altered or deleted before they expire, and for the automation platform, where server backups are held under a delete lock. Backups are held in protected storage with restricted access and can be restored, on the cycle set out in Section 8.2. Availability is monitored, with alerting.

Endpoint protection and maintenance. CrowdStrike Falcon endpoint protection runs on all Exenai servers and on every staff device. Infrastructure and dependencies are kept up to date with security patches. Exenai Connect and the Candidate Experience Platform run on Microsoft Azure managed services, which Microsoft maintains and patches.

Logging and monitoring. Exenai Connect keeps a full, queryable audit log of every request and action through the gateway, which the Customer can inspect. The automation platform keeps its own run logs and reports, with alerting on failures. VPN access is logged for each user.

Governance. Staff are bound by confidentiality obligations and receive data protection training. A documented incident response procedure is in place. Sub-processors go through due diligence and are bound by contractual data protection terms. All hosting is in certified data centres.

Deletion. A documented secure deletion procedure applies to live systems. Backups expire on the cycle in Section 8.2, and deletion follows the timescales in Section 8.

Schedule A: Sub-processors

Schedule A is the sub-processor list published at exenai.com/legal/subprocessor-list. It is not reproduced here, so that there is one list to maintain rather than two. Changes to it are notified under Section A5.4 and may be objected to under Section A5.5.

Questions about this document can go to privacy@exenai.com.