I’m trying to understand Atlassian’s upcoming data contribution changes for customers whose highest active plan is Premium. Atlassian says these changes take effect on August 17, 2026. Based on the documentation, the default for Premium is: * Metadata: On * In-app data: Off Atlassian also says: * Enterprise customers can opt out of metadata contribution, but * Free, Standard, and Premium customers cannot opt out of metadata contribution because it is always on. That seems to mean a Premium customer may be able to opt out of in-app data contribution, but not metadata contribution, even though Atlassian says metadata can include content attributes, common patterns, search activity, Rovo Chat patterns, and certain custom configuration data. If that reading is correct, I think a few points need clarification: * Is Enterprise really the only standard way to fully opt out of metadata contribution? * If a Premium customer disables all available in-app data contribution settings, what data can still be used under metadata contribution? * How broad is “metadata” in practice? Does it include search queries, workflow/status naming patterns, custom field patterns, Rovo Chat prompts/responses, and other admin/configuration-derived signals? * Are there any non-Enterprise exceptions (contractual, compliance-based, or policy-based) for customers who do not want their metadata used to improve apps and experiences for all customers? The core concern is simple: if a Premium customer does not want Atlassian using either in-app data or metadata to improve apps and AI experiences for all customers, is there any path to do that without upgrading to Enterprise?

Hi Cameron - thank you for your post and the questions above. Here is a summary of responses to the questions above. Is Enterprise really the only standard way to fully disable metadata contribution? In addition to customers with at least one Enterprise plan or trial, customers with specific compliance requirements may see a different experience in Atlassian Administration. To confirm your data contribution settings, navigate to Atlassian Administration > Security > Data contribution. If you have additional questions or concerns, please contact Atlassian Support. If a Premium customer disables all available in-app data contribution settings, what data can still be used under metadata contribution? All eligible data that is classified as metadata content attributes and common patterns will remain in-scope for data contribution. For details on what constitutes metadata, please refer to the examples we’ve provided in our documentation. How broad is “metadata” in practice? Are search activity, naming patterns, workflow/configuration patterns, and Rovo interaction patterns included in that scope? Yes, all of the examples you’ve listed would be in-scope for metadata contribution. As a reminder, common patterns are derived only from the following types of in-app data: search queries and results prompts and responses in Rovo Chat configuration items you define (for example, names of custom fields in Jira) In addition to common patterns, content attributes are statistical characteristics, numeric fields, and derivatives of your in-app data. For metadata examples, please refer to our documentation. What specific exclusion path exists for compliance-sensitive customers that do not have Enterprise, if any? Please refer to our FAQs for details on exclusions available to customers with specific compliance requirements. 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. These exclusions are not limited to customers with Cloud Enterprise plans. If a customer qualifies for exclusion based on the criteria detailed above, they will automatically be excluded from data contribution. If you have more questions, please contact Atlassian Support. How can an organization administrator find out if their organization has been excluded from data contribution? Organization administrators can verify whether their Atlassian organization is excluded from data contribution by navigating to Atlassian Administration > Security > Data contribution. If the Atlassian organization is excluded due to specific compliance requirements, there will be no option to opt-in to data contribution settings as an intentional safeguard. Can you confirm whether exclusions are automatic or require a request/review process + Who customers should contact to evaluate eligibility Exclusions for Atlassian organizations with specific compliance requirements are automatically applied, regardless of the active plan(s) in your Atlassian organization. If an organization administrator has at least one active trial or plan of the in-scope Atlassian apps, they should have received an email notification and in-app banner with details on their available data contribution settings. If you aren’t an organization administrator, we recommend you connect with them first to confirm. If you and your admin team need additional support, please contact Atlassian Support. Can you confirm whether similar accommodations exist for other compliance-driven customers on Premium? We intentionally designed our approach to serve the broadest set of customer needs by aligning with the most common compliance requirements we see across our customer base. Therefore, Atlassian cloud organizations with the following offerings are excluded: 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. These exclusions are not based on the highest active plan or trial, and are not limited to customers with an Enterprise plan. If you have additional compliance-driven requirements, please contact Atlassian Support so we can discuss your unique situation.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Premium customers: can we opt out of metadata contribution without Enterprise?

Cameron Farrier

I’m trying to understand Atlassian’s upcoming data contribution changes for customers whose highest active plan is Premium. Atlassian says these changes take effect on August 17, 2026.

Based on the documentation, the default for Premium is:

Metadata: On
In-app data: Off

Atlassian also says:

Enterprise customers can opt out of metadata contribution, but
Free, Standard, and Premium customers cannot opt out of metadata contribution because it is always on.

That seems to mean a Premium customer may be able to opt out of in-app data contribution, but not metadata contribution, even though Atlassian says metadata can include content attributes, common patterns, search activity, Rovo Chat patterns, and certain custom configuration data.

If that reading is correct, I think a few points need clarification:

Is Enterprise really the only standard way to fully opt out of metadata contribution?
If a Premium customer disables all available in-app data contribution settings, what data can still be used under metadata contribution?
How broad is “metadata” in practice? Does it include search queries, workflow/status naming patterns, custom field patterns, Rovo Chat prompts/responses, and other admin/configuration-derived signals?
Are there any non-Enterprise exceptions (contractual, compliance-based, or policy-based) for customers who do not want their metadata used to improve apps and experiences for all customers?

The core concern is simple: if a Premium customer does not want Atlassian using either in-app data or metadata to improve apps and AI experiences for all customers, is there any path to do that without upgrading to Enterprise?

Accepted answers

All comments

Arend Feenstra

Hi @Cameron Farrier

I am also researching what exactly is changing and what impact this has involved our organisation and customers. Due to the changed policy, Atlassian should be able to share more information about the right migration paths. In particular, what is exactly collected in the collection of Metadata.

This webinar might be interesting — users could register at the end of April for a webinar by Atlassian. @Atlassian, can you share more information about what exactly is changing in the policy.

https://webinars.atlassian.com/atlassian/emea-atlassian-s-updated-data-practices-what-s-changing-and-how-it-impacts-you-84a2f1bbae64?bmid=c744b8934aec&bma=353c86e4cd85&bmi=681a24250004&bmid_type=member

Who can provide legal assistance regarding whether the new policy complies with AVG/GDPR European guidelines? Collecting data for 7 years seems excessive to me, especially when it concerns meta-app data.

Best regards

Arend

Claus Østergaard Pedersen

Hi @Cameron Farrier

I very much agree with your thoughts, and share your worries about compliance.

The only information about opting out of the metadata sharing, I have been able to find, as a non Enterprise user, is the following:

Additionally, we do not use metadata and in-app data from Atlassian organizations with HIPAA compliance or from other certain government and financial services customers.
If your Atlassian organization falls into one of the above categories, it is excluded from data contribution, and none of its metadata or in‑app data is used for data contribution.

The above commes from the following page: https://support.atlassian.com/security-and-access-policies/docs/data-contribution-settings-availability/

How to get "approved" as being an organization that fits the requirements, I unfortunately do not know.

Please share if you find any additional information.

Thanks in advance.

Best regards

Claus

Cameron Farrier

Thanks, Arend.

I’m glad you raised the same concern from the EU/GDPR angle as well. You called out a few of the exact gaps I’m trying to understand too: what Atlassian means by metadata in practice, what the actual migration or decision paths are for non-Enterprise customers, and whether the retention period and resulting use align with customer expectations and compliance obligations.

The webinar reference is helpful. Even with that, I still think Atlassian should publish a much more concrete breakdown that answers questions like:

what specific data elements are treated as metadata
which of those elements remain on for Premium customers even when in-app contribution is disabled
whether search activity, naming patterns, admin/configuration-derived signals, and Rovo interaction patterns are included
whether there is any non-Enterprise path for customers with compliance concerns for opting-out of metadata contributions

If Atlassian is monitoring this thread, a direct clarification on those points would be very helpful for admins trying to evaluate risk, governance, and customer impact.

Cameron Farrier

Thanks, Claus. I appreciate you pointing to that exception language. The note you found seems to confirm there may be some exclusions for HIPAA-compliant organizations and certain government or financial services customers, even though the general guidance appears to say Free, Standard, and Premium customers cannot opt out of metadata contribution.

That creates a follow-up question that still does not seem clearly answered: how does a customer actually determine whether they qualify for one of those exclusions, and what is the process for having that recognized by Atlassian?

At a minimum, I would hope Atlassian could clarify:

the exact eligibility criteria for those exclusions
whether they are automatic or require a request/review process
who customers should contact to evaluate eligibility
whether similar accommodations exist for other compliance-driven customers on Premium

If I find anything more concrete, I’ll add it here as well.

Cameron Farrier

Appreciate the thoughtful responses so far. The replies here reinforce that the main issue is not just whether a setting exists, but whether customers can get a precise and operational definition of metadata contribution for Premium environments.

For Atlassian, I think the most helpful next step would be a direct answer to a few narrow questions:

Is Enterprise truly the only standard path to fully disable metadata contribution?
For Premium customers who disable all available in-app contribution settings, what data still remains in scope under metadata contribution?
Are search activity, naming patterns, workflow/configuration patterns, and Rovo interaction patterns included in that scope?
What specific exclusion path exists for compliance-sensitive customers that do not have Enterprise, if any?

I’m hoping Atlassian can clarify this publicly, since it seems likely a number of admins are trying to answer the same governance and compliance questions right now. Considering the data contribution settings were just made available last week- it would be helpful to understand what other levers of control (if any) will be made available to admin teams between now and the effective date approaching in August.

Arend Feenstra

@Cameron Farrier an @Claus Østergaard Pedersen Excellent to read, in that case we could possibly start a collective, with multiple individuals or organizations experiencing the same concerns. I am also active in other legal communities, where I have raised the same concerns. Vendors have a transparency obligation, including under the upcoming EU AI Act (August 2, 2026), to disclose what data is being collected and for what purpose.

Cameron Farrier

Agreed. I think that is the core issue here: transparency and customer control.

If multiple customers are reading the policy the same way and raising the same concerns, Atlassian should respond with a more specific public explanation of what falls under metadata contribution, what is excluded, how long that data is retained, and what options exist for customers with legal, compliance, or governance constraints.

The upcoming EU AI Act only makes that need for clarity more important. Customers should not have to infer scope from high-level language when the real question is whether search activity, configuration patterns, prompts/interactions, or other derived signals may still be used without a full opt-out path.

If others are seeing the same issue, I would welcome additional voices here. At this point, I think the ball is really in Atlassian’s court to respond directly on a few narrow points:

- what specific data elements fall under metadata contribution
- whether Premium customers have any non-Enterprise path to fully exclude that data
- whether any exception or review process exists for compliance-sensitive organizations
- what documentation Atlassian can provide so customers can properly assess this internally

If these concerns are becoming collective rather than isolated, a direct response from Atlassian would be the most helpful next step.

Gaurav Jain_wfvad4

Hi Cameron - thank you for your post and the questions above. Here is a summary of responses to the questions above.

Is Enterprise really the only standard way to fully disable metadata contribution?
1. In addition to customers with at least one Enterprise plan or trial, customers with specific compliance requirements may see a different experience in Atlassian Administration.
  
  To confirm your data contribution settings, navigate to Atlassian Administration > Security > Data contribution. If you have additional questions or concerns, please contact Atlassian Support.
If a Premium customer disables all available in-app data contribution settings, what data can still be used under metadata contribution?
1. All eligible data that is classified as metadata content attributes and common patterns will remain in-scope for data contribution. For details on what constitutes metadata, please refer to the examples we’ve provided in our documentation.
How broad is “metadata” in practice? Are search activity, naming patterns, workflow/configuration patterns, and Rovo interaction patterns included in that scope?

Yes, all of the examples you’ve listed would be in-scope for metadata contribution. As a reminder, common patterns are derived only from the following types of in-app data:

search queries and results
prompts and responses in Rovo Chat
configuration items you define (for example, names of custom fields in Jira)

In addition to common patterns, content attributes are statistical characteristics, numeric fields, and derivatives of your in-app data.

For metadata examples, please refer to our documentation.

What specific exclusion path exists for compliance-sensitive customers that do not have Enterprise, if any?
1. Please refer to our FAQs for details on exclusions available to customers with specific compliance requirements.
  
  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. These exclusions are not limited to customers with Cloud Enterprise plans. If a customer qualifies for exclusion based on the criteria detailed above, they will automatically be excluded from data contribution. If you have more questions, please contact Atlassian Support.
How can an organization administrator find out if their organization has been excluded from data contribution?
1. Organization administrators can verify whether their Atlassian organization is excluded from data contribution by navigating to Atlassian Administration > Security > Data contribution. If the Atlassian organization is excluded due to specific compliance requirements, there will be no option to opt-in to data contribution settings as an intentional safeguard.
Can you confirm whether exclusions are automatic or require a request/review process + Who customers should contact to evaluate eligibility
1. Exclusions for Atlassian organizations with specific compliance requirements are automatically applied, regardless of the active plan(s) in your Atlassian organization. If an organization administrator has at least one active trial or plan of the in-scope Atlassian apps, they should have received an email notification and in-app banner with details on their available data contribution settings. If you aren’t an organization administrator, we recommend you connect with them first to confirm. If you and your admin team need additional support, please contact Atlassian Support.
Can you confirm whether similar accommodations exist for other compliance-driven customers on Premium?
1. We intentionally designed our approach to serve the broadest set of customer needs by aligning with the most common compliance requirements we see across our customer base.
  
  Therefore, Atlassian cloud organizations with the following offerings are excluded:
  - 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.
  
  These exclusions are not based on the highest active plan or trial, and are not limited to customers with an Enterprise plan. If you have additional compliance-driven requirements, please contact Atlassian Support so we can discuss your unique situation.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

data

metadata

in-app