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 that Atlassian offers here.

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

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 that 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 the REST api request took) is stored globally.

ScriptRunner Data During JCMA Migrations

When migrating from Jira Data Center to Jira Cloud using the Jira Cloud Migration Assistant (JCMA), ScriptRunner configuration data migrates as part of your Jira data.

According to Atlassian, migration data is temporarily stored in transit in US-WEST or US-EAST for up to 14 days during the migration process. Because ScriptRunner data is embedded within Jira configuration data (for example, Workflow Rules are embedded directly into your workflows), it follows the same migration path.

ScriptRunner does not control where Atlassian stores or routes JCMA migration data during transfer.

Our migration processing services operate in both the EU and the US regions. If your ScriptRunner Cloud data residency is set to EU, ScriptRunner migration processing will occur in the EU where applicable. However, any data handled directly by JCMA during migration remains under Atlassian’s control.

Residency

So where does your data reside?

ScriptRunner for Jira and Confluence Cloud installed before June 30th 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.

You cannot have dual residency.

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, the European Union, or the US.

New instances of ScriptRunner for Jira and Confluence Cloud

When ScriptRunner is installed, its data is stored 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/

To ensure ScriptRunner for Jira and Confluence Cloud data residency within the EU (Frankfurt), you must select the European Union as the Jira instance location. If any other European country is selected, ScriptRunner for Jira and Confluence Cloud data residency will default to the US (Oregon).

If you are located outside of the EU or US, for example, in Australia, and select this as your instance location, ScriptRunner for Jira and Confluence Cloud data residency will default to the US (Oregon).

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 refer to Atlassian’s documentation.

Behaviours data residency

When your Jira Cloud instance is pinned to a specific data residency location, any data that Behaviours stores in Forge storage is also pinned to that same location. Forge storage is only used to store the information required to connect the separate Behaviours app with ScriptRunner. You can read more about how Forge Data Residency works.

Configuration data that enables communication between ScriptRunner and Behaviours is stored within ScriptRunner’s own hosting infrastructure on AWS. This data follows the same data residency location as your ScriptRunner instance and Jira Cloud location. You can find more information about the AWS regions here.

Behaviour scripts are also stored within ScriptRunner’s hosting environment and inherit the ScriptRunner data residency location.

While no script data is stored within the Behaviours app, it does transmit data from ScriptRunner for Jira Cloud to Jira. All Behaviour scripts are executed in the location from which the end user’s browser is running.