Data contribution FAQs

Previously, we used 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.

Now, we also 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 went into effect on August 17, 2026.

Initially, data contribution settings 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. You can manage these settings in Atlassian Administration 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.

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

Yes, this change is reflected in our customer terms of service. Our updated Atlassian Customer Agreement, AI Terms, Data Processing Addendum, and Privacy Policy went into 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 configured or from Atlassian cloud organizations that belong to government 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.

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.

Highest plan

Metadata

In-app data

Free

On

On

Standard

On

On

Premium

On

Off

Enterprise

On

Off

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.

Data contribution settings are currently available to customers with at least one active Jira, Confluence, or Jira Service Management plan in their Atlassian organization.

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.

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, 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. We will only use eligible metadata and in-app data according to your settings. When you change your settings, 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 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. 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 does it apply to apps hosted on Atlassian Isolated Cloud.

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 ourData 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.