Understand data contribution
We’re updating how we use customer data so we can improve our apps and AI experiences for all customers. Learn more about this change
We’re continuously investing in ways to help your teams achieve more with our platform. A big part of that is building meaningful AI experiences that are genuinely useful in your day‑to‑day.
With data contribution, metadata and in-app data from your Atlassian organization can be used in accordance with your settings to improve our apps and AI experiences for all customers. This allows us to learn from richer, more diverse customer data and usage patterns, so we can deliver enhanced AI capabilities that unlock even greater value across your organization. For example, it enables smarter assistants, faster workflows, and predictive insights that shape the experience in Atlassian apps. How your data contributes to app improvements
We know you trust Atlassian with some of your most business‑critical work, and we take that responsibility seriously, especially when it comes to keeping your data safe. We don’t use metadata or in-app data from apps that don’t have data contribution settings available, and we don’t use metadata or in-app data from Atlassian organizations with certain compliance requirements. More about the data contribution settings availability
Where data contribution setting are available, you can control how Atlassian uses metadata and in-app data from your Atlassian organization, to improve apps and AI experiences for your teams and teams like yours. More about the data contribution settings
Trust and accountability
We’re committed to being transparent about how we safeguard your data contributions. We apply privacy-preserving measures, including de-identification and aggregation, to protect the data you contribute before using it to improve our apps and services for all customers. More about how we protect your data
Refer to this table to understand how we safeguard your data contributions.
De-identification | Metadata and in-app data are de-identified and aggregated before we use them to improve apps and experiences for all customers. We remove information that directly identifies individuals, such as name and email. |
|---|---|
Access controls and purpose limitation | We ensure our teams access metadata and in-app data only for approved purposes. |
Encryption | We encrypt metadata and in-app data in transit over public networks and at rest, to protect it from unauthorized disclosure or modification. More about how we encrypt data |
Data residency | The data residency settings you’ve enabled for your Atlassian organization will apply to your in-app data contributions. We are unable to apply customer data residency settings to contributed in-app data that has been de-identified and aggregated at a customer level, such that it is no longer associated with individual customers (including common patterns). |
Contributed data retention | If you adjust your data contribution settings to opt out of metadata and/or in-app data, or delete an app or site, we will:
Data that is de-identified and aggregated at a customer level such that it is no longer associated with individual customers (including common patterns), may be retained for up to seven years. |
Was this helpful?