Legal
Subprocessors
The service providers hootform uses to run the service, what each receives and where.
Last updated 20 October 2026
These are the companies that handle customer data on hootform's behalf. Each is bound by a data protection agreement and uses the data only to provide their service to us. Our Privacy Policy explains how this fits together.
Our subprocessors
| Service | What for | What reaches them | Where |
|---|---|---|---|
| DigitalOcean | Hosting: application servers, the database and file storage | Everything stored in hootform: accounts, forms, responses and attached files | European Union |
| Resend | Sending email: sign-in codes, invitations and response notifications | Recipients' email addresses and the message, which for a notification includes the response | United States |
| Dodo Payments | Merchant of record for Premium: checkout, payment, invoices and sales tax | The buyer's name, email, billing address and payment details, which they enter with Dodo directly | See their policy |
| Anthropic | AI features: building a form, follow-up questions, AI insights, response summaries and translation | The form's text and, for follow-ups, insights and summaries, typed answers that aren't identifying | United States |
| OpenAI | The same AI features when they run on OpenAI, and checking typed answers for spam | As for Anthropic, plus short and long text answers as they're submitted, for the spam check | United States |
| Cloudflare | Turnstile: telling people from bots at sign-in, on the demo and when a response starts | The visitor's IP address and browser signals | Global |
| Sign in with Google, for people who choose it | The Google account's name and email address | United States |
hootform's own servers, database and file storage run in the European Union. Where data reaches a provider outside the EU or UK, the transfer relies on an adequacy decision (such as the EU–US Data Privacy Framework) or on the European Commission's Standard Contractual Clauses.
Services you choose to use
These aren't our subprocessors: data goes to them because an editor connected or embedded them in a form. Their own terms and policies apply.
| Service | What for | What reaches them | Where |
|---|---|---|---|
| Google Sheets | Adding each completed response as a row in a spreadsheet the editor connects | The responses of the forms it's connected to | United States |
| Unsplash | Searching for and showing photos an editor picks for a form | Editors' search terms; respondents' browsers load the picked photos from Unsplash | Global |
| YouTube, Vimeo and Loom | Videos an editor embeds in a form | Respondents' browsers load the video from the provider | Global |
| Webhook endpoints | Delivering completed responses to a URL the editor sets | The responses of the forms it's set on | Wherever the editor's server is |
Changes to this list
We'll update this page at least 30 days before a new subprocessor starts handling customer data, and change the date at the top. To be told by email when it changes, or to object to a new subprocessor, write to [email protected].