• Get started
  • Documentation

What are the compliance and residency expectations for Assets Data Manager?

Assets Data Manager for Jira Service Management Cloud is currently rolling out in Open Beta and will be available to all Premium + Enterprise sites by end of October 2024.

Data Manager contains both on-prem middleware components (the Adapters and Cleanse & Import clients) and Cloud-based components.

The following information applies only to the Cloud-based components of Data Manager.

This document does not apply to raw data that is resident or stored with third-parties, or information that is stored locally.

Does Data Manager impact my compliance with GDPR?

We are committed to helping our customers stay compliant with GDPR and their local requirements.  As we do today for all of our products, we will process and transmit data for Data Manager in accordance with our Privacy Policy, Data Processing Addendum, and GDPR commitment.

Is Data Manager SOC 2 and ISO compliant?

Although many of the systems and services used by Data Manager hold these certifications and adhere to the same internal policies and standards, Data Manager itself has not undergone external assessment for SOC 2 or ISO certification.

As we further develop our Data Manager services and tools, we will aim to include them in our standard audit certification reporting cycle.

Is Data Manager HIPAA compliant?

No, at this time Data Manager is not HIPAA compliant and our Business Associate Agreement (BAA) does not cover this feature. If you are required to comply with HIPAA, we recommend that you do not use this feature until we have expanded our coverage to include it.  

Will Data Manager allow changes to Data Residency settings?

At this time Jira Service Management Data Residency is set during the initial initialisation of the Data Manager feature. After the feature has been initialised, Data Manager will not allow a change of Data Residency.

Example: If you select a US Data Residency, we would not support a move to a EU Data Residency after the feature has been initialized.

Still need help?

The Atlassian Community is here for you.