Sub-processor Register
Version 2.1 · Last updated 14 November 2026
This register is Annex 3 to our Data Processing Agreement. It lists every third party that processes personal data on our behalf in providing the service, what each one receives, where it operates, and the safeguard we rely on for any transfer outside the United Kingdom. We give workspace owners at least 30 days' notice by email before adding or replacing a sub-processor, as the DPA describes.
1. Infrastructure sub-processors
These providers host or transmit customer data as part of running the service.
| Sub-processor | Function | Data it receives | Location | Transfer safeguard |
|---|---|---|---|---|
| DigitalOcean, LLC | Hosting: application servers, managed PostgreSQL database, backups, DNS | All customer data, at rest and in use | London (LON1), United Kingdom | Data stays in the UK. DigitalOcean's data processing agreement; UK Addendum to the EU SCCs for any incidental support access from outside the UK |
| Amazon Web Services EMEA SARL | Transactional email (Simple Email Service) | Recipient email address and the content of alert, verification and billing emails | London (eu-west-2), United Kingdom | Data stays in the UK. AWS data processing addendum; UK Addendum to the EU SCCs for any incidental support access |
| Stripe Payments Europe, Ltd and Stripe, Inc. | Payments, invoicing, VAT calculation | Billing contact name, address, email and country, VAT number, card details (held by Stripe, never by us), level, billing interval and currency, the number of billed clients (a count only, never client names), invoice data | Ireland and the United States | Stripe's data processing agreement; UK Extension to the EU–US Data Privacy Framework and the UK Addendum to the EU SCCs |
Planned
| Sub-processor | Function | Data it would receive | Location | Status |
|---|---|---|---|---|
| Wasabi Technologies, Inc. | Object storage for generated reports and data exports | The contents of PDF reports and export files | London (eu-west-1-london), United Kingdom | Not yet in use. Reports and exports are currently stored on our own servers in London. We will give the 30-day notice before this provider is engaged |
We do not currently use any third-party error-monitoring, analytics or customer-messaging service. If we engage one, it will be added here with notice.
2. Certificate and domain look-up sources
To discover certificates and read domain expiry dates the service queries public sources. Each query contains the domain name being checked and nothing else: no client name, no MSP name, no contact details. A domain name is personal data only in the rare case that it identifies a person, which is why these sources appear in this register.
| Source | Operator | Function | Data sent | Location | Safeguard |
|---|---|---|---|---|---|
| Cert Spotter | SSLMate, Inc. | Certificate Transparency log search | Domain name | United States | Public certificate data; data minimisation (domain name only); UK Addendum to the EU SCCs or UK Extension to the DPF where certified |
| Censys Search | Censys, Inc. | Certificate Transparency log search (secondary) | Domain name | United States | As above |
| crt.sh | Sectigo Limited | Certificate Transparency log search (fallback) | Domain name | United Kingdom | Public certificate data; no transfer outside the UK |
| RDAP and WHOIS | The registry or registrar responsible for each domain, via the IANA bootstrap service | Reading a domain's registration and expiry date | Domain name | Worldwide, determined by the domain's top-level domain | Public registration data published by the registry under ICANN or national rules; data minimisation. No contract is possible with a public registry; the query is the same one any member of the public can make |
| Direct TLS check | Tidehawk, from our own servers | Reading the certificate a server presents | A connection to the customer's own server, on the customer's authority | London, United Kingdom | No third party involved |
3. Notes for auditors
- The primary Certificate Transparency source is Cert Spotter; Censys and crt.sh are used when it is unavailable. Which sources are active is set at platform level and shown here.
- A per-workspace option to restrict discovery to the direct TLS check and UK-based sources only is on our roadmap. It is not available today and should not be relied on until it is announced under the DPA's notice process.
- Backups of the database are held by DigitalOcean in the same London region as the database and rotate within 35 days.
- Tidehawk staff access customer data only from the administration console, with mandatory two-factor authentication, and every such access is logged as described in Annex 2 of the DPA. Staff are located in the United Kingdom.
4. Version history
| Version | Date | Change |
|---|---|---|
| 2.1 | 14 November 2026 | Stripe row: billing moved to per-client pricing; the count of billed clients, billing country and currency are now sent. No sub-processor added or replaced. |
| 2.0 | 23 September 2026 | Full rewrite. DNS moved from Cloudflare to DigitalOcean. Self-hosted error monitoring removed as not in use. Wasabi marked as planned rather than current. Registry operators, Stripe entities and transfer mechanisms stated precisely. |
| 1.0 | 11 July 2026 | First published register. |