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).
"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.
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.
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.
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.
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:
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.
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.
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.
The Processor acknowledges the Controller's right to complain about the Processor's handling of Personal Data. The Processor shall:
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.
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.
| Item | Detail |
|---|---|
| Subject matter | Compliance data management and exchange service (the Platform) |
| Duration | For the duration of the Controller's active subscription + 90-day post-cancellation data export period + 10-year regulatory retention (where applicable) |
| Nature & purpose of Processing | Storage, 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 Data | Names, 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 Subjects | The Controller's employees, officers, directors, and authorised representatives; counterparties (Buyers/Suppliers) with whom data is exchanged |
| Measure | Detail |
|---|---|
| Encryption in transit | TLS 1.3 for all data in transit (Worker to client, Worker to D1/R2, Worker to sub-processors) |
| Encryption at rest | AES-256 (Cloudflare D1 and R2 native encryption) |
| Access control | Role-based authentication via Clerk. Per-user session tokens. No shared credentials. No admin endpoint exposing user data contents. |
| Network security | Cloudflare Workers sandbox (per-request isolation). No persistent server. No open ports. WAF (Cloudflare). |
| Audit logging | All data access events logged (user ID, timestamp, action, resource). Data contents NOT logged. Logs retained 12 months. |
| Development security | Input validation on all user inputs. Parameterised SQL queries (no string concatenation). No user data in server logs. Code reviewed before deployment. |
| Data minimisation | Only data necessary for the Service is collected. No data is collected for marketing, profiling, or model training. |
| Personnel security | Access to production infrastructure limited to the sole operator. 2FA enabled on all accounts. No third-party access to production data. |
| Incident response | On detection of a security incident: (1) contain, (2) assess, (3) notify Controller within 24 hrs, (4) remediate, (5) document. |
| Backup & recovery | Cloudflare-managed backups for D1. R2 versioning enabled. RPO: 24 hours. RTO: 4 hours. |
| Sub-processor | Function | Location | Data accessed |
|---|---|---|---|
| Cloudflare (D1, R2, Workers, Browser Rendering, Queues) | Data storage, compute, file storage, PDF rendering, event processing | EU (Frankfurt) | All data (as infrastructure layer) |
| Clerk | Authentication, session management, user directory | US (AWS) | Email, name, user ID, session tokens |
| Paddle | Billing, invoicing, tax calculation, payment processing | UK / US | Billing email, company name, payment status |
| Resend | Transactional email delivery | US / UK | Email address, name (for personalisation) |
Last updated: [DATE]. Changes to this list are subject to the 30-day notice requirement in Section 5.