Data Residency for Asana

Data residency for Asana allows global teams to choose the region where certain types of data at rest are stored. Data Residency, coupled with Asana’s Privacy Commitment ensures your data is stored and used only in the ways our customers require.

Who can use this feature?

Data residency is available to be purchased as an add-on in Enterprise organizations and is included in Enterprise+ tiers. Super admins can enable data residency for an organization. 

What you need to know about data residency:

  • Customers must store all Asana data in a single region
  • For data residency access, paid plan customers must upgrade to an Enterprise organization plan or Enterprise+.
  • Contact our Sales team to set up data residency for your organization. 

Where data residency for Asana is available

Asana partners with Amazon Web Services to deliver in-region storage with high reliability and performance. With access to a regional data center, customers can more easily adhere to both internal data policies as well as evolving government and third-party regulations favoring data residency requirements.    

Check out the table below, to see where data residency is available and the corresponding backup regions.

Data residency region Data backup region
Virginia, United States (default) Ohio, United States (default)
Frankfurt, Germany Dublin,  Ireland
Tokyo, Japan Osaka, Japan
Sydney, Australia  Dublin, Ireland

How data residency for Asana works 

Data stored in the data region

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:

  • Customer data: including teams, projects, tasks, domain & CSV exports, and attachments. 
  • User-generated content included in a user's first project 
  • User profile data: user name, profile photo, and locale

Data stored outside the data region

The following categories of data may be stored outside of the customer’s data region:

  • User authentication: e-mail addresses, passwords (guests), one-time keys (e.g. password reset links, signup/invite links), IP addresses, random identifier 
  • Data used to measure seat count, usage, and revenue

Note: The data residency feature does not change any aspects of Asana other than the data at rest storage location in Amazon Web Services. Asana will continue to store and process all categories of data in the United States and other international locations in accordance with Asana's Privacy Statement, and where applicable, the Data Processing Addendum entered into with Asana. For more information on where information is stored and processed via our subprocessors or Asana affiliates, please see our Subprocessors and Affiliate page.

Data migration

By default, data will continue to reside in the United States for new workspaces and existing customer data. Customers must contact our Sales team to opt-in for data residency to migrate their organization to their selected data region. 

How does Asana approach privacy and security? 

Asana adheres to global privacy laws and security standards. For more information about Trust at Asana please click here. Customer data is encrypted at rest and in transit, and protected with cross-regional backups.

Enterprise Key Management

New and existing Enterprise Key Management (EKM) customers can choose to create and store their encryption keys in a specific data region with data residency.

Multi Orgs 

New and existing customers needing more than one data residency region to support their multi-geo compliance needs can opt-in to multi-org deployment & get multi-geo data residency allowing them to keep their data distinct.

Network and Data Flow Diagrams

See Asana’s Trust Center for a high-level data flow diagram and detailed network diagram.

Ready to get started?  

Reach out to our Sales team today.

Was this article helpful?

Thanks for your feedback