Data contribution FAQs

We’re continuously investing in ways to help your teams achieve more with our platform and this change is no different. AI is already multiplying what teams can accomplish, from agents that simplify complex workflows to enterprise search and chat that quickly surface the right context when it matters.

By learning from richer, more diverse customer data and usage patterns, we can deliver enhanced AI capabilities that unlock greater value across your organization. While we use this type of data to improve your individual company or organization’s experience today, we’re updating how we use customer metadata and in-app data to improve our apps and AI experiences for all customers.

At the same time, 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. That’s why we are pairing this change with new in‑app settings to give you control and strengthening our existing safeguards with de-identification and aggregation of all contributed data. This approach enables us to unlock more powerful AI experiences for all customers while keeping your data protected.

Today, we already use this metadata and in-app data to improve your organization’s experience only. For example, we may identify and analyze similar content within your instance to better surface relevant results for your users.

Starting August 17, 2026, we will begin to use customer metadata and in-app data to improve our apps and experiences for all customers.

To learn more about what we do today, please refer to our transparency notes.

While the updates reflected in our terms apply across Atlassian cloud apps, initially, these settings will only apply to data in Jira, Confluence, and Jira Service Management, including data in your Atlassian Platform apps (Rovo, Home, Teams, Projects, Assets, Goals, Analytics, and Administration). We will also provide these settings for certain Teamwork Graph connectors that you set up for your organization.

We’ll notify you when settings become available for additional apps you own, so you can review them in Atlassian Administration. To learn more about data contribution, please refer to our documentation.

Changes to how Atlassian will use metadata and in-app data to improve apps and experiences for all customers will go into effect on August 17, 2026.

Initially, data contribution settings will only apply to metadata and in-app data in Jira, Confluence, and Jira Service Management, including data in your Atlassian Platform apps (Rovo, Home, Teams, Projects, Assets, Goals, Analytics, and Administration) and certain Teamwork Graph connectors that you’ve set up for your organization. These settings will be available in Atlassian Administration by May 19, 2026, and you can manage them at any time. Atlassian will not use metadata or in-app data from apps where no data contribution settings are available.

We’ll notify you when settings become available for data within additional apps you own, so you can review them in Atlassian Administration.

Metadata refers to characteristics about your content and insights into content that is common across customers. Metadata includes two data types referred to as content attributes and common patterns.

• Content attributes are statistical characteristics, numeric fields, and derivatives of your in-app data.
  • Examples of content attributes may include the number of story points assigned to a Jira work item or the complexity of a Confluence page.
• Common patterns are phrases, keywords, and topics we extract from search queries and results, Rovo Chat (conversations, prompts, and responses), and custom configuration data that are frequently seen across many customers, while omitting rare data that may be unique to your organization.
  • Examples of common patterns may include common words, phrases, or Rovo Chat prompt topics that are frequently used by customers, such as “vacation policy” or “recap team activity.”

Before we use metadata to improve apps and experiences for all customers, we de-identify and aggregate it. We remove information that directly identifies individuals, such as names and email addresses, and we apply controls to prevent re-identification of the data.

Metadata helps us understand how customers typically use Atlassian apps so we can make them more intuitive and efficient. For example, with these insights we can improve search relevance and identify frequent tasks across customers. You can learn more about what metadata is, how it's protected, and how it's used in the documentation.

In-app data refers to content created by users within Atlassian apps. This can include things like:

• titles of and content within Confluence pages
• titles, description, and comments of Jira work items
• custom emoji names
• custom Jira or Confluence status names
• custom workflow names

All in-app data is de-identified and aggregated when being used to improve apps and experiences for all customers. We remove information that directly identifies individuals, such as name and email addresses, and we apply controls to prevent re-identification of the data.

When enabled through data contribution settings, Atlassian may use in‑app data to improve apps and experiences for all customers. For example, we may use in-app data to identify frequent tasks to surface better recommendations or next steps in workflows. You can learn more about what in-app data is, how we protect it, and how we use it in the documentation.

Data contribution defaults and settings are determined by the highest active plan within an Atlassian organization, including trials. If you have multiple apps in one Atlassian organization, the app with the highest plan will determine your defaults and available settings.

For example, if you have a Confluence Standard plan and Jira Premium plan in your Atlassian organization, your data contribution defaults and settings for the entire Atlassian organization will be aligned to the Premium plan. For more details, you can reference this table of defaults and settings in our documentation.

No, data contribution settings are determined independently for each Atlassian cloud organization based on the highest active plan in that specific Atlassian organization. If you manage multiple organizations, you’ll need to review and manage your data contribution settings for each organization individually in Atlassian Administration.

You can find your organization’s highest active plan by navigating to Atlassian Administration > Apps > Atlassian apps.

Yes, this change applies to any active plan in your Atlassian organization, including trials. Your data contribution defaults and settings will be based on the highest active plan in your Atlassian organization, which may be a trial.

If your highest active plan changes when your trial ends, you will have 30 days to review and manage your data contribution settings before we begin using metadata and in-app data according to your new settings.

Yes, this change applies to any active plan in your Atlassian cloud organization, including active cloud trials and Cloud Migration Trials. Your data contribution defaults and settings will be based on the highest active plan in your Atlassian cloud organization.

If you choose to purchase an Atlassian cloud plan when your Cloud Migration Trial ends, your available data contribution settings may change to match your new highest active plan in your Atlassian cloud organization. If they do, you will have 30 days to review and adjust your available data contribution settings before we begin using metadata and in-app data according to your new settings.

Please note: Your Data Center products are not affected by this change.

When you add new apps to your Atlassian organization, your existing data contribution settings will automatically apply to those apps. If the new app introduces data contribution settings that weren't previously available, we'll inform you so you can review and adjust them as needed. However, if you add an app to your Atlassian organization that does not currently have a data contribution setting available, for example Loom or Bitbucket, metadata and in-app data from that app will not be contributed.

When you change plans, we maintain your existing data contribution selections wherever possible.

• If you upgrade your plan and additional data contribution settings become available, we'll inform you so you can adjust them as needed.
• If you downgrade your plan, we will not change your settings to the default of your new highest active plan. However, if you currently have a Cloud Enterprise plan in your Atlassian organization and you move to a plan that doesn’t offer a data contribution setting for metadata, metadata contribution will be turned on. In that case, we’ll notify you and give you 30 days to review your new data contribution settings before we begin to use this data according to your new configuration.

Yes, this change is reflected in our customer terms of service. Our updated Atlassian Customer Agreement, AI Terms, Data Processing Addendum, and Privacy Policy will take effect on August 17, 2026. You can review the updated terms on our legal site.

To honor our customers' compliance requirements, Atlassian doesn’t use metadata or in-app data from Atlassian cloud organizations that have any of the following offerings:

• Customer-managed-keys (CMK) or bring-your-own-key (BYOK)
• Atlassian Government Cloud

• Atlassian Isolated Cloud

Additionally, we do not use metadata and in-app data from Atlassian cloud organizations with HIPAA compliance or from other certain government and financial services customers.

If your Atlassian cloud organization falls into one of these categories, it is excluded from data contribution, and none of its metadata or in‑app data is used for data contribution.

Any Atlassian cloud organization associated with a government entity is excluded from data contribution.

Please contact Atlassian Support if you are a government customer with questions about how this change applies to you.

Yes, educational institutions, including those that are government-run, are included in data contribution. Data contribution settings for educational institutions are determined based on highest active plan.

Data contribution settings are new controls available in Atlassian Administration that allow you to manage how Atlassian uses metadata and in-app data to improve apps and experiences for all customers. These settings are managed at the Atlassian organization level. If you manage multiple Atlassian organizations, you'll need to review and manage the data contribution settings for each one separately.

Initially, these settings will apply to metadata and in-app data in Jira, Confluence, and Jira Service Management, including data in your Atlassian Platform apps (Rovo, Home, Teams, Projects, Assets, Goals, Analytics, and Administration). We will also provide these settings for certain Teamwork Graph connectors that you set up for your organization. We will not use metadata or in-app data from apps that do not have data contribution settings available.

Organization admins can view and adjust data contribution settings in Atlassian Administration.

Data contribution default settings follow the highest active plan in each Atlassian cloud organization.

Some Atlassian cloud organizations are excluded from data contribution due to their compliance requirements, so default settings are not available.

Visit Atlassian Administration to see your organization’s specific data contribution settings.

If your Atlassian organization has an active Enterprise plan, you can opt-out of metadata contribution.

If your Atlassian organization’s highest active plan is Free, Standard, or Premium, metadata contribution is always on, and you’re not able to opt-out.

All metadata is de-identified and aggregated before it is used to improve apps and experiences for all customers. We remove information that directly identifies individuals, such as name and email addresses.

You can learn more about what metadata is, how it's protected, and how it's used in the documentation.

Please note: some Atlassian organizations, including those with certain compliance requirements may see different settings in Atlassian Administration.

Yes, if you’re an organization admin, you can change the data contribution setting for in-app data. Visit Atlassian Administration to see your organization’s specific data contribution settings.

Please note: some Atlassian organizations, including those with certain compliance requirements, may see different settings in Atlassian Administration.

Here are some examples of how Atlassian may use metadata and in-app data to improve apps and experiences for all customers:

• For metadata, we may classify Jira work items by intent and use those classifications to improve workflows and build templates based on the teams that use them most. We may also use common Rovo search query keywords that are aggregated across customers to help us train our search models to improve the relevance of search results.

• For in-app data, we may provide more tailored recommendations and next steps in workflows. For example, instead of Rovo responding with “Do you need help with anything?”, Rovo might suggest “Shall I create a work item for this?”.

We always de-identify and aggregate contributed data before using it to improve our apps and experiences for all customers.

Data contribution settings are gradually being rolled out to customers with at least one active Jira, Confluence, or Jira Service Management plan in their Atlassian organization. For these customers, settings will be available by May 19, 2026, and you will receive an in-app notification when your settings are available in Atlassian Administration.

Customers who do not currently have one of these Atlassian apps in their Atlassian organization will not see data contribution settings in Atlassian Administration. When settings are available for additional Atlassian apps, we’ll notify impacted customers so they have time to review and manage data contribution.

If your settings aren’t available yet, you can watch this video for a demo to get a preview of what you can expect.

Atlassian Platform apps (Rovo, Home, Teams, Projects, Assets, Goals, Analytics, and Administration) are included and embedded experiences across the collections and applications you purchase. Because of this, their metadata and in-app data contribution is managed through the same settings you use for Jira, Confluence, and Jira Service Management at the Atlassian organization level, rather than requiring you to manage each one separately. If you’re an organization admin, you can manage all of your available data contribution settings in Atlassian Administration.

Your organization’s data contribution settings may differ from what’s listed in our documentation if you have certain compliance requirements. If you have questions, please reach out to Atlassian Support.

Your default data contribution settings are based on the highest active plan in each of your Atlassian organizations, including trials. For example, if your Atlassian organization has Jira Standard and Confluence Premium, your highest active plan is Premium.

This means your default data contribution settings would be:

• On for metadata
• Off for in-app data, with the option to adjust in-app data contribution.

Organization admins can configure your data contribution settings by navigating to Atlassian Administration > Security > Data contribution. From there, you can review your default settings and make adjustments based on the highest active plan in your Atlassian organization. For a step-by-step guide, refer to our documentation or watch our demo video.

These two settings are independent of each other.

• Data contribution settings allow you to manage what data you share with Atlassian to improve apps and experiences for all customers.
• Activating or deactivating AI lets you manage which apps use AI and where AI experiences show up for your users.

Yes. Atlassian will use contributed metadata and in-app data from an individual Atlassian app to improve apps and experiences across its portfolio. For example, insights from how teams use Jira may be used to help improve experiences in Confluence. All contributed data is de-identified and aggregated before it is used to improve apps and experiences for all customers.

Yes, data contribution applies to certain Synced and Synced Lite connectors that you set up for your Atlassian organization. For more details on Teamwork Graph connector settings, please refer to our documentation.

Yes, you can adjust your available data contribution settings in Atlassian Administration at any time. Starting August 17, 2026, we will begin using eligible metadata and in-app data according to your settings at that point in time. If you change your settings after the effective date, we will begin using contributed data according to your new settings moving forward. We will remove previously contributed data as outlined in our documentation.

No, Atlassian will not use metadata or in-app data from apps where no data contribution settings are available.

Initially, data contribution settings will apply to metadata and in-app data in Jira, Confluence, and Jira Service Management, including data in your Atlassian Platform apps (Rovo, Home, Teams, Projects, Assets, Goals, Analytics, and Administration). We will also provide these settings for certain Teamwork Graph connectors.

We will notify you when data contribution settings become available for additional Atlassian apps, such as Loom and Trello, and give you time to review them in Atlassian Administration.

No, Atlassian does not currently use data within Atlassian Marketplace apps. We will notify you when data contribution settings become available for additional Atlassian apps, including Marketplace apps built by Atlassian, and give you time to review them in Atlassian Administration. To learn more about a specific app’s data use practices, privacy policy, and more, visit the Atlassian Marketplace.

No, if your Atlassian organization is excluded from data contribution, you do not need to take action.

Between now and May 19, 2026, you will see a new data contribution page in Atlassian Administration. For excluded organizations, data contribution will be turned off by default, and you won’t have the option to turn it on.

This is an intentional safeguard to ensure none of your Atlassian organization’s metadata and in‑app data is contributed.

We still recommend reviewing data contribution settings in Atlassian Administration for all of your Atlassian organizations to confirm they reflect your requirements.

Yes, because Rovo is an Atlassian Platform app, Rovo browser extension data will be contributed according to the data contribution settings you select at the Atlassian organization level.

Data contribution only applies to metadata and in-app data from apps that have data contribution settings available in Atlassian Administration, regardless of which Atlassian Collection you own. For example, if you own the Atlassian Teamwork Collection, you can manage data contribution for data in Jira, Confluence, and Platform apps (like Rovo), but not Loom.

Initially, data contribution settings will apply to metadata and in-app data in Jira, Confluence, and Jira Service Management, including data in your Atlassian Platform apps (Rovo, Home, Teams, Projects, Assets, Goals, Analytics, and Administration). We will also provide these settings for certain Teamwork Graph connectors. We will notify you when data contribution settings become available for additional Atlassian apps, such as Loom and Trello. Until then, we do not use metadata or in-app data from those apps.

No. Data from Data Center products is not subject to data contribution settings and is not included in this change. Data Center connectors, such as the Confluence Data Center to Rovo connector, are not currently included in this change. This data will not be contributed.

No, this change does not apply to metadata and in-app data hosted on Atlassian Government Cloud nor will it apply to apps hosted on Atlassian Isolated Cloud when it becomes available.

When customers contribute metadata and/or in-app data to improve apps and experiences for all customers, we apply existing safeguards with additional privacy-preserving measures, including:

• All metadata and in-app data is de-identified and aggregated before it is used to improve apps and experiences for all customers. We remove information that directly identifies individuals, such as names and email addresses.
• We go one step further for common patterns, where we extract phrases, keywords, and topics only from search queries and results, Rovo Chat (conversations, prompts, and responses), and custom configuration data frequently seen across customers. We omit data that is low in frequency and may be unique to your organization.
• We limit how Atlassian teams can access contributed in-app data, with robust monitoring practices. When improving features across customers, our teams only access in-app data you choose to contribute after it has been de-identified and aggregated.
• If you contribute metadata and/or in-app data, we may also extract common phrases, keywords, and topics from content attributes and in-app data frequently seen across customers. Similar to common patterns, we omit data that is low in frequency and may be unique to your organization, so that these insights are no longer associated with individual customers.

Additionally, every customer has the option to opt out of contributing in-app data.

Yes, we respect the data residency settings you have configured for your Atlassian organization. Data residency settings remain in effect for contributed in-app data, and this change does not alter how your data residency configurations are applied.

You can learn more about how data residency applies to contributed data, including data processed so that it's no longer associated with individual customers, in the documentation.

No, this change does not affect how we support your GDPR compliance. We will continue to process and transmit data in accordance with our Data Processing Addendum, Privacy Policy, and GDPR commitment.

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:

• remove the corresponding in-app data within 30 days from our datasets used to improve apps and experiences for all customers, and corresponding metadata within 90 days.
• retrain any models previously trained on that data.

We will stop collecting new metadata and/or in-app data from the corresponding app, and we will stop identifying recurring patterns from data you previously contributed. You can learn more about our retention of contributed data in our documentation.

We encrypt contributed metadata and in-app data in accordance with our standard encryption policy for all data in Atlassian cloud apps. Specifically, we encrypt in-app data and metadata in transit over public networks and at rest to protect it from unauthorized disclosure or modification. You can learn more about our encryption practices in our Trust Center.

No. Atlassian does not sell customer metadata or in-app data.