Sub-processors

What a sub-processor is

When you run a survey you are the controller and we are your processor. Anyone we engage to carry out part of that processing — the company that runs the database, the company that delivers the sign-in email — is a sub-processor. Article 28 UK GDPR says we may only engage one with your authorisation, and that we must impose the same data protection obligations on them that we owe you. Our data processing agreement gives that authorisation for the providers listed above and sets out how additions are handled.

Notes on individual entries

Supabase and Amazon Web Services

These two are the ones that matter for survey data. Supabase provides the database, authentication and file storage; it runs on AWS infrastructure in the London region. Survey definitions, responses, saved partial answers and uploaded files all live here and nowhere else. The controls applied to them — row-level security, server-side organisation isolation, a private upload bucket with short-lived signed URLs — are described on the security page.

Resend

Listed for transactional email. Emailing survey owners when a response arrives sends through Resend when a survey has notification addresses set. Where it is used it would receive an email address and the content of the message. It does not receive survey responses. Account and authentication email is handled by Supabase, which is already on this list.

Anthropic

This row is published ahead of the processing, not because of it. Automated summarisation of free-text answers is not built, and no response content is sent to Anthropic today. We are listing it now because the commitment on this page is to publish an addition before it starts processing, and a list that only ever catches up afterwards is not worth much.

The terms on which that processing would happen — what is sent, what is stripped first, whether the survey owner has to switch it on — are not settled, and we are not going to describe them here before they are. This page and the UK GDPR page will carry the detail before the feature is available, not after.

Hostinger

Provides the virtual private server that runs the web application itself. It sees technical connection data and application logs rather than survey content, which is stored in Supabase. We have not yet confirmed the data centre region for this server, so the location and transfer safeguard are marked to be confirmed rather than stated.

Google (Workspace)

Business email and document storage. Survey data does not flow through it. It is listed because support correspondence can contain personal data the moment a customer pastes some into an email, and a sub-processor list that quietly omits the place your emails land is not a complete one. The data region is not yet confirmed.

How we change this list

We publish changes to this list before a new sub-processor begins processing. Customers with a signed data processing agreement may object to an addition on reasonable data protection grounds; the DPA sets out what happens then. Removals are published as they happen. The "last reviewed" date at the top of this page changes whenever any row does, so it is a safe thing to diff or bookmark.

If you need this list attached to a procurement return, or need a confirmed region before you can sign, ask through the contact page and we will chase the provider and update the row rather than give you a verbal answer.