Data Residency Policy
Better flexibility and more control over your Cloud data
Edit Custom Field Values is able to follow Atlassian's data residency approach. Much of what Edit Custom Field Values can do for you in the area of data residency depends on how our app gets installed inside Jira. Therefore, we advise you to start reading about data residency availability, additional regions, and expanded capabilities by Atlassian and make sure you understand Atlassian's approach on data residency and realms.
If you have any questions after or during reading this, contact us via support.
Supported regions
Edit Custom Field Values supports the following realms:
EU
US
Global (this is the equivalent of the Atlassian global realm).
Data at rest
Edit Custom Field Values works on data that is inside Jira. There is no data at rest other than the data in the installation handshake between Jira and Edit Custom Field Values.
Edit Custom Field Values is hosted on Google Cloud computing services. We use the offered Google regions to deploy data resident silo's of the app's infrastructure. Google has extensive documentation on the whereabouts of the regions and an interesting whitepaper with background information.
The realms store their data in the following regions within the Google computing infrastructure:
Data in transit
Atlassian defines data resident compliant applications as where your data at rest is stored. Beyond this requirement we can also guarantee that data in transit does leave the realm at any point in time.
This can only be guaranteed if both Jira and Edit Custom Field Values are inside the same realm. Currently there is no way to verify in Jira's plugin manager in what realm an app is installed. If you want to have a confirmation on the installed realm, contact us via support.
Backups
Backups are stored in the same location in the realm. Additionally, we make offsite backups that are remote from the Google Cloud computing services, these backups are stored at Backblaze.
Last updated