Legal
Subprocessors
AnswerTide uses these processors. Last updated 4 October 2026.
“In use” means the provider processes data in production today. “Planned” means the connection is built but switched off: no customer data reaches that provider until it is switched on, and for an integration, until you connect your own account. We update this page before a planned provider is switched on.
Subprocessors
| Provider | Purpose | Data | Region | Status |
|---|---|---|---|---|
| Fly.io | Application hosting | All service data in transit and in memory | United States | In use |
| Supabase | Postgres, Auth, pgvector | Account data, indexed content, conversations, handoff transcripts | United States | In use |
| Anthropic | Answer generation, and the AI Answer Check comparison in a Docs Answer Audit (inference only) | Visitor questions and retrieved excerpts of your content; for an audit, the AI Answer Check answers and excerpts of the audited public pages | United States | In use |
| Voyage AI | Embeddings and rerank | Your indexed content and visitor questions | United States | In use |
| OpenAI | Browser voice (Talk) speech sessions, only when a customer turns voice on; the AI Answer Check in a Docs Answer Audit (inference only) | Visitor voice audio and its transcript, and the cited answer text AnswerTide sends to the session; for an audit, fixed questions naming the audited domain (no page text, email or personal data) | United States | In use |
| Cloudflare | Connection setup (STUN) for browser voice, only when a customer turns voice on | The visitor's network address while the voice connection is set up; no audio, text or account data | Global network | In use |
| Stripe | Payments and Customer Portal | Billing contact and payment details | United States | In use |
| Resend | Transactional email, when configured | Recipient email addresses and message content, including handoff transcripts | United States | In use |
| Resend (inbound email) | Receiving email for the Inbox agent, and sending its replies from a business's own domain | Emails your customers send to your forwarding address, and the replies sent back | United States | Planned |
| Twilio | Phone numbers, inbound calls and voicemail for the Receptionist | Caller phone numbers, call details, voicemail audio and its transcript | United States | Planned |
OpenAI processes data under its own Data Processing Addendum and publishes its own subprocessor list. Browser voice is off until a customer turns it on; text chat does not use OpenAI.
The AI Answer Check in a Docs Answer Audit asks OpenAI a fixed set of questions that name the audited domain, through the API with storage off. No page text, email address or other personal data is sent. Anthropic compares those answers with the audited public pages. Both are inference only.
The AI voice for phone calls is not built yet. Its provider will be listed here before it processes any call.
Integrations you connect
These providers send or receive data only when you connect your own account with them, and the data goes to or comes from that account.
| Provider | Purpose | Data | Region | Status |
|---|---|---|---|---|
| HubSpot | CRM: contacts, notes and deals for leads | Lead name, email, phone and company, a conversation or booking note, quote amounts | Your HubSpot account | Planned |
| Zendesk | Helpdesk tickets for handoffs, and ticket status and notes read back | Visitor email, the question, the transcript, pages visited and cited sources | Your Zendesk account | Planned |
| Freshdesk | Helpdesk tickets for handoffs | Visitor email, the question, the transcript, pages visited and cited sources | Your Freshdesk account | Planned |
| Help Scout | Helpdesk tickets for handoffs | Visitor email, the question, the transcript, pages visited and cited sources | Your Help Scout account | Planned |
| Intercom | Helpdesk tickets for handoffs | Visitor email, the question, the transcript, pages visited and cited sources | Your Intercom account | Planned |
| Slack (app) | Handoff messages in your workspace, and your team's replies in the thread | The visitor's question, email and transcript; your team's replies | Your Slack workspace | Planned |
| Notion | Knowledge source: pages you pick are imported (read only) | The text of the pages you pick | Your Notion workspace | Planned |
| GitHub | Knowledge source: public repositories you pick are imported (read only) | The text of the files you pick | Your GitHub account | Planned |
| Google Docs as a knowledge source (read only), and Google Calendar for booking | The text of the documents you pick; your calendar's free and busy times, and the events booked, with the visitor's name and email | Your Google account | Planned | |
| Microsoft | Outlook calendar for booking, through Microsoft Graph | Your calendar's free and busy times, and the events booked, with the visitor's name and email | Your Microsoft account | Planned |
| Calendly | Booking through your Calendly page, and bookings read back | Invitee name and email and the event booked | Your Calendly account | Planned |
| Shopify | Store app that adds the assistant to your store | Your store's address and an access token; the app writes only the assistant's public key and reads no customer data | Your Shopify store | Planned |
| Zapier | Sends the events you subscribe a Zap to | Leads, handoffs with their transcript, bookings and unanswered questions you subscribe to | Your Zapier account | Planned |
A customer-configured Slack webhook delivers a handoff to that customer's workspace. Slack is not our subprocessor in that case. We do not list Sentry — it is not in the production stack.
Related: DPA · Privacy · Trust and security