---
title: "Data Residency"
canonical: "https://docs.getxray.app/space/XRAYCLOUD/44565771/Data%20Residency"
format: markdown
---
Table of Contents
> Macro (toc)
# Introduction
[Data Residency](https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/) refers to the ability to specify the geographic location where your data is stored and processed. This capability is crucial for organizations that must comply with local data protection laws, industry regulations, or internal policies requiring data to be stored in specific regions. By controlling data residency, you can ensure that sensitive information remains within the designated boundaries, enhancing security and compliance.
Key aspects of data residency include:
- **Geographic control:** select a specific region where your data will be stored. This is important for meeting regional data protection regulations.
- **Compliance assurance:** helps organizations comply with laws such as the GDPR in Europe, CCPA in the United States, or other local data protection regulations.
- **Improved performance:** store data closer to your users, you can reduce latency and improve application performance.
- **Enhanced security:** keep data within specified geographic boundaries can reduce the risk of unauthorized access and data breaches.
# Overview
> ℹ️ Data Residency is available for [Jira](https://www.atlassian.com/software/jira), [Jira Service Management](https://www.atlassian.com/software/jira/service-management), [Jira Product Discovery](https://www.atlassian.com/software/jira/product-discovery), and [Confluence with Enterprise](https://www.atlassian.com/software/confluence/enterprise), [Premium](https://www.atlassian.com/software/confluence/premium), and [Standard plans](https://www.atlassian.com/software/confluence/standard).
> ⚠️ ### **Co-Location Requirement for Xray Standard and Enterprise **(this only applies to the non-standalone [app versions](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/392921546) - versions before [Xray Cloud 6.10.0](https://docs.getxray.app/space/XRAYCLOUD/433979453/Xray+Cloud+6.10.0+Release+Notes))
> ⚠️
> ⚠️ - **For Xray Enterprise customers**, it is **required that Xray Standard and Xray Enterprise are deployed in the same location**. If they are not co-located, Xray Enterprise will not function as expected. This is essential to ensure proper communication, reduce latency, and maintain the overall performance of the system. To understand where Xray is installed, check below.
> ⚠️ - To avoid any disruption in service or degradation in functionality, please ensure that both versions are hosted within the same infrastructure environment.
Data Residency gives you control over where your [in-scope product data](https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/#In-scope-product-data) for Jira, Jira Service Management, Jira Product Discovery, and Confluence is hosted.
It allows you to choose whether it’s globally distributed or held in place in a defined geographic location, such as Europe or the US.
If you work in a regulated industry like finance, government, or healthcare, Data Residency may be a necessity for operating in a Cloud environment. More generally, it can also help you meet company data management requirements.
## Viewing where your Jira Data is Hosted
You can view where your in-scope product data is hosted from your organization's administration (you must have organization admin permissions to do this):
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> Go to [admin.atlassian.com](http://admin.atlassian.com/). Select the desired organization if you have more than one (Figure 1 - 1).
>
> 
>
> > Macro (rw-step)
>
> The Atlassian Admin screen will open (Figure 2). On the left-side menu, click *Data management* (Figure 2 - 1) and then *Data residency* (Figure 2 - 2). You can also use the search bar (Figure 2 - 3) to type *Data residency* and access it.
>
> 
>
> > Macro (rw-step)
>
> This will open the Data Residency screen for your organization. This screen (Figure 2) lists:
>
> - The Atlassian Marketplace apps in your organization (Figure 2 - 4) and their status (Figure 2 - 7).
> - The location of each app (Figure 2 - 5). If an app is pinned to a location, its in-scope data is held there. If Data Residency is available for your app, you can request to have its in-scope data moved and pinned to a new location.
> - Which Marketplace apps are pinned (Figure 2 - 6).
> - How many apps are pinned (Figure 2 - 10).
> - How many apps are eligible to be moved (Figure 2 - 11).
## Moving Jira Data to Another Location
If Data Residency is available for your product, you can request to have your in-scope product data pinned to a new location. You may need to do this to meet company data requirements. Or, if you work in a regulated industry like finance, government, or healthcare, this may be necessary for operating in a cloud environment.
This section provides detailed information on how to request a Data Residency move, how the move will affect your product, and how to cancel your Data Residency move for apps.
> ℹ️ The default Jira location for the data is the US, but that can change at Atlassian's discretion. If you want to ensure your data is hosted in the US region, we advise you to pin your data to the US region.
## Scheduling a Data Residency Move
If data residency is available for your product, you can move it to one of the supported [locations](https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/#What-are-locations-and-AWS-regions).
To schedule a data residency move:
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> Go to [admin.atlassian.com](http://admin.atlassian.com/). Select the desired organization if you have more than one (Figure 1 - 1).
>
> > Macro (rw-step)
>
> The Atlassian Admin screen will open (Figure 2). On the left-side menu, click *Data management* (Figure 2 - 1) and then *Data residency* (Figure 2 - 2). You can also use the search bar (Figure 2 - 3) to type *Data residency* and access it.
>
> > Macro (rw-step)
>
> In the Atlassian apps table, click the ellipsis button (Figure 3 - 1) and then *View app details*** **(Figure 3 - 2)** **in the line of the product that you want to move.
>
> 
>
> > Macro (rw-step)
>
> A new screen will open (Figure 4). There, click the *Set location* button (Figure 4 - 1).
>
> 
>
> > Macro (rw-step)
>
> A new screen will open (Figure 5).
>
> Review the information about the steps involved in moving a product. Click the *Next* button (Figure 5 - 1).
>
> 
>
> > Macro (rw-step)
>
> Select the location from the menu where you want to move your product (Figure 6 - 1) and click *Next* (Figure 6 - 2).
>
> 
>
> > Macro (rw-step)
>
> Select a move window option (Figure 7 - 1) and click *Next* (Figure 7 - 2).
>
> 
>
> > Macro (rw-step)
>
> Review the apps (Figure 8 - 1) and click the *Next* button (Figure 9 - 2).
>
> 
>
> > Macro (rw-step)
>
> Review your data residency move request details (Figure 9 - 1) and click *Submit request* (Figure 9 - 2).
>
> 
# Operations
With Data Residency, you can control where your data is stored. Xray fully supports Data Residency.
Currently, Atlassian supports a combined move of a product and Xray.
## Moving your Xray Data to Another Location
> ℹ️ In case your location is Europe and you move Xray Data to a European location (like Europe - Frankfurt), you may experience improved performance on loading information from Xray.
### App Statuses
Before you request a Data Residency move for Xray, you must understand the different app statuses (Figure 10 - 1).
Xray offers the ability to pin and move data between locations. There are five app statuses:
[Pinned]
Xray is already pinned to the product location and store data in the same location.
For example, say you have Confluence pinned to the USA location and install an Xray pinning to the USA. If Xray is installed after the product is pinned, it is also moved to the USA location.
#### [Eligible]
For Xray to be eligible for a Data Residency move, it must:
- Support data pinning in the same location as the product.
- Support data movement between locations.
- Not be currently pinned to the same location as the product.
#### [not Eligible]
If Xray is showing as* Not eligible* for data residency move, it can be because the area selected is not supported for Data Residency in the same location as the product.
#### [no action available]
If you have apps that have no action available for a data residency move, it is because some app partners specify that their apps either:
- Only store data within the Atlassian product.
- Do not store any data at all.
#### [Not Set]
[Not applicable]
### Requesting a Data Residency Move for Xray
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> Go to [admin.atlassian.com](http://admin.atlassian.com/). Select the desired organization if you have more than one (Figure 1 - 1).
>
> > Macro (rw-step)
>
> The Atlassian Admin screen will open (Figure 2). On the left-side menu, click *Data management* (Figure 2 - 1) and then *Data residency* (Figure 2 - 2). You can also use the search bar (Figure 2 - 3) to type *Data residency* and access it.
>
> > Macro (rw-step)
>
> In the Atlassian apps table (Figure 10), click *Set Location* (Figure 10 - 2).
>
> > Macro (rw-step)
>
> A new screen (Figure 11) will open with the information regarding the change of the Data Residency location. Review the information and click *Next* (Figure 11 - 1).
>
> 
>
> > Macro (rw-step)
>
> Use the dropdown menu to select your location (Figure 12 - 1). Then, click *Next* (Figure 12 - 2).
>
> 
>
> > Macro (rw-step)
>
> Select a move window option (Figure 13 - 1) and click *Next* (Figure 13 - 2).
>
> 
>
> > Macro (rw-step)
>
> Review the Marketplace apps eligible for the move (Figure 14 - 1) and click Next (Figure 14 - 2).
>
> 
>
> > Macro (rw-step)
>
> Review your request and once you’re done, click *Confirm request* (Figure 15 - 1).
>
> 
>
> > Macro (rw-step)
>
> You will see a message confirming the submission of your request (Figure 16 - 1), and your marketplace app status is updated (Figure 16 - 2).
>
> You will also receive an email confirmation will the move details.
>
> 
>
> > ℹ️ - Data Residency move for Marketplace apps must be requested with at least three days in advance.
> > ℹ️ - Xray might already be pinned to your selected region, even if you haven’t explicitly chosen that region. Xray might have been pinned during installation or pinned there to optimize performance. You can move your Xray data to another location of your choice, provided Xray supports your preferred location.
> > ℹ️ - You will be notified, via email, regarding the start and finish of the moving process.
### Xray Locations
At the launch, Xray supports data residency in the following locations:
- United States.
- Europe (Frankfurt).
- Germany (Frankfurt) - new location.
- Australia (Sydney).
### Data Residency Move for Xray and the Impact on Your Product
While Xray is moving your eligible app data to the requested location, the product will be offline, and your users will not be able to access it. This move can be scheduled up to three days in advance and takes up to 24 hours for all apps to move.
You should plan for your product to be offline for 24 hours during an app move. When you request a data residency move for Xray, you select a 24-hour move window. Atlassian provides this 24-hour window for Xray to move the app. Xray aims to complete your move within this window, but we cannot guarantee the exact time of the move, as it depends on the size of the customer data.
As soon as the move is complete, your Atlassian product and Xray will be back online, and you'll be notified by email.
> ℹ️ When moving your data to a new region, the file dates will be updated to reflect the date of the transfer. We are working on a solution to preserve the original dates during this process.
> ℹ️
> ℹ️ If you have any questions, please [contact the Xray Support team](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28).
## Cancelling a Data Residency Move for Apps
You can cancel a Data Residency move as long as the respective process active status is *MOVE SCHEDULED* (Figure 12 - 4). You can’t cancel a move after the status has changed to *MOVE IN PROGRESS*.
To cancel a Data Residency move:
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> Go to [admin.atlassian.com](http://admin.atlassian.com/). Select the desired organization if you have more than one (Figure 1 - 1).
>
> > Macro (rw-step)
>
> The Atlassian Admin screen will open (Figure 2). On the left-side menu, click *Data management* (Figure 2 - 1) and then *Data residency* (Figure 2 - 2). You can also use the search bar (Figure 2 - 3) to type *Data residency* and access it.
>
> > Macro (rw-step)
>
> Find the app in the Atlassian apps table, click the ellipsis button (Figure 17 - 1), and then *Cancel move* (Figure 17 - 3).
>
> 
>
> > Macro (rw-step)
>
> A modal will open (Figure 18). Click *Cancel move* (Figure 18 - 2) to confirm the removal of the process, or *Keep move* (Figure 18 - 1) to go back and keep the location move.
>
> 
Support/Troubleshooting
If you have questions or technical issues, please [contact the Support team via the Customer Portal (Jira service management)](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) or [send us a message using the in-app chat](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44577312).