
Between VerifyFlow (Processor) and Customer (Controller)
Last updated: January 2026 | UK GDPR Compliant
All personal data processed and stored within United Kingdom infrastructure
Full processor obligations under UK GDPR Article 28(3) are met
Complete list of sub-processors disclosed with safeguard details
72-hour breach notification and full rights assistance guaranteed
1.1. In this Data Processing Agreement (“DPA”), the following terms shall have the meanings set out below unless the context otherwise requires:
1.2. The terms “Commissioner”, “Data Protection Impact Assessment”, and “International Transfer” shall have the meanings given to them in the Applicable Data Protection Law.
1.3. This DPA is incorporated into and forms part of the principal agreement between the Controller and the Processor for the provision of the Services (“Principal Agreement”). In the event of any conflict between this DPA and the Principal Agreement, this DPA shall prevail with respect to data protection matters.
2.1. This DPA applies to all Processing of Personal Data carried out by the Processor on behalf of the Controller in connection with the provision of the Services.
2.2. The Processor shall Process Personal Data for the duration of the Principal Agreement, unless otherwise agreed in writing or required by Applicable Data Protection Law.
2.3. Upon termination or expiry of the Principal Agreement, the Processor shall, at the Controller’s election, either return or delete all Personal Data in its possession, except to the extent that retention is required by Applicable Data Protection Law or for the establishment, exercise, or defence of legal claims. The Processor shall confirm deletion in writing upon request.
2.4. The obligations and rights of the Controller and the Processor set out in this DPA shall survive the termination or expiry of the Principal Agreement to the extent necessary to give effect to the provisions of this DPA.
3.1. The Processor shall Process Personal Data solely for the purpose of providing the Services to the Controller, which include:
3.2. The Processor shall not Process Personal Data for any purpose other than as set out in this DPA or as otherwise instructed by the Controller in writing.
4.1. The categories of Data Subjects whose Personal Data may be Processed under this DPA include:
4.2. The Controller warrants that it has a lawful basis for providing the Personal Data of Data Subjects to the Processor and that all necessary consents have been obtained or other lawful bases established prior to initiating any Processing.
5.1. The following types of Personal Data may be Processed:
5.2. The Processor acknowledges that biometric data constitutes Special Category Data and shall apply enhanced safeguards as set out in this DPA, including obtaining explicit consent from the Data Subject prior to biometric Processing.
6.1. The Controller shall:
7.1. The Processor shall, in accordance with Article 28(3) of the UK GDPR:
7.2. The Processor shall immediately inform the Controller if, in its opinion, an instruction infringes the UK GDPR or other Applicable Data Protection Law.
8.1. The Controller provides general written authorisation for the Processor to engage the Sub-processors listed below. The Processor shall impose data protection obligations no less protective than those set out in this DPA on each Sub-processor by way of a written contract.
8.2. The Processor shall remain fully liable to the Controller for the performance of each Sub-processor’s obligations.
8.3. Current authorised Sub-processors:
| Sub-processor | Purpose | Location | Transfer Safeguard |
|---|---|---|---|
| Vercel Inc. | Application hosting and edge delivery | United States | SCCs |
| AWS (Amazon Web Services) | Object storage and data backups | United Kingdom | Domestic |
| Resend Inc. | Transactional email delivery | United States | SCCs |
| Hetzner Online GmbH | Virtual private server infrastructure | Germany | Adequacy |
8.4. The Processor shall notify the Controller in writing at least 30 days prior to engaging any new Sub-processor or replacing an existing Sub-processor. The Controller may object to such changes within 14 days of receipt of notice. If the Controller objects on reasonable grounds relating to data protection, the parties shall discuss the objection in good faith. If no resolution is reached, the Controller may terminate the Principal Agreement without penalty.
9.1. The Processor shall not transfer Personal Data to a country or territory outside the United Kingdom unless:
9.2. Where Personal Data is transferred to Sub-processors located in the United States (Vercel, Resend), such transfers are made subject to the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, as applicable.
9.3. Where Personal Data is transferred to Sub-processors located in the European Economic Area (Hetzner, Germany), such transfers benefit from the UK adequacy decision for the EEA.
9.4. The Processor shall conduct and document a transfer risk assessment for each international transfer, evaluating the laws and practices of the destination country, and shall implement supplementary measures where necessary to ensure an essentially equivalent level of protection.
10.1. The Processor implements the following technical and organisational measures pursuant to Article 32 of the UK GDPR:
AES-256 encryption for all stored Personal Data, including identity documents and biometric data, with keys managed via hardware security modules.
TLS 1.3 enforced on all connections. HSTS headers with minimum 12-month max-age. Certificate transparency monitoring enabled.
Role-based access control (RBAC) with least-privilege principle. Multi-factor authentication required for all administrative access. Organisation-level data isolation enforced at application layer.
Immutable, append-only audit trail capturing all data access, modifications, and verification events with SHA-256 integrity hashes. Logs retained for 6 years.
Annual third-party penetration testing conducted by CREST-accredited providers. Vulnerability remediation within 30 days (critical) or 90 days (high severity).
24/7 automated monitoring with alerting. Documented incident response plan with defined roles, escalation paths, and communication procedures. Regular tabletop exercises conducted.
Biometric face descriptors deleted immediately after comparison. Identity document images deleted after 30 days. Only verification outcomes retained long-term.
Automated daily encrypted backups with geographic redundancy. Recovery point objective (RPO) of 24 hours. Recovery time objective (RTO) of 4 hours. Regular restoration testing.
10.2. The Processor shall regularly test, assess, and evaluate the effectiveness of its technical and organisational measures for ensuring the security of Processing, and shall update such measures as necessary to address evolving threats and vulnerabilities.
11.1. The Processor shall, taking into account the nature of the Processing, assist the Controller by appropriate technical and organisational measures to fulfil the Controller’s obligation to respond to requests from Data Subjects exercising their rights under Chapter III of the UK GDPR, including:
11.2. Where the Processor receives a request from a Data Subject directly, it shall promptly redirect the Data Subject to the Controller and notify the Controller of the request within 24 hours.
11.3. The Processor shall respond to the Controller’s requests for assistance in relation to Data Subject rights within 72 hours, providing all relevant information and technical support necessary for the Controller to fulfil its obligations within the statutory timeframes.
11.4. The Processor shall maintain technical capability to export, rectify, or delete Personal Data relating to individual Data Subjects without affecting the Personal Data of other Data Subjects.
12.1. The Processor shall notify the Controller without undue delay, and in any event within 72 hours, after becoming aware of a Personal Data Breach affecting Personal Data Processed on behalf of the Controller.
12.2. Such notification shall include, to the extent available:
12.3. Where it is not possible to provide all information at the same time, the Processor shall provide the information in phases without further undue delay.
12.4. The Processor shall cooperate with the Controller and take such reasonable steps as directed by the Controller to assist in the investigation, mitigation, and remediation of each Personal Data Breach.
12.5. The Processor shall document all Personal Data Breaches, comprising the facts relating to the breach, its effects, and the remedial action taken, and shall make such documentation available to the Controller and the Commissioner upon request.
13.1. The Processor shall retain and delete Personal Data in accordance with the following schedule, unless the Controller provides alternative written instructions or Applicable Data Protection Law requires otherwise:
| Data Category | Retention Period | Justification |
|---|---|---|
| Identity document images | 30 days | Verification complete; evidence pack generated |
| Biometric face descriptors | Immediate | Deleted upon completion of facial comparison |
| Evidence packs & audit logs | 6 years | MLR 2017 record-keeping obligations |
| Screening results | 6 years | MLR 2017 / Proceeds of Crime Act 2002 |
| Account and contact data | Duration + 30 days | Deleted 30 days after account termination |
13.2. The Processor employs automated retention enforcement through scheduled processes that identify and securely delete Personal Data upon expiry of the applicable retention period.
13.3. Deletion shall be carried out using industry-standard secure deletion methods that render the Personal Data irrecoverable. The Processor shall provide written confirmation of deletion upon the Controller’s request.
13.4. Notwithstanding the above, the Processor may retain Personal Data to the extent required by Applicable Data Protection Law, provided that the Processor shall ensure the confidentiality of such Personal Data and shall Process it only for the purpose required by law.
14.1. The Processor shall make available to the Controller all information necessary to demonstrate compliance with the obligations laid down in this DPA and Article 28 of the UK GDPR.
14.2. The Processor shall allow for and contribute to audits, including on-site inspections, conducted by the Controller or an independent third-party auditor mandated by the Controller, subject to the following conditions:
14.3. The Processor may satisfy audit requests by providing the Controller with a summary of the results of any independent third-party audit or certification (such as SOC 2 Type II or ISO 27001) conducted within the preceding 12 months, provided that such report adequately addresses the Controller’s concerns.
15.1. This DPA shall be governed by and construed in accordance with the laws of England and Wales.
15.2. The parties submit to the exclusive jurisdiction of the courts of England and Wales for the resolution of any disputes arising out of or in connection with this DPA.
15.3. Nothing in this DPA shall limit or exclude the rights of Data Subjects or the powers of the Information Commissioner’s Office under Applicable Data Protection Law.
15.4. If any provision of this DPA is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect. The parties shall negotiate in good faith a replacement provision that achieves the same purpose as the original provision to the greatest extent permitted by law.
15.5. This DPA, together with the Principal Agreement and any schedules or annexes hereto, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior or contemporaneous agreements, understandings, and communications, whether written or oral.
For a pre-signed copy of this DPA, contact legal@verifyflow.uk