Sub-processors
A sub-processor is a third party that may process personal data on Tidehawk’s behalf while delivering the service.
The register
Section titled “The register”The complete, current list lives at https://tidehawk.co/subprocessors. It is the authoritative version and it is written to be read as-is by an auditor or a data protection officer.
This page deliberately does not reproduce that list. The register is versioned and can change, and a copy in the documentation would eventually disagree with it. Send your auditor to the register, not here.
The register sets out, for each provider:
- What they do for Tidehawk
- What data they process
- Which region they operate in
- The transfer safeguard relied on, such as Data Privacy Framework certification or Standard Contractual Clauses with the UK Addendum
It forms part of, and is incorporated into, the Data Processing Agreement at https://tidehawk.co/dpa.
What the register covers
Section titled “What the register covers”The register groups providers into three kinds, which is useful to know before you read it.
- Core service providers. Hosting, database, transactional email, object storage, payments and DNS. These are the providers that hold or carry your data.
- Public look-up sources. Certificate Transparency indexes and domain registration services, queried with a domain name only, to discover certificates and expiry dates. Nothing of yours is stored on these providers.
- Customer-directed integrations. The PSA platforms. These only come into play when you connect one, and then only your own instance receives your data. See Integrations overview.
A copy of the core list is also shown in the app, under Settings → Sub-processors, with a link through to the full register.
Notice of changes
Section titled “Notice of changes”Tidehawk gives at least 30 days’ advance notice before adding or replacing a sub-processor, so that controllers can object. Material changes are versioned alongside the Data Processing Agreement.
Error monitoring is not a sub-processor
Section titled “Error monitoring is not a sub-processor”Tidehawk runs its own error-monitoring service on its own infrastructure in London rather than sending diagnostics to a third party. It is therefore not listed as a sub-processor. See Where your data lives.
Questions and objections
Section titled “Questions and objections”For a question about a specific provider, an objection to a change, or a request for the more detailed documentation available under a mutual non-disclosure agreement, email privacy@tidehawk.co or use https://tidehawk.co/contact.