A subprocessor is another processor engaged to process personal data on behalf of a processor. Search reviewed disclosures and inspect changes between comparable published versions.
Published lists and source-version changes
Company records retain their individual review dates. The Intercom version pair was rechecked on 2026-10-15; it covers one complete, explicitly bounded source section.
Intercom: 2025-04-09 → 2026-06-25
Default US-hosted service subprocessors. These are publisher version dates, not verified edit or adoption dates.
Two publisher-provided versions rechecked: effective 2025-04-09 and 2026-06-25. Publication dates and actual adoption dates are not established. Next editorial review due . This edition records what was checked on the review date; it does not promise current contract status. If the review is overdue, use the linked primary sources to recheck before acting.
11 providers in the earlier version; 14 in the later version. The comparison finds 3 disclosure additions, 0 removals and 11 retained providers. These are source-version differences, not monthly buying events.
Full audit table, unaffected by the AI filter above. Normalized default US section; regional and affiliate lists excluded.
Provider
Version result
Processing purpose
Location: earlier → later
Amazon Web Services, Inc.
Retained
Hosting, storage and processing, including AI
USA → USA
Snowflake Inc.
Retained
Data warehousing and processing, including AI
USA → USA
Mailgun Technologies, L.L.C.
Retained
Email delivery
USA → USA
Message Systems, Inc. (d/b/a Sparkpost)
Retained
Email delivery
USA → USA
Twilio, Inc.
Retained
SMS and phone
USA → USA
Cloudflare, Inc.
Retained
TLS for custom help-center domains
USA → USA
OpenAI, L.L.C.
Retained
AI processing
USA → USA
PlanetScale Inc.
Retained
Database storage and caching
USA → USA
Anthropic, PBC
Retained
AI processing
USA → USA
Google L.L.C.
Retained
AI processing
USA → USA
Microsoft Corporation
Retained
AI processing
USA → USA
Eleven Labs, Inc.
Added to disclosure
Text-to-speech AI
Not listed → USA
Ably Realtime Ltd.
Added to disclosure
Real-time messenger delivery
Not listed → USA
Cartesia AI, Inc.
Added to disclosure
Text-to-speech AI
Not listed → USA
Across the 11 retained providers, normalized purposes and USA processing locations are unchanged in this scope. This does not cover the separate EU or Australia sections.
Textual changes are separate
Mailgun: Mailgun Technologies, LLC → Mailgun Technologies, L.L.C.. Legal-name punctuation only; not a new provider.
Google: Google LLC → Google L.L.C.. Legal-name punctuation only; not a new provider.
Version effective dates bound this document comparison. They do not date the purchase, first production use or exact edit. There is no verified switch or churn in this report.
A subprocessor relationship concerns processing performed for another processor. A published list can identify providers, processing purposes, and locations. Not every commercial vendor or integration is necessarily a subprocessor for the service in question.
GDPR Article 28 context
Article 28 addresses the conditions for engaging another processor, including authorization and contractual obligations. Read the applicable agreement and the regulation together; a public list alone does not establish that all contractual requirements have been met.
How to read the tracker
The review date tells you when we checked a source. A version’s effective date is supplied by the publisher. The tracker compares a defined scope, normalizes provider names, and shows additions and removals only when both versions cover that same scope.
The archived Intercom pair covers the default US-hosted service list. Other company rows are reviewed subsets without a historical pair. “History unavailable” does not mean the source has never changed.
A public job board supports an ATS observation. A subprocessor disclosure identifies a provider that may process data for particular services. A vendor customer story describes a published relationship. These sources have different scopes and are labeled separately.
Counts cover the records on these pages, not the whole market. No observation in our covered sources does not mean a company does not use a vendor. Source recency and unresolved conflicts affect confidence; observations do not establish spend, renewal timing, or customer churn.