Sub-processors
The third parties that process data on Ivy's behalf, what each does, and what it sees.
Last updated 9 September 2026
1.How to read this
Ivy is assembled from a small number of providers. For each one below: what it does for Ivy, what data reaches it, and when. “Connected” providers (Google, Slack) only see an office’s data if that office connected them; the rest are part of running the service. We will give workspace administrators at least 30 days’ notice before adding a provider that processes office content.
2.Current list
| Provider | Purpose | Data touched | When |
|---|---|---|---|
| Anthropic | Model inference — the language model that reads a request and writes the answer. | Message content, the contents of connected data fetched for that request, tool inputs and outputs. | Every question and every scheduled routine. |
| Exa | Web search. | The search query Ivy composes. Not the conversation. | When a request needs the open web. |
| Google Workspace APIs | Mail, Docs, Sheets, Drive and Calendar, as connected by the office. | Whatever the connected account can see and Ivy is asked to read or write: mail, documents, spreadsheets, files, events. | When the office has connected Google and a request uses it. Ivy's own mailbox also receives mail here. |
| Slack | Chat surface in connected workspaces. | Messages in channels and threads where Ivy is mentioned or messaged, and what it posts back. | When the office has connected a Slack workspace. |
| Vercel | Hosting, serverless functions and their logs, durable workflow state, and Sandbox microVMs for coding jobs. | All application traffic in transit; function logs (identifiers, counts, error text); code and files a coding job works on. | Always (hosting); coding jobs only when an office starts one. |
| Supabase | Postgres database and Vault. | Everything Ivy stores: accounts, conversations, inbound mail, audit records, usage, memory pointers. Connected-tool credentials in Vault. | Always. |
| Clerk | Identity — sign-in, organizations and roles. | Name, work email, organization membership, session. | Every sign-in and every authenticated request. |
| PostHog | Product analytics — which pages and features are used, so we can improve them. | User id and work email, pages visited, clicks and feature events, and browser errors. Not message content, documents or connected-tool data. | While you use the web app. |
3.What is not on this list
Tools an office connects beyond Google and Slack — a CRM, a data room, a portfolio system reached over MCP — are chosen by that office and act under its own agreement with that vendor. Ivy passes them only what a request needs. They are listed in the workspace’s own Connections page rather than here.
4.Questions
[Contact email]. Regions and transfer mechanisms per provider: [to be confirmed by legal].