Data Residency

All new Jira and Confluence Cloud customers can choose the location where their instance is hosted, including all processed and stored data related to that instance. These locations are known as the realms, or localities, that customers can choose to pin their data to, provided they are compliant with any legislation in their chosen region (ex, GDPR in the EU). You can find more information on locations and associated AWS regions Atlassian offer here.

ScriptRunner for Jira and Confluence Cloud offers hosting in either the EU (Frankfurt) or USA (Oregon). The location of ScriptRunner data residency will match that of your Jira or Confluence instance if you chose one of these regions.

The ScriptRunner Behaviours app cannot currently be pinned to a specific location, as this is not supported. Instead, it will adopt a global location, meaning data residency is not guaranteed to be specifically within the EU (Frankfurt), or in the US (Oregon), as it is determined by Atlassian. You can find more information about the AWS regions associated with the global location here.

What is Data Residency?

Data residency refers to the physical location where an organization's data is stored and processed. To understand the term Data Residency and how it relates to your instance of ScriptRunner for Jira and Confluence Cloud, we can outline the benefits it provides and break it down into its component parts. 

Benefits of Data Residency

Data residency gives organizations more control over their data by ensuring their user-generated content is stored within the US or EU. Companies who work in regulated industries like finance, government, or healthcare may need data residency to operate in a cloud environment.

Data

All script data, including Behaviour scripts, is stored within ScriptRunner for Jira Cloud and Jira. 

The data that is stored includes:

• all scripts, script variables and ScriptRunner related configurations (script fragments, scripted fields)
• the logs generated by any scripts. These are stored in whole in the specific region/realm where their Jira or Confluence instance is pinned.
  Note: Metadata about scripts that have run (ex. duration, errors, how long rest api request took) are stored globally.

Residency

So where does your data reside?

ScriptRunner for Jira and Confluence Cloud installed before June 30 2021

Your data is stored in the US regardless of where you are geographically located however you can change the data residency.

ScriptRunner or Jira and Confluence Cloud installed after 30th June 2021

Your data will be stored in the EU (Frankfurt) if your Jira instance is pinned to the European Union otherwise it will be stored in the US (Oregon).

If you require data residency hosting in a region that we do not currently provide, please let us know via our suggestion board.

Set Locality

Instances of ScriptRunner for Jira and Confluence Cloud installed before 30th June 2021

These instances are automatically stored in the US (Oregon) unless you have pinned your Jira instance to a supported region, European Union or the US.

New instances of ScriptRunner for Jira and Confluence Cloud

When ScriptRunner is installed, its data is stored in the in the EU (Frankfurt) if your Jira instance is pinned to the European Union otherwise it will be stored in the US (Oregon). For details on how to pin the region, see:

https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency-and-realms/

Change Locality

You can change the data residency location of your Jira instance and ScriptRunner for Jira/Confluence at any time. For more information on how to perform a data residency move please Atlassian’s documentation.