Data residency for Slack
Data residency for Slack allows global teams to choose the region where certain types of data at rest are stored.
Before you get started, here's what you should know:
- Customers must store all Slack data in a single region.
- If you’re using the free version of Slack or the Standard plan, you’ll need to upgrade to the Plus plan first.
- Contact our Sales team to set up data residency for your organization.
Where data residency for Slack is available
In the table below, see where data residency is available and the corresponding backup regions.
|Data residency region||Data backup region|
|Frankfurt, Germany||Paris, France|
|Paris, France||Frankfurt, Germany|
|Tokyo, Japan||Osaka, Japan|
|Sydney, Australia||Sydney, Australia*|
|London, United Kingdom||London, United Kingdom*|
*Slack will replicate data in order to keep the data residency and data backup in the same region.
How data residency for Slack works
The following categories of customer data will be stored at rest in a data center within the Customer’s selected region as of the date data residency is enabled:
- Messages, posts and snippets
- Files (e.g., images, docs, etc.) uploaded to the Service
- Search index of Customer Data
- App- or bot-generated messages and files
Other categories of customer data, such as user profile information and channel names, channel topics and channel descriptions, may be delayed or unavailable for storage in the data residency region.
The following categories of data may be processed and stored in regions outside of the customer’s data region:
- Workspace and channel membership information
- Data used to measure seat count, usage, and revenue
- Data used for analytics and to measure quality of service, e.g. sanitized logs
- IDs generated by Slack on behalf of the customer
If a new workspace or Enterprise Grid org is set up in a data residency region, customer data will be stored in the selected region starting the date the workspace or org is created.
For existing customers wishing to enable data residency, customer data can be migrated to a selected data region at any time. When a workspace or Enterprise Grid's data is migrated, all new user data will start residing in this region. However, old data will continue to live in the United States. Over time, Slack will migrate the data stored in the U.S. to the customer’s selected data region.
If two organizations connected by a shared channel are both in the same data region, all of their customer data will remain in that data region as well. If the organizations are located in different data regions, the following will happen:
- Each organization’s messages will live in their respective data regions.
- The search index for the shared channel will live in both regions.
- If the shared channel is disconnected, both organizations will get a copy of the other party’s previously shared data.
Note: Enterprise Key Management (EKM) is not currently integrated with data residency, but we may offer this capability in the future.
Ready to get started? Contact our Sales team.
- Only the Primary Owner can enable data residency for a workspace or org
- Plus and Enterprise Grid plans