Zephyr provides data residency options to help organizations meet compliance and regulatory requirements by allowing customers to store their app data in specific geographic regions. This ensures that customer data remains within selected jurisdictions, aligning with data protection laws and industry best practices.
Currently, Zephyr supports data residency in the following regions:
United States (US) - Oregon
European Union (EU) - Dublin
Additional regions may be introduced based on demand. If your organization requires data residency in a different region, please contact our support team to express your interest.
Currently, data residency is only available for new Jira instances. New Jira instances will have their data stored based on their Jira location. Existing Jira instances cannot yet select a data residency region but will have migration options available in the coming quarters.
For new Jira instances, data residency will be determined as follows:
If a Jira instance is pinned to a supported region (US or EU) at the time of Zephyr installation, Zephyr will be installed in that region by default.
If a Jira instance is pinned to a region that Zephyr does not currently support, it will be hosted in the United States (US) by default.
If no specific region is pinned, Zephyr will be installed in the United States (US) by default.
For existing Jira instances, we are working on infrastructure changes and data migration to support additional regions than US. This feature will be available in the coming quarters. Jira instances will have the option to migrate their data to a different supported region once the migration process is made available.
Zephyr data will be stored in the selected region based on Jira's location settings. This includes:
Core application data: This includes user-generated content and configurations, like test cases, test scripts, test cycles, test executions, app attachments, and app configurations.
Account identifiers: Zephyr stores only the Atlassian account ID for users, as per GDPR compliance.
Jira-managed data like defects, fix versions, and components will follow Jira’s data residency policies. Zephyr data residency applies only to data managed by the app and does not override Jira’s data residency settings.
Some metadata and operational data, such as analytics, may still be processed globally. For a detailed list of tools processing data outside supported regions, refer to our Data Processing Tools Documentation.
The following data is not covered under Zephyr’s data residency support:
BDD test executions
Data processed by the No-code automation feature
Since data residency is only available for new Jira instances, if your Jira location is already pinned to a specific region, the Zephyr app will be installed in that region by default. Otherwise, it will be installed in the United States (US).
For existing Jira instances, data residency selection is not currently available. We are working on infrastructure updates to enable data migration, which will be available in the coming quarters.
Zephyr supports the following types of migrations:
JCMA Migration (From On-Prem to Cloud)
Zephyr supports migration from on-prem (Server or Data Center) to Cloud using the Jira Cloud Migration Assistant (JCMA). When an instance migrates, the app data will be transferred to the pinned region based on Jira’s location settings, ensuring that migrated data follows the selected data residency region.
Upgrade from Zephyr Squad to Zephyr
Currently, upgrades from Zephyr Squad to Zephyr are not supported for data residency. If a Jira instance requires data residency, it will not be able to upgrade from Zephyr Squad to Zephyr at this time. Once data residency support for upgrades is available, instances will be able to perform the upgrade.
Zephyr ensures data security and compliance with industry standards, including:
Certified under the Atlassian Security Program
SOC 2 Type 2 certified
GDPR compliant
Uses HTTPS for data encryption in transit and AWS mechanisms for encryption at rest
Compliant with Atlassian’s Marketplace Security Bug Bounty Program
Compliant with Atlassian’s Cloud Fortified apps program
For more details on data security and privacy, refer to our Data Security and Reliability Documentation.
We continuously evaluate the demand for additional data residency options. If you need a specific region not currently supported, please reach out to our support team to register your interest.
Can I select my data residency region after installation?
For new Jira instances, data residency is determined at the time of installation based on the Jira location. Existing Jira instances currently cannot select a data residency region, but migration to a different region will be available in the coming quarters.
When will data residency be available for existing Jira instances?
We are working on infrastructure updates to enable data migration, which will be available in the coming quarters.
What happens if a new region is introduced?
Once a new region is introduced, Jira instances will have the option to migrate their data to that region, once the migration feature is launched.
Does data residency impact app performance?
Data residency does not impact the core functionality of Zephyr. However, selecting a region closer to your users may improve performance by reducing latency.
For more details, contact our support team.