Data residency for Slack

Data residency for Slack allows global teams to choose the region where certain types of data at rest are stored.

Here's what you need to know about data residency:

Note: The data residency feature does not change any aspects of Slack other than the data storage location. Slack will continue to store and process all other categories of data in accordance with your written agreement for Slack Services and Slack’s Privacy Policy.

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*
Montreal, Canada Montreal, Canada*

*Slack will replicate data in order to keep the data residency and data backup in the same region.

How data residency for Slack works

Customer data

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 (ex., images, docs, etc.) uploaded to the Slack Service
  • Search index of Customer Data
  • App- or bot-generated messages and files

Other categories of customer data such as user profile information, channel names, channel topics, and channel descriptions may be delayed or unavailable for storage in the data residency region.

Other data

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, ex. sanitized logs
  • IDs generated by Slack on behalf of the customer

Data migration

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.

Shared channels

If external organizations connected by a shared channel are in the same data region, all of their customer data will remain in that data region as well. If 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 each organization's region.
  • If the channel stops being shared, each organization will get a copy of the other party's previously shared data.

Enterprise Key Management

New Enterprise Key Management (EKM) customers can choose to create and store their encryption keys in a specific data region with data residency. Existing EKM customers are not able to store their encryption keys in specific data regions at this time, but we may offer this capability in the future.

Ready to get started? Contact our Sales team.

Who can use this feature?
  • Only the Primary Owner can enable data residency for a workspace or org
  • Plus and Enterprise Grid plans