Subprocessors
The companies that process data so SuperHQ can run, what each one does, and where.
Last updated 6 November 2026
In use
- Google Cloud (Cloud Run)Runs the application and its background jobsAll service data in transit and while processed · London, United Kingdom
- SupabaseDatabase, sign-in and file storageAccount data and all workspace data · London, United Kingdom
- UpstashJob queues, short-lived cache and live updatesShort-lived copies of workspace data while jobs run · Global (replicated across regions)
- ResendSends email: sign-in and invite mail, replies and campaignsRecipients, subjects and message content · Ireland (EU)
- AnthropicAI models behind Pal (reading, drafting, proposing)The text and files Pal reads to do a task · United States
- CloudflareDNS and the captcha (Turnstile) on sign-in formsIP address and browser signals during the captcha · Global edge network
- Google WorkspaceOur own mailbox for support and correspondenceWhat you email us · Global
Not in use yet
The code can also use OpenAI (speech-to-text for recorded video) and fal (generated images and video). Neither is switched on in production. Before either is, it will be listed above with 30 days' notice, as the DPA requires.
Services you connect yourself
When your team connects an account to its workspace (Stripe, Meta, Google Search Console, or your own database), that service is yours, under your own agreement with it. SuperHQ reads from it on your instruction. Those providers are not our subprocessors.
Changes
We give at least 30 days' notice before adding or replacing a subprocessor. To get notice by email, or to object to a change, write to hello@superhq.app.