This provision states that due to the ongoing situation in the Middle East, customer organizations hosted in the UAE are routed to an EU location, trial and Scratch Org sign-ups from several Middle Eastern countries are routed to the EU, and Israeli commercial customer data is temporarily backed up to an EU location pending resolution of the crisis.
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 establishes temporary cross-regional data routing affecting customers in the UAE, Israel, Lebanon, Bahrain, Oman, Jordan, Qatar, Kuwait, and Egypt, creating a situation where Customer Data is processed in the EU regardless of customer location or regional preference, which may interact with both EU GDPR requirements for inbound transfers and the data protection frameworks of the originating jurisdictions.
Interpretive note: The document references 'the ongoing situation in the Middle East' and 'until the crisis has resolved' without specifying conditions or timelines, creating uncertainty about the duration and resolution criteria for this routing provision.
The document states that Customer Data for organizations in affected Middle Eastern jurisdictions is currently routed to EU locations due to the ongoing regional situation. This routing applies to hosted orgs, new trial sign-ups, Scratch Orgs, and commercial org backups depending on the specific country, and is described as temporary for Israeli backup data pending crisis resolution.
Cross-platform context
See how other platforms handle Middle East Data Routing to European Union and similar clauses.
Compare across platforms →"Due to the ongoing situation in the Middle East, orgs hosted in the UAE as well as new trial org sign ups and Scratch Orgs from Lebanon, Bahrain, Oman, Jordan, Qatar, Kuwait, Egypt, or the UAE will be routed to a location in the European Union. In addition, Customer Data of commercial Customer orgs in Israel will be temporarily backed up to a location in the EU until the crisis has resolved.Excerpt from Slack's Sub-Processors (Salesforce)
(1) REGULATORY LANDSCAPE: This provision engages both EU GDPR as the destination jurisdiction's data protection framework and the national data protection laws of UAE, Israel, and other affected countries as originating jurisdictions.
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 establishes temporary cross-regional data routing affecting customers in the UAE, Israel, Lebanon, Bahrain, Oman, Jordan, Qatar, Kuwait, and Egypt, creating a situation where Customer Data is processed in the EU regardless of customer location or regional preference, which may interact with both EU GDPR requirements for inbound transfers and the data protection frameworks of the originating jurisdictions.
The document states that Customer Data for organizations in affected Middle Eastern jurisdictions is currently routed to EU locations due to the ongoing regional situation. This routing applies to hosted orgs, new trial sign-ups, Scratch Orgs, and commercial org backups depending on the specific country, and is described as temporary for Israeli backup data pending crisis resolution.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Slack.