Subprocessors

Effective date: July 21, 2026

This page lists third-party providers that Dualhook uses to provide the service, plus customer-selected integrations that are not treated as Dualhook subprocessors in the standard Webhook Override flow. It is incorporated by reference into the Data Processing Addendum.

1. Subprocessor Notice

Dualhook will provide at least 30 days' notice before adding or replacing a subprocessor, unless urgent security, availability, legal, or provider-continuity needs require a shorter period. Objections can be sent to contact@dualhook.com.

Provider legal pages and account terms can change. The database is hosted in Ireland (AWS eu-west-1), application functions run in Dublin, Ireland, and the outbound relay runs on Cloudflare's global network without storing message bodies.

2. Current Subprocessors

ProviderPurposeData categoriesLocation / transfer notesProvider materials
ClerkAuthentication, organization membership, user sessions, and account emails.Account identifiers, organization identifiers, email addresses, authentication metadata, and session data.

Provider infrastructure and subprocessors as described in Clerk's public legal materials.

Provider DPA and transfer terms, including applicable safeguards described by Clerk.

StripeCheckout, subscription billing, invoicing, tax/VAT records, and payment notices.Billing profile data, payment and subscription metadata, invoices, tax IDs, and payment status.

Provider infrastructure and subprocessors as described in Stripe's public legal materials.

Stripe DPA and service-provider terms, including applicable transfer safeguards.

VercelApplication hosting, serverless functions, cron jobs, and private Blob storage.Application traffic metadata, logs needed to operate the service, support attachment blobs, and hosted application data.

Serverless functions run in Dublin, Ireland; the edge network is global. Dualhook does not claim exclusive EU-region hosting.

Vercel DPA and subprocessors, including applicable transfer safeguards.

CloudflareOutbound WhatsApp runtime relay, TLS termination, request rate limiting, and network protection.Outbound message payloads and requested media in transit, connection-scoped credential hashes, and content-free operational request metadata. Message and media bodies are not persisted or cached by Dualhook.

Cloudflare's global network and subprocessors as described in its public legal materials. Dualhook configures the runtime relay with cache bypass and no-store response headers.

Cloudflare DPA and data-localization terms, including applicable transfer safeguards.

Turso / libSQLManaged database hosting for Dualhook application data.Account, organization, connection configuration, billing metadata mirrors, webhook metadata, health checks, email logs, and support metadata.

AWS eu-west-1 (Ireland).

Turso DPA and subprocessors, including applicable transfer safeguards.

PostHogPrivacy-focused website and product analytics (cookieless).Page views, named button clicks, basic session/device metadata, and a small set of server-side product events keyed by a pseudonymous organization ID. No cookies or device storage; no session replay.

PostHog EU Cloud (Frankfurt, Germany). Dualhook does not send names, email addresses, phone numbers, or WhatsApp message content to PostHog.

PostHog DPA and privacy terms; EU-hosted project with IP capture disabled.

ResendTransactional and administrative email delivery.Recipient email addresses, message content, delivery metadata, and related email logs.

Provider infrastructure and subprocessors as described in Resend's public legal materials.

Resend DPA and subprocessor terms, including applicable transfer safeguards.

3. Customer-Selected Integrations

Meta / WhatsApp Graph API

Customer-selected platform integration used to configure WhatsApp Business assets, route inbound message-path webhooks, and receive outbound relay requests.

Inbound message-path webhooks route directly from Meta to the customer endpoint. Outbound payloads and requested media transit Dualhook's allowlisted runtime relay to Meta without content persistence. Customers choose and control their WhatsApp Business Account, Meta assets, end-user notices, opt-ins, and downstream message handling.