Subprocessors
Last updated October 14, 2026
These are the third-party providers (“subprocessors”) that may process personal data on our behalf to provide tufu. Our Data Processing Addendum explains how we choose them and how we tell you about changes.
Service providers
| Provider | What it does for tufu | Location |
|---|---|---|
| Anthropic, PBC | Generates answers, summaries and suggested replies | United States |
| MongoDB, Inc. (Voyage AI) | Indexes knowledge so answers can find it | United States |
| Railway Corporation | Hosting, database and background jobs | United States |
| Cloudflare, Inc. | Network delivery, protection against attacks and bots (including the sign-up check), and storage of uploaded files | Global |
| Resend (Plus Five Five, Inc.) | Sending emails, and receiving email replies and the support email you forward to tufu | United States |
| Functional Software, Inc. (Sentry) | Error monitoring: details of errors, such as the page involved and which account and team it happened in, without email addresses or IP addresses | United States |
Payments are handled by Stripe, Inc., which receives card details directly and processes them as its own controller under its privacy policy, so it isn't a subprocessor.
Integrations you choose
These receive data only if your team connects them, under your own agreement with them:
- Slack, for handoff cards and threads, answering in your workspace, and Slack as a knowledge source.
- Discord, if you add tufu's Discord app to your server, where the bot posts its answers and your team's replies.
- Google, if you sign in with Google.
- Your own AI provider account (OpenAI, Anthropic, Google, xAI or OpenRouter), if you add your own API key. A bot's answers then go through your account instead of ours.
- Knowledge sources you connect, such as GitHub or Confluence, which we read from.
Changes
We update this page at least 30 days before adding or replacing a subprocessor and tell team admins by email. Questions: .