robotsnoindex
robotsnoindex
descriptionChoose a location to host and store your product data for Jira and Confluence. Learn more about Atlassian's data residency.


Currently, only products with Enterprise plans can have in-scope data hosted within the EU and US realms. Later this year, products with Standard and Premium plans will be able to have in-scope data hosted within the EU and US realms. Learn more and sign up for updates


As an organization admin, view where your Jira Software, Jira Service Management, and Confluence data or in-scope product content is hosted.

A realm indicates the geographical boundary where your product content is hosted. All products are hosted within the global realm by default. Location refers to the AWS regions where your data or in-scope product content resides. Learn more about AWS infrastructure and our cloud hosting infrastructure

View where your data is hosted

To view where your data is hosted:

  1. Select the name of your organization at admin.atlassian.com to access your organization’s Administration overview.

  2. Go to Security > Data residency

  3. In the data residency table, see the Realm and Location columns.

For your Jira Software Enterprise, Jira Service Management Enterprise, and Confluence Enterprise, you can choose to have certain product content at rest hosted in the EU or US realms. If you have product content hosted in the EU or US realms and you’d like to release it, choose the Global realm.

Realm

Location

Global

All data, including product content, is hosted within any of our AWS regions, determined by Atlassian. We may move this data between regions as needed. All products are in the global realm by default.

APAC (Singapore and Sydney), EU (Frankfurt and Dublin), and US (US East and US West)

EU

In-scope product content for Jira Software Enterprise, Jira Service Management Enterprise, or Confluence Enterprise is hosted within the Frankfurt and Dublin AWS regions. Your product will show a PINNED status to indicate the in-scope product content is held in place within the realm.

EU (Frankfurt and Dublin)

US

In-scope product content for Jira Software Enterprise, Jira Service Management Enterprise, or Confluence Enterprise is hosted within the US East and US West AWS regions. Your product will show a PINNED status to indicate the in-scope product content is held in place within the realm.

US (US East and US West)

All data is hosted within our AWS regions. To optimize product performance, we don’t limit data movement when it’s hosted globally and we may move data between regions as needed. Currently, there are certain types of data that can’t be hosted in a specific location.

Product content that can be pinned in the EU or US realms 

(tick) Product content that can be pinned in a realm

(error) Product content that can’t be pinned in a realm

  • Jira Software data

    • All attachments

    • Board and sprint data

    • Comments

    • In-product notification data

    • Jira issues and field content (including system and custom fields)

    • Jira search data

    • Project configuration data (including workflows, custom field configuration, and board configuration)

  • Jira Service Management data
    • All attachments

    • Comments

    • In-product notification data

    • Insight object data and schema configuration data
    • Jira issues, request types, and field content (including system and custom fields)

    • Jira search data (excluding AI and machine learning enhancements)

    • Project configuration data (including workflows and custom field configuration)

    • Queue data

  • Confluence data

    • All attachments (including embedded images)

    • Comments

    • Confluence page and blog data

    • In-product notification data

    • Page and comment likes

    • Page metadata

    • Source data for notifications in emails

  • Jira Software data

    • Connected DevOps data

    • Product analytics

  • Jira Service Management data

    • All Jira Service Management features powered by Opsgenie

    • Customer accounts

    • Incident management functionality data

    • Knowledge base category data (if integrated with Confluence)

    • Product analytics

    • SLA configuration data

  • Confluence data

    • Permission and restriction configuration data

    • Product analytics (search data and space keys)

  • General data related to all products

    • Atlassian Marketplace and app data

    • Cached content (up to 30 days)

    • Data in transit (up to 30 days)

    • Product, audit, and operational logs

    • Third-party product integration data

    • User account information data

    • User analytics

Currently, all analytics data is hosted in the US. 

Why we don’t pin user account information data

Atlassian adheres to Standard Contractual Clauses to ensure that all user data is adequately protected as required under the General Data Protection Regulation. We treat all user data the same way and use industry-standard technical and organizational measures to secure the information we store. 

To limit the footprint of user data throughout our system, we centralize user information into a small, controlled set of identity services and use representative IDs to reference this information when required. Products only store IDs, so when products need to display user data they call the identity services to retrieve the user data represented by these IDs.

In order to meet performance requirements for users located around the world, these identity services replicate this user data globally from the centralized identity service.

For these reasons, data residency cannot apply to user data at this time. We understand that this may be a challenge for some of our customers, and we are happy to help you find a solution that would work better for your data residency needs.

For more information on where and how we store user data, see the Atlassian Trust center.

Why we don’t pin Atlassian Marketplace and app data

Atlassian Marketplace is comprised primarily of third-party app partners. These partners are not a part of Atlassian. We are in discussions with our Marketplace partners about data residency and we’re working on the ability for you to choose the realm where you’d like your app data hosted.

We will be progressively making more product content available to be pinned within a realm.

Why we don’t pin Jira Service Management data that is powered by Opsgenie

Jira Service Management combines the rich capabilities of Jira Service Desk with modern incident management, powered by Opsgenie, to provide a next-generation solution for both IT and Enterprise Service Management (ITSM & ESM). Currently, Jira Service Management features powered by Opsgenie aren’t incorporated into the Jira platform and aren’t eligible to be pinned to a realm. It’s on our roadmap, but until then, we’d like you to be aware that:

  • certain Jira Service Management product content will always be hosted in the US realm, even if you choose to have your Jira Service Management in the EU realm.

  • when you move your Jira Software, your Jira Service Management will still experience downtime, but your users will still be able to access features powered by Opsgenie.

If you have an Opsgenie product that is not incorporated in Jira Service Management, you can choose to host certain data in the EU or US. Learn more about data residency for Opsgenie

Data residency glossary

Term

Definition

Asset data

Third-party asset data stored in the asset platform used to syncronize with Jira functionality.

Atlassian Marketplace and app data

Data from Connect apps that may be stored outside of the Atlassian cloud environment by a third-party app vendor.

Attachments

Files attached or added to Jira Software or Confluence issues, pages, or other content.

Audit logs

Logs generated by admin actions.

AWS regions

Amazon Web Services regions.

Cached content

Content stored in a non-specified region for up to 30 days with the purpose of:

  • Progressive content migration to a nominated realm

  • Temporary storage of transactional content, such as emails, until delivery has been confirmed or abandoned.

Connected DevOps data

Data related to the Jira DevOps experience including:

  • Commits

  • Branches

  • Pull Requests

  • Builds

  • Deployments

  • Feature flags

  • Remote links

Customer accounts

User data in your customer accounts for Jira Service Management projects. 

Data in transit

Data being processed, and not stored, by Atlassian services.

Incident management functionality data

The data used in functionality for the incident management feature powered by Opsgenie.

In-product notification data

Data related to Jira Software and Confluence in-product notifications.

Jira Service Management features powered by Opsgenie

All features accessed through the Opsgenie URL. Some of these features are displayed in the Jira Service Management product screen.

Knowledge base category data

Categories for the Jira Service Management knowledge base, including description and configuration displayed in the portal when integrated with Confluence.

Operational logs

Atlassian system logs used for operational maintenance and diagnostic purposes.

Page metadata

The data used to describe a Confluence space for the purpose of search indexing.

Permission and restriction configuration data

Data related to the configuration of product or site access permissions or restrictions.

Pinned

Product content located and limited to either the EU or US realms is referred to as pinned product content.

Product analytics

Events fired by our cloud products for in-product user experience optimization and performance.

Product content

Data added directly by a user.

Product content at rest

Data added directly by a user, that has persisted for 30 days or longer in our cloud data stores.

Product logs

Logs generated by Jira Software and Confluence product changes related to content and configuration.

Queue data

Data in customer requests triaged for teams to answer. For example, a summary, status, or customer name.

SLA configuration data

Service Level Agreement text field names, time metric configuration, calendar configuration, and JQL queries for SLA Goal configurations.

Source data for notifications in emails

Data in an email with notification details. For example, an email that contains issue names and comments.

Third-party product integration data

Data from any product integrated with Jira Software or Confluence. For example, a Github integration

User account information data

Personal account information including:

  • Name

  • Email address

  • Avatar

User analytics

Events fired by our cloud products to help understand experiences based on how a user interacts with products.