This provision establishes that enabling specific product features, including Einstein and Agentforce capabilities, triggers the activation of additional infrastructure providers and sub-processors beyond those used for the base service, with Customer Data processed by those additional entities and locations as a consequence of feature enablement.
This analysis describes what Slack's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision creates a direct operational link between feature configuration decisions and sub-processor inventory: enabling Einstein NLP, generative AI, speech, or analytics features introduces additional sub-processors including AWS, Microsoft Azure, OpenAI, Deepgram, LiveKit, and Eleven Labs across multiple jurisdictions, requiring that organizations maintain a dynamic sub-processor map that reflects their current feature configuration.
Under this clause, the set of sub-processors processing Customer Data is not static but expands as additional features are enabled within covered services. The document states that if these features are enabled, Customer Data will be processed by the additional infrastructures, making feature activation decisions a direct determinant of the applicable sub-processor chain.
Cross-platform context
See how other platforms handle Feature-Triggered Sub-processor Activation and Cross-Regional Data Flows and similar clauses.
Compare across platforms →"Some Services run primarily on one infrastructure, but have some features that run partly or entirely on different infrastructures. For example, for many Customers, most Sales Cloud features run on the Salesforce's first-party infrastructure, but Sales Cloud also includes Einstein1 Features that run on the Einstein Platform infrastructure. Similarly, the Marketing Cloud Engagement Services are based primarily on the Marketing Cloud Engagement infrastructure, but some features of Marketing Cloud run partially on Einstein Platform or Marketing Cloud Einstein infrastructure. If these features are enabled, Customer Data will be processed by these additional infrastructures.Excerpt from Slack's Sub-Processors (Salesforce)
(1) REGULATORY LANDSCAPE: This provision implicates GDPR Article 28 sub-processing authorization obligations and Article 30 records of processing activities requirements, as the sub-processor chain is variable based on feature configuration rather than fixed at contract …
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision creates a direct operational link between feature configuration decisions and sub-processor inventory: enabling Einstein NLP, generative AI, speech, or analytics features introduces additional sub-processors including AWS, Microsoft Azure, OpenAI, Deepgram, LiveKit, and Eleven Labs across multiple jurisdictions, requiring that organizations maintain a dynamic sub-processor map that reflects their current feature configuration.
Under this clause, the set of sub-processors processing Customer Data is not static but expands as additional features are enabled within covered services. The document states that if these features are enabled, Customer Data will be processed by the additional infrastructures, making feature activation decisions a direct determinant of the applicable sub-processor chain.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Slack.