Data processing agreement
1. Definitions
In this agreement, "Controller" is the Customer named in the Order Form and "Processor" is Concept Informatics Ltd ("Concept Informatics"), company number 03893221, 25 Waverley Avenue, Whitley Bay, Tyne and Wear, NE25 8AU, United Kingdom. "Principal Agreement" means the Master Service Agreement and the Order Form between them. "Data Protection Law" means the UK GDPR, the Data Protection Act 2018 and, where it applies, the EU GDPR. "Customer Personal Data", "Personal Data", "Data Subject", "Personal Data Breach" and "Sub-processor" have the meanings in Data Protection Law.
2. Roles and scope
For Customer Personal Data the Controller decides the purposes and means of processing, and the Processor processes it on the Controller's behalf only to provide the services in the Principal Agreement. Each party complies with Data Protection Law. The Controller confirms it has a lawful basis for sharing Customer Personal Data with the Processor and has given the notices needed.
3. Instructions
The Processor processes Customer Personal Data only on the Controller's documented instructions, which are the Principal Agreement and this agreement, unless the law requires otherwise, in which case the Processor tells the Controller first where the law allows. The Processor tells the Controller if it believes an instruction breaks Data Protection Law. The Controller agrees to share personal data with the Processor only in sanitised form wherever the audit allows, and the Processor does not send Customer Personal Data to any AI model provider unless the Controller has approved that provider in writing in the Order Form.
4. Confidentiality
The Processor makes sure that every person authorised to process Customer Personal Data is bound by a duty of confidentiality, and limits access to those who need it.
5. Security
The Processor applies the technical and organisational measures in Annex 2, which are suited to the risk, and reviews them regularly.
6. Sub-processors
The Controller gives general authorisation for the Sub-processors in Annex 3. The Processor tells the Controller of any intended addition or replacement at least 30 days in advance, by email, and the Controller may object on reasonable data protection grounds within that time. If the objection cannot be resolved, the Controller may end the affected service and receive a refund of fees for the period not delivered. The Processor imposes on each Sub-processor the same obligations as in this agreement and stays responsible for them.
7. Helping with Data Subject requests
Taking into account the nature of the processing, the Processor helps the Controller to respond to requests from Data Subjects to use their rights. If a Data Subject contacts the Processor directly, the Processor passes the request to the Controller without undue delay and does not respond except to say it has done so.
8. Personal Data Breaches
The Processor tells the Controller without undue delay, and within 48 hours of becoming aware, of a Personal Data Breach affecting Customer Personal Data, and gives the information the Controller reasonably needs to meet its own duties to notify.
9. Assistance with assessments
The Processor helps the Controller with data protection impact assessments and consultations with the regulator, where they relate to the processing under this agreement, taking into account the nature of the processing and the information available to the Processor.
10. Deletion or return
When the services end, or sooner if the Controller asks in writing, the Processor returns or deletes Customer Personal Data, at the Controller's choice, within 30 days, and deletes existing copies, including from backups on their normal cycle, unless the law requires storage. The Processor confirms deletion in writing on request. This section does not stop the Processor keeping, as a controller in its own right and as its privacy policy describes, the business contact details of the Controller's people, the commercial record of the engagement (fees, dates and the reports delivered) and its change record, for 24 months after the services end, then deleting them. The Processor does not use them for any other purpose.
11. Information and audits
The Processor gives the Controller the information needed to show compliance with this agreement and allows and contributes to audits, including inspections, by the Controller or an auditor it appoints, on reasonable notice, once a year (or more often after a Personal Data Breach), during working hours and subject to confidentiality.
12. International transfers
The Processor does not transfer Customer Personal Data outside the UK and the EEA except as listed in Annex 3 and with a valid transfer mechanism: an adequacy decision, the UK-US data bridge or EU-US Data Privacy Framework for certified providers, or the EU standard contractual clauses with the UK addendum or the UK International Data Transfer Agreement.
13. Liability
Each party's liability under this agreement is subject to the limits and exclusions in the Principal Agreement, to the extent the law allows. Nothing limits a Data Subject's rights or liability that cannot be limited.
14. Term and law
This agreement lasts as long as the Processor processes Customer Personal Data. It is governed by the law that governs the Principal Agreement, which is the law of England and Wales, except where Data Protection Law or a transfer mechanism requires otherwise.
Annex 1: Description of the processing
| Item | Description |
|---|---|
| Subject matter | Provision of the AI ROI Audit, any pilot build and ongoing support to the Controller |
| Duration | The term of the Principal Agreement and the deletion period in section 10 |
| Nature of the processing | Storage, review and analysis of documents, records and interview notes shared for the audit; AI-assisted analysis only where the Controller has approved a provider; presentation of findings; deletion |
| Purpose | To measure the Controller's processes, score AI use cases and prove the best one on sample data |
| Types of Personal Data | Names, business contact details and job roles of staff, and any personal data in the sanitised samples the Controller chooses to share. Special category data is not permitted |
| Categories of Data Subjects | The Controller's staff, and its customers or suppliers where they appear in sanitised samples |
| Frequency | Continuous during the engagement |
Annex 2: Technical and organisational measures
- Access control: unique accounts, least privilege, multi-factor authentication on email, storage, code and cloud accounts, access removed on leaving.
- Audit tool: engagement records are held in the Processor's internal audit tool, which only named staff can sign in to. The database is in the European Union (Frankfurt), is not reachable from a browser, and is reached only through the tool's server with a key held as a server secret. Changes and exports are recorded in a change record that holds no client content. Deleting an engagement removes everything held under it, and deleting the client removes its contacts as well.
- Encryption: TLS in transit; encryption at rest on devices and cloud storage; secrets held in a password manager and never in documents or code.
- Data minimisation: the Controller sanitises samples before sharing; project data is kept in a separate folder per customer and not copied to personal devices outside the encrypted work machine.
- AI tools: no Customer Personal Data is sent to an AI model provider without the Controller's written approval in the Order Form; approved providers are used under business terms that exclude training on inputs; every approved use is recorded.
- Logging and monitoring: access logs on the storage used for project data, reviewed when an incident is suspected.
- Vulnerability management: devices and software kept up to date, automated dependency and secret scanning on code we write.
- Resilience and recovery: backups of project documents, with recovery tested at least yearly.
- People: confidentiality obligations, and data protection and security awareness on joining and yearly.
- Incident response: a documented procedure and breach register, with notification as in section 8.
- Retention and deletion: project data deleted on the schedule in section 10.
Annex 3: Sub-processors
The current list is kept at Sub-processors, which forms part of this annex. Concept Informatics gives notice of changes as section 6 says.
| Sub-processor | Service | Location of processing | Transfer mechanism |
|---|---|---|---|
| Cloudflare, Inc. | Website hosting and delivery, the form-handling Worker and Email Routing used to deliver form submissions | United States and global edge | UK-US data bridge and EU-US Data Privacy Framework certification, with standard contractual clauses as fallback |
| Supabase Pte. Ltd. (Singapore), hosting on Amazon Web Services | Database and sign-in for the internal audit tool that holds engagement records | European Union (Frankfurt, eu-central-1) for the database, sign-in and backups. Usage logs and support access may be in the United States or Singapore. Supabase's own sub-processors are on its published list | Standard contractual clauses, with the UK addendum, incorporated in Supabase's data processing addendum, Irish law |
| Aminos (aminos.ai) | Chatbot platform that runs a website chatbot built for the Controller, and holds the conversations and any contact details visitors enter, only where the Controller has a chatbot | [Location of processing to be confirmed before publication] | [To be confirmed before publication] |
| AI model provider named in the Order Form | AI-assisted analysis of sanitised samples, only where the Controller has approved it in writing | As stated in the Order Form | As stated in the Order Form |