1.Always in the path
Every workspace uses these. There is no configuration in which a customer’s data avoids them.
| Provider | Purpose | What it receives |
|---|---|---|
| Neon | Managed Postgres — the primary database | All application data: workspaces, assistants, conversations, contacts, knowledge sources. |
| Oracle Cloud Infrastructure | Compute for the API and background workers | Everything in transit through the API, processed in memory. |
| Vercel | Hosting for this site and the dashboard | Request metadata for the web surfaces. No conversation content. |
| Cloudflare R2 | Object storage | Uploaded knowledge documents and generated exports. |
| Cloudflare Turnstile | Bot protection on the public chat endpoint | A challenge token and the visitor's IP address at the moment of the challenge. |
| Groq | The default model that generates answers | The retrieved passages and the conversation turn being answered. |
| Anthropic | Fallback and premium models | The retrieved passages and the conversation turn being answered. |
| Resend | Transactional email — sign-in, password reset, notifications | Recipient address and the message body. |
| Brevo | Marketing email, if you opt in | Your account email address. No conversation content. |
| Dodo Payments | Payments, as merchant of record — they remit your sales tax and VAT | Billing details. Card data goes to them directly and never reaches our servers. |
2.Only if you connect them
These receive data only when you connect the matching integration, and only what that integration needs. Disconnecting one stops the flow and affects nothing else.
| Provider | Purpose | What it receives |
|---|---|---|
| Calendar availability and bookings, Sheets as a lead destination, and sign-in | Free/busy times and created events; appended lead rows. | |
| Microsoft | Outlook and Microsoft 365 calendar availability and bookings | Free/busy times and created events. |
| Calendly | Reading scheduled events | Scheduled event details. Read-only. |
| HubSpot | Contacts and activity logging | Lead contact details and a log of what was asked. |
| Slack | Posting leads into a channel | The lead and the conversation transcript. |
| Telegram | Lead and handover alerts to the chat you connect | The alert itself: the lead's name, contact details and what they asked. |
| Meta (WhatsApp Business) | Lead and handover alerts to the number you connect | The alert itself, and the number it is sent to. |
3.The one to read twice
Model providers receive content on every answered message
Answering a question requires sending the visitor’s message and the retrieved passages from your content to a model provider. It happens on every answered message and it is inherent to the product rather than a setting.
What they may and may not do with it is in the AI transparency statement, and clause 6 of the DPA states it as a contractual term.
4.Changes to this list
We give at least 30 days’ notice by email before adding or replacing a subprocessor. If you reasonably object on data protection grounds within that period, tell us and we will work with you to find an alternative — and if we cannot, you may terminate the affected part of the service and receive a pro-rata refund.
This page forms Annex III to the Standard Contractual Clauses incorporated into the DPA. Last reviewed 2026-09-10.