Where your data lives
This page states where Tidehawk keeps your data and what crosses a border. It is a description of how the service is built, not legal advice. The authoritative statements are the privacy policy and the sub-processor register.
Storage and processing
Section titled “Storage and processing”| Layer | Provider | Region |
|---|---|---|
| Application and background worker | DigitalOcean App Platform | LON1, London, UK |
| Primary database | DigitalOcean Managed PostgreSQL | LON1, London, UK |
| Transactional email | Amazon Web Services SES | eu-west-2, London, UK |
| Object storage for reports, exports and erasure certificates | Wasabi | eu-west-1, London, UK |
| Error monitoring | Self-hosted GlitchTip on Tidehawk’s own infrastructure | LON1, London, UK |
| DNS | Cloudflare, DNS-only | Global anycast |
Your workspace settings show this as Data residency: DigitalOcean LON1.
Cloudflare provides authoritative DNS only. It is not in front of the application as a proxy, so application traffic and application data do not pass through it. What Cloudflare sees is DNS resolution.
Error monitoring runs on Tidehawk’s own infrastructure in London rather than a third-party service, so diagnostics stay in region.
What leaves the region, and why
Section titled “What leaves the region, and why”No customer data is stored outside the UK or EU. Two kinds of transmission do cross a border.
Certificate and domain look-ups. To discover certificates, Tidehawk queries public Certificate Transparency indexes, and to find domain expiry dates it queries RDAP and WHOIS. Some of those operators are outside the UK. These queries carry the domain name only. They do not carry your workspace identity, your end-client names, or any account data, and nothing of yours is stored on those providers. The results are written to the database in London.
Tidehawk also scans hosts directly from its own workers in London to read the certificate a host is serving. That path involves no third party at all.
Billing. Card payments and invoicing are handled by Stripe, which operates in the United States and globally. Stripe receives your billing contact details, your plan, and the card data you enter on Stripe’s own pages. Tidehawk never holds your card number.
The sub-processor register sets out the transfer safeguard relied on for each provider, including Data Privacy Framework certification and Standard Contractual Clauses with the UK Addendum.
Where your PSA data goes
Section titled “Where your PSA data goes”If you connect a PSA, tickets and alert content are sent to your own PSA instance, wherever you host it. That happens at your direction, and only the ticket content you configure is sent. See Integrations overview.
Controller and processor
Section titled “Controller and processor”For your own account data, Tidehawk is the controller. For the end-client monitoring data you load into Tidehawk, such as client names, domains and certificates, you are the controller and Tidehawk is the processor, acting on your instructions under the Data Processing Agreement at https://tidehawk.co/dpa.