Data residency for Slack allows global teams to choose the region where certain types of data at rest are stored. You can contact our Sales team to set up data residency for your organization. Before you get started, here's what you should know:
We currently offer data storage in Frankfurt, Germany.
Customers must store all Slack data in a single region.
Customer data stored in Frankfurt is backed up in Paris, France.
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. Logs (sanitized logs)
IDs generated by Slack on behalf of the customer (UID, EID, TID)
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.