This Data Processing Addendum ("DPA") forms part of the AnswerVault Terms of Service. It applies whenever Catapult processes personal data on your behalf in providing AnswerVault.
No signature is needed. This DPA is incorporated into the Terms of Service and takes effect when you accept them. It is in writing, including in electronic form, as UK GDPR Article 28(9) requires. If your organisation needs a countersigned copy, email dpo@catapultcx.co.uk.
Parties
- Controller: the Customer, as defined in the Terms of Service.
- Processor: Catapult CX Limited, a company registered in England and Wales (Company No: 11381539). Data Protection Officer: Craig Cook, CEO, dpo@catapultcx.co.uk.
- Effective date: the date the Customer accepts the Terms of Service.
- Service: AnswerVault, an AI-powered document query service.
1. Definitions
In this DPA:
- "UK GDPR" means the UK General Data Protection Regulation, as it forms part of the law of England and Wales, Scotland and Northern Ireland by virtue of section 3 of the European Union (Withdrawal) Act 2018.
- "Controller", "Processor", "Personal Data" and "Processing" have the meanings given in UK GDPR Article 4.
- "Sub-processor" means any third party engaged by the Processor to carry out processing activities on behalf of the Controller.
- "Services" means the AnswerVault service provided under the Terms of Service.
- "Security Incident" means any confirmed or reasonably suspected unauthorised access to, disclosure of, loss of, or destruction of Personal Data processed under this DPA.
2. Subject matter, duration and nature of processing
2.1 Subject matter
The Processor processes Personal Data on behalf of the Controller solely in connection with providing the Services, as described in Schedule 1.
2.2 Duration
Processing continues for the term of the Terms of Service, until the Controller instructs the Processor in writing to stop, or until the data is deleted under clause 4.7, whichever is earliest.
2.3 Nature and purpose
The Processor processes Personal Data only to provide AnswerVault to the Controller, including document ingestion, vector embedding, retrieval, AI-generated responses and the associated logging described in Schedule 1.
3. Controller obligations
The Controller warrants and undertakes that it:
- has and will maintain a valid lawful basis under UK GDPR Article 6 (and Article 9 where applicable) for all Personal Data it causes to be processed under this DPA;
- has given all required privacy notices to data subjects whose Personal Data is in documents connected to AnswerVault;
- will not connect document sources containing special category data (UK GDPR Article 9) or criminal offence data (Article 10) unless it has an applicable legal basis and has told the Processor in advance;
- will carry out its own Data Protection Impact Assessment before deploying AnswerVault where processing is likely to result in high risk to data subjects, including sensitive-population or regulated-sector deployments;
- will configure AnswerVault's data scope (connected sources and folders) in line with data minimisation, connecting only the sources its use case needs;
- will meet its own obligations under the Freedom of Information Act 2000 (or the Freedom of Information (Scotland) Act 2002) for any prompts, responses or documents accessible through AnswerVault, and will not rely on the Processor to make disclosure decisions;
- will make sure its users know that they are interacting with an AI system, that outputs are AI-generated and must be independently verified, and that they should not include third-party Personal Data in prompts unless the query needs it.
4. Processor obligations
For Personal Data processed under this DPA, the Processor will:
4.1 Instructions
Process Personal Data only on the Controller's documented instructions, which are this DPA, Schedule 1, the Terms of Service and the Controller's configuration of the Service, as updated by the Controller in writing. This includes transfers outside the UK, which are made only as set out in clause 5. The Processor will tell the Controller if it believes an instruction infringes UK GDPR or other data protection law. Where this DPA and the Terms of Service differ on the processing of Personal Data, this DPA prevails.
4.2 Confidentiality
Ensure everyone authorised to process Personal Data under this DPA is bound by confidentiality obligations, contractual or statutory, and has received appropriate data protection training.
4.3 Security
Implement and maintain appropriate technical and organisational measures to protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access, as required by UK GDPR Article 32. The measures in place are set out in Schedule 3, and are documented in the Processor's ISO/IEC 27001:2022 Statement of Applicability and reviewed at least annually.
4.4 Sub-processors
The Controller gives the Processor general authorisation to engage the sub-processors listed in Schedule 2, subject to this clause. The Processor will:
- impose data protection obligations on each sub-processor that are no less protective than those in this DPA;
- give at least 14 days' notice of any intended addition or replacement of a sub-processor, by updating Schedule 2 on this page and emailing the Controller's account owner, during which the Controller may object in writing on reasonable data protection grounds; if the parties cannot resolve the objection, the Controller may terminate the Services without penalty;
- remain fully liable to the Controller for each sub-processor's acts and omissions as if they were its own.
4.5 Data subject rights
Provide reasonable assistance to the Controller to respond to requests to exercise data subject rights under UK GDPR Chapter III, in time for the Controller to meet its statutory deadlines. The Controller remains responsible for receiving, assessing and responding to those requests, and the Processor will not respond to a data subject directly unless the Controller instructs it to.
4.6 Assistance with Controller obligations
Provide reasonable assistance to the Controller with its obligations under UK GDPR Articles 32 to 36: security of processing, notifying Personal Data breaches to the ICO and to data subjects, Data Protection Impact Assessments, and prior consultation with the ICO.
4.7 Deletion and return of data
On termination of the Terms of Service, or on the Controller's written request, the Processor will, at the Controller's choice, either securely delete all Personal Data processed under this DPA within 30 days, including document vectors, chunk text stored for retrieval and citation, prompt and response logs and any cached content for the Controller's tenant, or return a copy to the Controller in a portable format before deleting it. The Processor will confirm deletion in writing on request. This does not apply where the law requires the Processor to keep Personal Data; it will then tell the Controller and restrict processing to what the law requires.
Audit records of activity on the Controller's tenant (who did what and when, recorded by identifier, and containing no document content, prompts or responses) are kept for 24 months in tamper-proof storage, for the security of the Services and as evidence of the Processor's security controls, and are then deleted. They are not deleted under this clause and are used for no other purpose.
4.8 Audit and inspection
Make available to the Controller all information reasonably necessary to demonstrate compliance with this DPA and UK GDPR Article 28, and allow and contribute to audits and inspections by the Controller or its appointed auditor, subject to:
- at least 20 business days' prior written notice;
- the audit taking place during normal business hours without unduly disrupting the Processor's operations;
- the Controller bearing the cost unless the audit reveals a material breach by the Processor;
- the auditor signing a confidentiality undertaking if the Processor asks.
The Processor may meet these obligations in whole or in part by providing its current ISO/IEC 27001:2022 certificate, SOC 2 report once obtained, or equivalent third-party audit reports.
5. International transfers
The Processor will not transfer Personal Data outside the UK except to the sub-processors in Schedule 2 and in compliance with UK GDPR Chapter V.
The Processor's Azure OpenAI resource is in the UK South region, and data stored at rest by the service remains in the UK. The models are deployed as Global Standard deployments, so prompts, document content and responses sent for inference and embedding may be processed in any Azure region where the model is deployed, including outside the UK. Those transfers are covered by the Microsoft Products and Services Data Protection Addendum, which incorporates the Standard Contractual Clauses and the UK Addendum, and by Microsoft's certification under the EU-US Data Privacy Framework (UK Extension). Messages relayed from Microsoft Teams pass through Azure Bot Service, which is also a global service covered by the same terms. Under the Azure OpenAI Service terms, prompts, completions and embeddings are not used to train models and are not shared with OpenAI.
Microsoft Corporation is US-incorporated, so US CLOUD Act jurisdiction applies regardless of where data is processed. For sub-processors in countries without a UK adequacy decision, the Processor will make sure appropriate safeguards are in place and provide transfer documentation to the Controller on request.
6. Security incidents
The Processor will:
- notify the Controller without undue delay, and in any event within 48 hours of becoming aware, of any Security Incident affecting Personal Data processed under this DPA;
- include in that notification, or as soon as reasonably practicable afterwards, the nature of the incident, the categories and approximate number of data subjects and records affected, the likely consequences, and the measures taken or proposed to address it and mitigate its effects;
- cooperate with the Controller in investigating the incident, notifying the ICO where Article 33 requires it, and communicating with affected data subjects where Article 34 requires it;
- not make any public statement, or notify data subjects or regulators about the incident, without the Controller's prior written consent, except where the law requires it.
7. Liability
Each party's liability under this DPA is subject to the limitations in the Terms of Service. Nothing in this DPA limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for any liability that cannot be excluded by law.
8. Governing law
This DPA is governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction over disputes arising under it.
9. Changes to this DPA
The Processor may update this DPA to reflect changes in data protection law or in the Services by giving 30 days' written notice, except for sub-processor changes, which follow clause 4.4. Changes that would reduce the protection given to Personal Data will not be made. The current version is always published at this address, with the date it was last updated.
Schedule 1: Processing details
| Subject matter | Providing the AnswerVault AI-powered document query service. |
|---|---|
| Duration | The term of the Terms of Service, plus any retention period the law requires. |
| Nature of processing | Document ingestion, including conversion of legacy Office files within the Processor's infrastructure and model-assisted processing of document content (text, page images and spreadsheet rows) to extract context and structure; chunking; vector embedding; storage of vectors and chunk text; retrieval of relevant document chunks in response to user queries; LLM inference to generate responses; logging of user prompts and AI responses; deletion on termination or request. |
| Purpose | To let the Controller's users query their own connected document repositories through an AI chat interface. |
| Categories of personal data | Names, contact details and identifiers of individuals referenced in connected documents; organisational data the Controller connects, such as staff records, correspondence and internal documents; structured tabular data from connected spreadsheets, which may contain personal data in bulk, such as customer lists, ledgers or staff exports; user prompts, which may contain personal data about third parties; AI-generated responses, which may reproduce personal data from source documents. |
| Categories of data subjects | The Controller's employees and contractors whose data appears in connected documents; third parties referenced in the Controller's documents; the Controller's users of AnswerVault, whose query logs are retained. |
| Special category data | Not to be connected without prior written agreement. If the Controller's documents contain special category data (UK GDPR Article 9), the Controller must tell the Processor and obtain written agreement before connecting those sources. |
| Controller's instructions | Process Personal Data only to provide AnswerVault as described above. Do not use Personal Data for any other purpose, including improving or training AI models. Send sub-processors only the data each processing operation needs. Keep prompt and response logs (chat history) for no longer than 12 months. Delete all Personal Data within 30 days of termination or a written instruction to delete, other than audit records kept under clause 4.7. |
Schedule 2: Approved sub-processors
The Processor will give at least 14 days' notice before adding or replacing a sub-processor, as set out in clause 4.4.
| Sub-processor | Role | Location | Transfer mechanism |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud infrastructure hosting: compute, storage, vector database, PostgreSQL. | United Kingdom, AWS eu-west-2 (London) | No transfer: processing remains in the UK. |
| Microsoft Ireland Operations Limited (Microsoft Corporation group): Azure OpenAI Service | LLM inference and vector embedding: receives document content at ingest, document chunks and user prompts. | Resource in UK South; data at rest in the UK. Global Standard deployments: inference may be processed in any Azure region. | Microsoft Products and Services Data Protection Addendum, including the Standard Contractual Clauses and the UK Addendum. No training on inputs; inputs are not shared with OpenAI. |
| Microsoft Ireland Operations Limited (Microsoft Corporation group): Azure Bot Service | Relays messages between Microsoft Teams and AnswerVault, only where the Customer uses the AnswerVault Teams app. | Global service: may be processed in any Azure region. | Microsoft Products and Services Data Protection Addendum, including the Standard Contractual Clauses and the UK Addendum. |
Enterprise customers who have agreed a self-hosted or customer-specified model have that agreement's sub-processors in place of the Azure OpenAI row.
Schedule 3: Security measures
| Measure | Description |
|---|---|
| Encryption in transit | TLS 1.2 or higher for all data transmitted between client, Catapult infrastructure and sub-processors. |
| Encryption at rest | AES-256 encryption of data at rest on AWS infrastructure. OAuth tokens for connected sources are additionally encrypted at application level. |
| Tenant isolation | Mandatory tenant filter on all database queries; tenant scoping derived from the authenticated session, never from client input, and enforced in the data-access layer; tenant-scoped cache keys; cross-tenant retrieval integration tests on every release. |
| Access control | Role-based access control; least privilege; MFA required for all administrative access; access reviews. |
| Audit logging | Audit logs across all system layers, kept for 24 months in tamper-proof (write-once) storage, then deleted. |
| Vulnerability management | Security review in the product development lifecycle; dependency scanning; penetration testing before major releases. |
| Incident response | Documented incident response procedure; incidents classified P1 to P4; P1 and P2 incidents escalated immediately, with a post-incident review within 5 working days. |
| ISO/IEC 27001 certification | Catapult CX holds ISO/IEC 27001:2022 certification; the ISMS is reviewed annually and subject to surveillance audits. |
| AI-specific controls | System prompt guardrails (assistive-only framing, source citations, out-of-scope deflection); document ingestion review policy; human-in-the-loop design; legacy Office files converted in an isolated component with no database, secrets or internet access. |
| Staff training | All staff complete annual information security and AI governance awareness training, with completion records kept. |
The Processor will tell the Controller of any material change to its security measures that reduces the protection they give. The Controller may ask for the Processor's current ISO/IEC 27001 certificate, and SOC 2 report once available, at any time.
Last updated 11/11/2026