TL;DR. SlackBridge's sub-processors are listed on its Sub-Processors page: Cloudflare, Microsoft, Slack, Stripe, Resend, Google, Sentry, PostHog and TypeSafe. Bridged messages are relayed by SlackBridge's own code and are never passed to an AI model. AI is used in one place visitors see: the help-page assistant, which finds passages in the help articles using Cloudflare Workers AI and checks them with TypeSafe, and shows them word for word. A support-inbox step that drafts replies for a person to review exists in the code but is switched off.
The short version
- Bridged messages never go through an AI model. Messages between Slack and Microsoft Teams are relayed by SlackBridge's own code. None of the code that relays messages, matches thread replies, resolves mentions or converts emoji calls an AI model.
- The help-page assistant uses AI to find and check passages, not to write. A question typed into "Search our help articles" on the help page is processed by Cloudflare Workers AI to find matching passages, and by TypeSafe to check that a passage answers it. The assistant shows help-article text word for word and does not write answers. The question is not stored unless you ask a person to follow up.
- Elsewhere on the website and dashboard: no AI model processes visitor data. Visitor analytics go to PostHog, which is listed as a sub-processor.
- Sub-processors: the authoritative list is the Sub-Processors page. It names nine companies, summarized below.
- Support inbox: AI drafting is switched off. SlackBridge has a step that can draft replies to emails sent to support@slackbridge.com for a person to review. It is off; what it would receive is described below.
Who are SlackBridge's sub-processors?
This is a summary of the Sub-Processors page, last updated October 5, 2026. The page itself is the reference for a vendor review or data-processing addendum: it says exactly what data each company processes and where.
| Company | What it does for SlackBridge | Location |
|---|---|---|
| Cloudflare, Inc. | Hosting (Workers) and key-value storage: configuration, encrypted OAuth tokens, short-lived message routing metadata, cached display names and avatars, mention member lists, usage metrics | United States (global edge network) |
| Microsoft Corporation | Microsoft Teams integration: message relay and sign-in | United States |
| Slack Technologies, LLC | Slack integration: message relay, channel management and sign-in | United States |
| Stripe, Inc. | Payments and subscriptions | United States |
| Resend, Inc. | Transactional email (account notifications and invitations) | United States |
| Google LLC | Google Workspace: SlackBridge's business email, including customer correspondence | United States |
| Functional Software, Inc. (Sentry) | Error monitoring for the SlackBridge API | United States |
| PostHog, Inc. | Product analytics, including session recordings and heatmaps where a visitor has accepted analytics (or by default outside the UK, EU/EEA and Switzerland) | United States |
| TypeSafe AI, Inc. | Answer checking for the help-page assistant: receives the question as typed and the public help-article passages it is compared with | United States |
Message text passes through Slack, Microsoft and Cloudflare while it is relayed, but SlackBridge does not store it. See How long does SlackBridge store my messages and data? for every retention window.
The Sub-Processors page states: "We will notify customers of any material changes to our sub-processors that may affect the processing of their data." Questions about sub-processors go to privacy@slackbridge.com. To request a data-processing addendum or other compliance documents, email support@slackbridge.com.
Does SlackBridge use AI on our messages?
No. A message posted in a bridged channel is received by SlackBridge, translated from one platform's format to the other's, and posted on the other side. Thread replies are matched using stored message IDs, mentions using a member list, and emoji using a fixed conversion table. No step in that path sends the message, or anything about it, to an AI model.
Where SlackBridge uses AI: the help-page assistant
The "Search our help articles" box on the help page is an automated assistant. When you type a question:
- Cloudflare Workers AI turns the question into a numeric representation and finds the closest passages in the help articles.
- TypeSafe checks whether each of the closest passages actually answers the question. Only passages it confirms are shown. If TypeSafe is unavailable, the assistant shows only very close matches instead.
- The passages are shown word for word, each with a link to its article. Nothing is written by a model.
The question is not stored by SlackBridge and is not written to its logs. TypeSafe receives the question exactly as typed, including anything you put in it; please don't include personal details. SlackBridge does not send TypeSafe your contact-form email address, your IP address or any account data. If you choose "Talk to a person", your email address and message are stored as a support request and deleted after 90 days. The Privacy Policy has the details.
The support inbox: AI drafting is switched off
Emails sent to support@slackbridge.com become support tickets that a person answers. SlackBridge's code includes a drafting step that could suggest replies to tickets for a person to review. It is switched off: it runs only if SlackBridge turns it on in its configuration and has an Anthropic API key, and neither is the case. Before it is ever switched on, Anthropic will be added to the Sub-Processors page.
If it were switched on, the step is designed in tiers:
- Sorting and simple drafts: Cloudflare Workers AI, using Meta's Llama 3.3 70B model, sorts the email by topic and drafts an answer to a straightforward question.
- Similar past tickets: Cloudflare Workers AI embeddings and Cloudflare Vectorize look up summaries of similar resolved tickets.
- Complex questions: Anthropic's Claude (Claude Haiku 4.5) is asked for a diagnosis and a draft reply.
The Claude step would receive:
- the email's subject line and up to the first 3,000 characters of its body;
- a summary of the SlackBridge account whose admin email address shares the sender's email domain, if there is one: organization and Slack workspace names, plan, connection names and status, linked channel names with their message counts and last-message times, and counts of the account's Microsoft notification subscriptions;
- short summaries of similar past tickets, when any are found.
SlackBridge would not attach the content of bridged messages, because it does not store them; anything a customer pastes into a support email would be part of that email.