Respond.io Subprocessors List (November 2026): Changes and History
Respond.io names 18 subprocessors on its published list. Read from the vendor's own page and re-checked daily.
Named rows include AWS, Segment, and SendGrid. We keep Respond.io's privacy policy, terms of service, and trust page on file.
Respond.io subprocessors (November 2026)
| # | Subprocessor | Purpose | Location |
|---|---|---|---|
| 1 | AWS | Infrastructure; Cloud infrastructure and hosting | — |
| 2 | Segment | Platform; Customer data pipeline / event tracking | — |
| 3 | SendGrid | Platform; Transactional and marketing email delivery | — |
| 4 | Pendo | Platform; Product usage analytics and in-app guidance | — |
| 5 | Apify | Platform; Web crawling to ingest customer-specified URLs into knowledge sources | — |
| 6 | Telnyx | Platform; VoIP telephony infrastructure and call recording for the Voice channel | — |
| 7 | Snowflake | Data Analytics & Warehouse; Data warehousing and analytics | — |
| 8 | OpenAI | AI Services; AI language model inference for AI Agent and AI Assist features | — |
| 9 | Mistral AI | AI Services; AI language model inference for AI Agent features; OCR processing of PDFs and images in knowledge sources | — |
| 10 | Google Cloud / Vertex AI | AI Services; Vector embedding generation for knowledge source retrieval and translations | — |
| 11 | LangSmith (LangChain) | AI Services; AI observability and tracing of model interactions | — |
| 12 | ElevenLabs | AI Services; Voice processing for AI-powered voice conversations (text-to-speech and speech-to-text) | — |
| 13 | PostHog | Platform; Tracing, monitoring and debugging | — |
| 14 | Rocketbots Malaysia Sdn. Bhd. | Business Operations; Administrative and support access | — |
| 15 | Nango | Platform; Third-party services integration | — |
| 16 | OneSignal | Platform; Push notification delivery to the respond.io mobile apps and web browser | — |
| 17 | Sentry | Platform; Error monitoring and mobile session capture; session replay can capture inbox screens showing conversation content | — |
| 18 | Meta Platforms | Communication Channels; WhatsApp | — |
Get an email when Respond.io changes its subprocessors
ClauseTrail re-checks this list every day and tells you exactly who was added or removed — including when a vendor starts sending data to an AI provider. The first vendors are free.
AI and customer data at Respond.io
What Respond.io's own documents say, with the sentence each answer comes from.
- Trains AI models on customer data
-
No
“We do not use customer content, including message content and conversation history submitted to the platform, to train, develop or improve generalised or foundational artificial intelligence or machine learning models.”
Privacy policy, respond.io ↗ - Sends customer data to AI model providers
-
Yes: OpenAI
“For example, if the user connects Respond.io to ChatGPT, information returned through the connection is provided to OpenAI.”
Privacy policy, respond.io ↗ - How to opt out
-
An MCP connection allowing AI assistants to access a Workspace is only available if a Workspace administrator enables it, and users can disconnect or revoke access at any time.
“An MCP connection can only be established where a Workspace Owner has enabled the connection for that Workspace.”
Privacy policy, respond.io ↗ - How long AI features keep data
-
Information disclosed to an AI assistant provider is subject to that provider's own retention and deletion practices, not Respond.io's.
“Information already disclosed to an AI assistant is subject to that provider's retention and deletion practices.”
Privacy policy, respond.io ↗
Certifications at Respond.io
What Respond.io's trust page lists, with the text each one comes from.
- ISO 27001
-
Active
“ISO 27001”
Trust page, respond.io ↗
Documents we track for Respond.io
- Privacy policy
- checked November 17, 2026 changed November 17, 2026 respond.io ↗
- Subprocessor list
- checked November 17, 2026 respond.io ↗
- Terms of service
- checked November 17, 2026 changed November 17, 2026 respond.io ↗
- Trust page
- checked November 17, 2026 respond.io ↗
Change history
-
September 30, 2026 – November 7, 2026 12 minor wording edits (Privacy policy, Terms of service) Show Reworded without changing what the documents say.
-
Privacy policy changed
Only a hidden timestamp field at the end of the document changed from 2026-11-03T22:59:27.695Z to 2026-11-06T10:53:56.886Z, with no changes to the policy text itself.
-
Privacy policy changed
Only an automatically generated timestamp at the bottom of the page changed, from 2026-10-30T10:19:09.223Z to 2026-11-02T11:37:54.064Z.
-
Privacy policy changed
A timestamp at the end of the document updated from 2026-10-30T01:47:01.769Z to 2026-10-30T10:19:09.223Z, with no other textual change.
-
Privacy policy changed
Only an internal timestamp at the bottom of the page changed from 2026-10-15T08:01:22.496Z to 2026-10-16T03:39:42.745Z, with no changes to the policy text itself.
-
Privacy policy changed
Only an internal timestamp line at the end of the privacy policy changed, from 2026-10-14T00:59:38.016Z to 2026-10-15T08:01:22.496Z.
-
Terms of service changed
A machine-readable timestamp at the bottom of the Terms of Service page changed from 2026-10-09T10:25:52.724Z to 2026-10-14T00:59:39.119Z; the document text itself, including the 'Last updated: January 20, 2025' date, is unchanged.
-
Privacy policy changed
Only a hidden timestamp field at the bottom of the privacy policy page changed from 2026-10-09T10:25:51.211Z to 2026-10-14T00:59:38.016Z, with no change to the policy text itself.
-
Terms of service changed
A page-generation timestamp at the bottom of the Terms of Service changed from 2026-10-08T01:14:52.081Z to 2026-10-09T10:25:52.724Z; the actual terms text, last updated January 20, 2025, is unchanged.
-
Privacy policy changed
Only an automated timestamp at the bottom of the document changed, from 2026-10-05T04:10:24.395Z to 2026-10-08T01:14:50.867Z.
-
Terms of service changed
Only an internal timestamp at the bottom of the Terms of Service changed, from 2026-09-29T15:53:26.405Z to 2026-10-02T02:23:17.590Z; the 'Last updated: January 20, 2025' date and all substantive text remain unchanged.
-
Privacy policy changed
Only a timestamp string at the bottom of the privacy policy page changed from '2026-09-29T15:53:25.237Z' to '2026-10-02T02:23:16.507Z'; no policy text was altered.
-
Privacy policy changed
Only a hidden timestamp string changed, from 2026-09-28T10:34:23.507Z to 2026-09-29T15:53:25.237Z; the visible 'Latest update: September 2026' text and all policy content remain unchanged.
-
Tracking since September 28, 2026. Every change links to the two versions of the document it came from. All vendors' changes →
Respond.io subprocessors FAQ
- How many subprocessors does Respond.io use?
- Respond.io lists 18 subprocessors on its published list, including AWS, Segment, SendGrid, Pendo, and Apify and 13 more.
- Does Respond.io use customer data to train AI models?
- According to its privacy policy, Respond.io does not use customer data to train AI models: “We do not use customer content, including message content and conversation history submitted to the platform, to train, develop or improve generalised or foundational artificial intelligence or machine learning models.”
- Which AI model providers does Respond.io send customer data to?
- OpenAI is named in Respond.io's privacy policy: “For example, if the user connects Respond.io to ChatGPT, information returned through the connection is provided to OpenAI.”
- Which security certifications does Respond.io list?
- Respond.io's trust page lists ISO 27001.
- When was Respond.io's subprocessor list last checked?
- ClauseTrail last checked Respond.io's subprocessor list on November 17, 2026. Lists are re-checked daily.
- How do I find out when Respond.io adds or removes a subprocessor?
- ClauseTrail monitors Respond.io's subprocessor list, DPA, privacy policy and terms and emails you the exact change — who was added or removed and what the page said before and after. The first vendors are free.