The subprocessors we use to deliver Hey Support.

We list every third-party service that touches customer data. When we add, change, or remove a subprocessor, this page updates. You'll find the same list referenced in our Privacy Policy and our DPA.

Last updated · August 24, 2026
Current subprocessors

Eight third parties. Nothing else.

Scroll to read full table →
SubprocessorPurposeData processedLocation
Vercel Inc.Application hosting, edge network, serverless compute, and cookieless marketing-site analyticsAll customer data in transit. The analytics covers hey.support visitors only — aggregate page views and page-load speed, with no cookie or cross-session identifier, and never the chat widget or the appUnited States
Supabase Inc.Managed Postgres, pgvector, authentication, storageAll customer data at rest, including knowledge base contentUnited States
OpenAI, L.L.C.Large language model inference and text embeddings via APIVisitor messages, retrieved knowledge chunks for response generationUnited States
Cartesia AI Inc.Voice synthesis (text-to-speech) and transcription (speech-to-text)Audio streams for voice conversations onlyUnited States
Stripe, Inc.Subscription billing, payments, customer portalBilling identifiers, no chat or knowledge dataUnited States
Razorpay Software Private LimitedSubscription billing and payments for customers in India (UPI AutoPay)Billing identifiers, no chat or knowledge dataIndia
Resend Inc.Transactional email deliveryEmail addresses and message content for invitations, notifications, password resetsUnited States
Functional Software, Inc. (Sentry)Application error monitoringStack traces, route paths, release and runtime metadata for failures only. Request bodies, query strings, cookies and IP addresses are stripped before transmission, so no chat content, knowledge base content, or lead data is sent. No session recordingUnited States
Google LLCMarketing site analytics (Google Analytics 4), loaded only after a visitor opts inMarketing site visitors only: page views, referrer, device, approximate location. No workspace, chat, or knowledge base dataUnited States

We don't use any other subprocessor for customer data processing.

How we vet new subprocessors

Four checks before we add anyone.

Before we add a subprocessor, we check four things:

  • They have a SOC 2 Type II report or equivalent audit on file
  • Their data processing agreement is enforceable in the jurisdictions our customers operate in
  • They commit not to use customer data for model training (where applicable)
  • The data they receive is the minimum needed for the function they perform

If any of those fail, we don't add them.

Cookies and analytics on the marketing site

Only after you opt in.

We use Google Analytics 4 on the marketing site, and it loads only after you accept analytics cookies in the consent banner. Advertising and personalization signals stay switched off unless you also accept marketing cookies. No Facebook Pixel, no Google Ads tracking. The marketing site is separate from your workspace and visitor data, and the analytics tag never runs inside the chat widget on your site.

Notifications of changes

Thirty days. By email if you want it.

When we add or change a subprocessor, we update this page at least thirty days before the change takes effect for paying customers. Enterprise customers receive a direct email at the contact on file.

You can subscribe to changes by emailing [email protected] with the subject “Subprocessor notifications.”

If you object to a new subprocessor, contact us. We'll work with you on an alternative or a transition plan.

Contact

Questions land here.

For questions about this list, our processing, or anything related: [email protected]