Legal / Sub-processors

Kadence Sub-processors

Last updated: June 22, 2026

We use the third parties below to operate Kadence. We require each to protect data consistent with our Privacy Notice and Data Processing Addendum. We will update this page before adding a new sub-processor that processes Customer Personal Data.

Infrastructure and platform

Sub-processorPurposeData
VercelApplication hosting and computeUsage, logs, request data
NeonManaged Postgres database (United States)Account data and Customer Data at rest
UpstashRate limiting and cachingIP addresses, workspace identifiers

Communications

Sub-processorPurposeData
Microsoft (Microsoft Graph)Sending and syncing outreach email through your connected Outlook mailboxRecipient addresses, email content, message metadata
ResendTransactional and digest email (sign-in links, invitations, briefs)Recipient email addresses, message content

AI providers

Sub-processorPurposeData
AnthropicLarge language model features (drafting, analysis, assistant)Prompt content, which may include prospect data
Google (Gemini)Large language model featuresPrompt content, which may include prospect data

Enrichment (data sources)

Sub-processorPurposeDataNotes
TavilyWeb-search enrichment (news, certifications, contact discovery)Company and person search termsCustomer-provided API key
Google (Places)Local business discoveryBusiness search termsCustomer-provided API key

Some enrichment providers operate only when you connect your own API key. When you do, you are licensing that provider directly and using Kadence to call it on your behalf.

Operations

Sub-processorPurposeData
CloudflareDNS for kadence.haunlab.comDomain and network metadata
TelegramOperational alerts to our team (errors, feedback, health)Limited operational data, which may include excerpts of submitted feedback

Questions about this list: taylor@haunlab.com.

All legal documents