Privacy Policy
Effective date: [DATE] · Last updated: [DATE]
ComplyPass Ltd · Registered in England & Wales · Company No. [NUMBER]
1. Who We Are
ComplyPass Ltd ("we", "us", "our") is a data controller and a data processor. As a controller, we process your personal data for our own purposes (account management, billing, security). As a processor, we process your compliance data on your documented instructions (the Terms of Service).
Registered office: [ADDRESS]
Company No. [NUMBER]
Email: privacy@complypass.co.uk
2. What We Collect
As Data Controller (our own purposes)
- Account data: Name, email address, company name, company registration number, role (Supplier/Buyer).
- Billing data: Processed by Paddle (our Merchant of Record). We receive confirmation of payment status but do not store card numbers or payment details.
- Usage data: Login timestamps, feature usage, page views (for security and service improvement).
As Data Processor (on your behalf)
- Compliance data: Company information, materials, origin data, emissions data, SBOMs, vulnerability data, sustainability metrics, code of conduct confirmations, and any other data you enter into your vault.
- Documents: Generated PDFs, spreadsheets, refusal letters, declarations, technical files.
- Audit trail: Records of data shared, with whom, when, in what format.
- Questionnaires & responses: Uploaded questionnaires and completed responses.
3. Lawful Basis for Processing
| Purpose | Role | Lawful Basis |
| Account management, service delivery | Controller | Contract performance (Art. 6(1)(b) UK GDPR) |
| Security, fraud prevention, abuse detection | Controller | Legitimate interests (Art. 6(1)(f) UK GDPR) |
| Billing (via Paddle) | Controller | Contract performance (Art. 6(1)(b)) |
| Processing your compliance data | Processor | Documented instructions from you (Art. 28 UK GDPR) |
| Regulatory retention (10-year) | Processor | Legal obligation (Art. 6(1)(c)) — as instructed by you |
4. Where Data Is Stored
All data is stored in the European Union (Frankfurt region) on Cloudflare infrastructure (D1 database, R2 object storage). No compliance data is stored outside the EU.
Account and billing metadata may be processed by our sub-processors in the UK and US (see Section 5).
5. International Transfers
Where personal data is transferred to the UK or US by our sub-processors (Clerk, Paddle, Resend), we rely on the UK Extension to the EU-US Data Privacy Framework (for US transfers) and the UK adequacy regulation (for UK transfers, which is domestic).
Under the Data Use and Access Act 2026 (DUAA), we have assessed whether the level of protection in the destination country is "materially lower" than in the UK. We conclude it is not, based on the Data Privacy Framework certification of our sub-processors. We will re-assess if the legal environment in the destination country changes.
6. How Long We Keep Your Data
| Data type | Retention period |
| Account data (name, email, company) | While active + 90 days after cancellation |
| Compliance data (vault, documents, audit trail) | As you configure (default: 10 years). You may set a shorter period. |
| Generated documents (PDFs, spreadsheets) | Same as compliance data (10 years default) |
| Audit log entries | 10 years |
| Billing records (held by Paddle) | As required by Paddle's own retention policy (typically 7 years for tax) |
The 10-year default reflects the retention requirements of multiple EU regulations (CRA, CBAM, EUDR). You may configure a shorter period, but we will warn you if it conflicts with a known regulatory requirement.
7. Who Can See Your Data
- You: Full access to your own data via your dashboard.
- Specific counterparties: When you respond to a Buyer's questionnaire (or as a Buyer, when a Supplier responds to yours), the relevant data is shared with that specific party. See Section 6 of the Terms of Service.
- Sub-processors: Cloudflare (infrastructure), Clerk (auth), Paddle (billing), Resend (email). They access only the data necessary for their specific function.
- Regulators: If legally required (court order, regulatory investigation), we will disclose data as required by law and notify you where permitted.
- We do NOT: Sell your data. Use your compliance data for our own purposes. Share your data with advertisers. Use your data for model training or AI development.
8. Your Rights
Under UK GDPR and the DUAA 2026, you have the right to:
- Access: Request a copy of your personal data.
- Rectification: Correct inaccurate data.
- Erasure: Request deletion (subject to the 10-year regulatory retention exception — see Section 6).
- Restriction: Limit processing in specific circumstances.
- Portability: Receive your data in a structured, machine-readable format (CSV).
- Objection: Object to processing based on legitimate interests.
- Complaint: Lodge a complaint with the ICO or your local supervisory authority.
To exercise any right, email privacy@complypass.co.uk. We will respond within 30 calendar days.
9. Complaint Handling (DUAA 2026)
If you are not satisfied with our response to a data subject request, you may complain to us first. We will:
- Acknowledge your complaint within 5 working days.
- Investigate and respond within 14 days of acknowledgement.
- If you remain unsatisfied, you may escalate to the Information Commissioner's Office (ICO) at ico.org.uk or your local supervisory authority.
10. Security
- Encryption in transit: TLS 1.3.
- Encryption at rest: AES-256 (via Cloudflare D1 and R2).
- Access controls: Role-based authentication via Clerk. No admin endpoint that exposes user data.
- Network isolation: Cloudflare Workers sandbox (each request runs in an isolated environment).
- Audit logging: All data access events are logged.
- We do not log the contents of user data in server logs. Logs contain metadata only (timestamps, status codes, user IDs).
11. Children
The Platform is not intended for individuals under 16. We do not knowingly process the personal data of children.
12. Changes to This Policy
We may update this Privacy Policy. Material changes will be notified by email at least 30 days before taking effect. The "Last updated" date at the top of this page reflects the most recent revision.