...
Reference: Atlassian document - Data Residency.
AssetIT
...
Adopting Data Residency
AssetIT has implemented the realm pinning capability. The URLs defined as regionBaseUrls control the location when an app is initially installed. After a customer moved a product to a specific location, when an app is installed, the corresponding location from the Connect descriptor will be selected. Even if the product has not been moved to a specific location, the regionBaseUrls is used at app installation time if the app supports the location where the product is provisioned.
AssetIT supports data residency in the following locations:
...
Products in your organization along with their status.
Apps associated with your organization and their respective statuses.
Location of each product and the corresponding AWS regions. If a product is pinned to a location, its in-scope data is stored there.
The number of products with a defined location.
The number of apps eligible for location changes.
Data Residency Policy
This policy outlines the data residency approach for AssetIT in compliance with Atlassian's data residency framework.
Data Storage and Management
Atlassian-Managed Data: All in-scope Jira product data is managed and stored by Atlassian.
AssetIT-Managed Data: All AssetIT in-app data and settings are stored in the selected data residency location, ensuring compliance with the chosen geographic requirements.
In-scope Product Data
According to Atlassian, this table presents in-scope product data types that can be pinned and out-of-scope product data that cannot be pinned. For definitions of these data types, please refer to the glossary in this Atlassian document: Understand data residency.
Data Residency Location
AssetIT will store all user-generated content and settings within the specified data residency region to meet compliance and security standards.
...
For further information about data management and security, visit DevSamurai Trust Center.