Data Processing Agreement

This DPA is incorporated into the Terms of Service by reference.
Effective date: [DATE] · Last updated: [DATE]
ComplyPass Ltd · Company No. [NUMBER]

This Data Processing Agreement ("DPA") is entered into between ComplyPass Ltd ("Processor") and each customer who uses the Platform in a capacity where the Processor handles personal data on the customer's behalf ("Controller").

This DPA complies with Article 28 of UK GDPR and the Data Use and Access Act 2026 (DUAA).

1. Scope & Definitions

"Personal Data" has the meaning given in UK GDPR. "Processing" has the meaning given in UK GDPR. "Data Subject" has the meaning given in UK GDPR. "Sub-processor" means a third party engaged by the Processor to process Personal Data on the Controller's behalf.

This DPA applies to all Processing of Personal Data carried out by the Processor in connection with providing the Service, as described in Schedule 1.

2. Documented Instructions

The Processor shall process Personal Data only on documented instructions from the Controller, including with regard to international transfers of Personal Data, unless required to do so by UK or EU law, in which case the Processor shall inform the Controller of that legal requirement before Processing, unless that law prohibits such information on important grounds of public interest.

The Terms of Service constitute the Controller's documented instructions. The Controller may provide additional instructions via email to privacy@complypass.co.uk.

3. Confidentiality

All personnel of the Processor who are authorised to process Personal Data have committed themselves to confidentiality obligations (contractual or statutory) and are aware of the penalties attached to breach of such obligations. The Processor shall ensure that such personnel only process Personal Data on the Controller's instructions.

4. Security of Processing (Article 32 UK GDPR)

The Processor shall implement the technical and organisational measures set out in Schedule 2, which are appropriate to the risk and the nature of the data. These measures include, without limitation:

The Processor shall promptly investigate and report any suspected or confirmed security incident to the Controller.

5. Sub-processors

The Controller grants general authorisation for the Processor to engage the sub-processors listed in Schedule 3. The Processor may add or replace sub-processors, provided that:

  1. The Processor gives the Controller at least 30 days' prior written notice (by email) of any intended addition or replacement.
  2. The notice identifies the new/replacement sub-processor, their location, and the scope of Processing.
  3. The Controller may object on reasonable data protection grounds within the 30-day period.
  4. If the objection cannot be resolved through good-faith discussion, the Controller may terminate the affected portion of the Service without penalty, and the Processor shall refund any pre-paid fees for the terminated portion.
  5. The Processor remains fully liable to the Controller for the performance of each sub-processor's obligations.

6. Data Subject Rights

The Processor shall, taking into account the nature of the Processing, assist the Controller by appropriate technical and organisational measures, insofar as this is possible, in fulfilling the Controller's obligation to respond to Data Subject requests (access, rectification, erasure, restriction, portability, objection) under UK GDPR and the DUAA 2026.

The Processor shall notify the Controller without undue delay (and in any event within 5 working days) of receiving any Data Subject request directed at the Processor, and shall not respond to the Data Subject directly without the Controller's prior written consent, unless required by law.

The Processor shall provide such assistance within 10 working days of the Controller's request, at no additional cost.

7. Breach Notification & Assistance

  1. The Processor shall notify the Controller of any confirmed or reasonably suspected personal data breach without undue delay and in any event within 24 hours of becoming aware of it.
  2. The notification shall include: the nature of the breach, categories and approximate number of Data Subjects affected, likely consequences, and measures taken or proposed to address the breach.
  3. The Processor shall provide reasonable assistance to the Controller in meeting the Controller's own breach notification obligations (72 hours to the ICO under UK GDPR, or the relevant EU supervisory authority).
  4. The Processor shall assist the Controller with any Data Protection Impact Assessment (DPIA) or prior consultation with a supervisory authority, insofar as this is practicable.

8. Deletion or Return of Data

At the end of the Service (upon cancellation or termination), the Processor shall, at the Controller's choice, delete or return all Personal Data processed on the Controller's behalf, and delete existing copies, unless:

The Controller may request a certificate of deletion within 30 days of the deletion date.

9. Audits & Compliance

  1. The Processor shall make available to the Controller all information necessary to demonstrate compliance with this DPA, including information about the technical and organisational measures in place.
  2. The Controller (or an independent auditor appointed by the Controller) may audit the Processor's compliance, subject to the following:

10. International Transfers

Where the Processor or any sub-processor transfers Personal Data to a country outside the UK (or outside the EEA, for EU data subjects), such transfer shall be made only under an appropriate transfer mechanism, including:

Under the DUAA 2026, the Processor has assessed whether the level of protection afforded in the destination country is "materially lower" than in the UK. The Processor's assessment is documented and available to the Controller on request.

11. Complaint Handling (DUAA 2026)

The Processor acknowledges the Controller's right to complain about the Processor's handling of Personal Data. The Processor shall:

  1. Designate privacy@complypass.co.uk as the contact point for complaints.
  2. Acknowledge receipt of a complaint within 5 working days.
  3. Investigate and provide a substantive response within 14 days of acknowledgement.
  4. Cooperate with the Controller in any subsequent escalation to the ICO or a relevant supervisory authority.

12. Liability

The Processor's liability under this DPA is subject to the liability cap set out in Section 11 of the Terms of Service. The data protection sub-cap (200% of annual fees) applies to claims arising from a breach of this DPA.

Nothing in this DPA limits the Processor's liability for: (a) breach of confidentiality; (b) wilful misconduct; (c) death or personal injury caused by negligence.

13. Term

This DPA takes effect on the date the Controller accepts the Terms of Service and continues for the duration of the Service. It survives termination for the purposes of Sections 7, 8, 9, and 12.

Schedule 1: Subject Matter, Duration, Nature & Purpose

ItemDetail
Subject matterCompliance data management and exchange service (the Platform)
DurationFor the duration of the Controller's active subscription + 90-day post-cancellation data export period + 10-year regulatory retention (where applicable)
Nature & purpose of ProcessingStorage, retrieval, structuring, template injection, document generation (PDF/CSV), expiry tracking, audit logging, and facilitated exchange between Controller and specific counterparties for the purpose of meeting regulatory obligations (CRA, CSRD/VSME, CBAM, EUDR, PPWR, DPP, EAA)
Types of Personal DataNames, email addresses, job titles, company names, company registration numbers, and any personal data contained within compliance documents (e.g., names of directors in a company filing)
Categories of Data SubjectsThe Controller's employees, officers, directors, and authorised representatives; counterparties (Buyers/Suppliers) with whom data is exchanged

Schedule 2: Technical & Organisational Measures

MeasureDetail
Encryption in transitTLS 1.3 for all data in transit (Worker to client, Worker to D1/R2, Worker to sub-processors)
Encryption at restAES-256 (Cloudflare D1 and R2 native encryption)
Access controlRole-based authentication via Clerk. Per-user session tokens. No shared credentials. No admin endpoint exposing user data contents.
Network securityCloudflare Workers sandbox (per-request isolation). No persistent server. No open ports. WAF (Cloudflare).
Audit loggingAll data access events logged (user ID, timestamp, action, resource). Data contents NOT logged. Logs retained 12 months.
Development securityInput validation on all user inputs. Parameterised SQL queries (no string concatenation). No user data in server logs. Code reviewed before deployment.
Data minimisationOnly data necessary for the Service is collected. No data is collected for marketing, profiling, or model training.
Personnel securityAccess to production infrastructure limited to the sole operator. 2FA enabled on all accounts. No third-party access to production data.
Incident responseOn detection of a security incident: (1) contain, (2) assess, (3) notify Controller within 24 hrs, (4) remediate, (5) document.
Backup & recoveryCloudflare-managed backups for D1. R2 versioning enabled. RPO: 24 hours. RTO: 4 hours.

Schedule 3: Sub-processor List

Sub-processorFunctionLocationData accessed
Cloudflare (D1, R2, Workers, Browser Rendering, Queues)Data storage, compute, file storage, PDF rendering, event processingEU (Frankfurt)All data (as infrastructure layer)
ClerkAuthentication, session management, user directoryUS (AWS)Email, name, user ID, session tokens
PaddleBilling, invoicing, tax calculation, payment processingUK / USBilling email, company name, payment status
ResendTransactional email deliveryUS / UKEmail address, name (for personalisation)

Last updated: [DATE]. Changes to this list are subject to the 30-day notice requirement in Section 5.