Version: TP.27032024.03
Effective date: 21/November/2024
1. Relationship to End User License Agreement (EULA)
This Data Residency policy is subject to the terms and conditions set forth in the End User License Agreement (EULA).
2. Managing Data Residency for Vansah Test Management For Jira
Data residency provides you with the authority to determine the location where your in-scope product data for Vansah Test Management for Jira. This choice enables you to select a specific geographic region, such as Australia, Europe, or the US.
3. Importance in Regulated Industries and General Data Management
For professionals operating in regulated sectors like finance, government, or healthcare, data residency is often essential when working in a cloud-based setting. Moreover, it can aid in fulfilling company data management standards across various industries.
4. View Where Your Data is Hosted
Data residency empowers you to decide where your in-scope Customer Data is hosted. By choosing a supported geographic location, you can ensure that your Customer Data is based on where you have pinned your Jira region.
To view where your Jira product data is hosted:
Go to Administration . Select your organization if you have more than one.
Select Security > Data residency
Now check under App status to ensure Vansah is PINNED to the same location.
5. In-scope Product and Customer Data
All product and Customer Data is pinned to your Jira supported region (see Regions supported). The table below lists the data types which will be pinned if your region is supported.
Product | Pinned Data | Can’t be pinned |
Vansah Test Management For Jira | Customer Data:
Product Data:
| Workspace Jira site name: Example: https://<>.atlassian.net |
6. Data Residency Diagram
The following diagram is an example based on a customer’s Jira Cloud product being pinned to Australia (AU) prior to installing Vansah.
Regardless of the region, Vansah’s BaseURL will be used to support your pinned Jira Region. Authentication is managed via Jira’s identity service.
7. Supported Locations/Regions
A location is the geographical boundary where in-scope product and Customer Data is hosted. Each location corresponds with one or more regions, which are physical locations around the world. The following locations are available for you to select from:
Location | Region | Status |
Default (USA) | North America (New York) | Available |
Australia | Sydney | Available |
Singapore | Asia Pacific (Singapore) | TBC |
Germany | Europe (Frankfurt) | Available |
EU | Europe (Frankfurt) | Available |
United Kingdom | London | Available |
By default, Vansah is hosted in the Default (USA) location when your Jira instance has not been pinned to another location which is supported by Vansah. If you require a Region which has not been included above however is supported by Atlassian, please raise a support request to have your region available before installing or moving your data. We are committed to supporting all Atlassian regions in the near future.
8. Requesting Data Residency Changes
If you require your Customer Data to stay in a specific location, and data residency location is available, you can request to have your Customer Data moved to a location and pinned there. For more information on how to request a data residency move, please refer to our article “How to request a Data Residency move for Vansah”.
9. Additional Information
For more information on data security and data privacy, please refer to our Data Security and Data Privacy policies.
10. Contact Information
If you have any questions about this policy , please contact us through our support port