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; } } }

How can a free-tier healthcare organization opt out of Data Contribution / AI training?

Liam_eycg69

We are a dental practice using Confluence on the free tier. We recently received an email from Atlassian stating that our organization's data may be used for AI training purposes.

As a dental practice, we are a covered entity under HIPAA, which restricts how our data can be used by third parties. We do not consent to our data being used for AI training or data contribution.

However, we are unable to find the "Data Contribution" settings in our organization's administration panel — we believe this option may not be available on the free tier.

Can anyone advise on how a free-tier customer in a regulated healthcare industry can formally opt out? Is there a way for Atlassian to manually exclude our organization, or is upgrading to a paid plan the only path forward?

Accepted answers

Liam_eycg69

UPDATE: 25/07/26

I just got this email for Atlassian yesterday:

Screenshot 2026-07-25 at 11.14.46.png

so ... result? I'm not quite sure how our org got excluded - we signed a BAA, are UK-based in healthcare, so it could have been any of these which did the trick? To clarify: we are still on free tier and so were not able to tag any of our apps as holding HIPAA data.

In any case, I'm happy with the result but I'm not sure what to advise other people in a similar situation to do to get this result! I got this email months later after not making any changes to my org settings.

All comments

marc -Collabello--Phase Locked-

Most likely you won't get an answer here. My recommendation is to contact support.

Liam_eycg69

Correct me if I'm wrong, but I don't think free tier accounts can contact support!

Bill Sheboy

Hi @Liam

Short answer: Based upon reading Atlassian materials and experimentation, free license level customers apparently have little to no control over Atlassian use of their data in this manner at this time.

Announced in an email to Org / Product Admins this week for "Upcoming changes to how Atlassian uses your data", there will be new settings to impact Data Contributions at various license levels. That information, and included knowledgebase (KB) links, suggest updating your settings before 1 May 2026 for the changes applying in August 2026. They do not describe what is currently happening regarding data contribution to "AI" tooling / training.

However, the described settings in the KB article do not appear accessible for a free license level. Perhaps they will appear as we get closer to the August 2026 threshold.

https://support.atlassian.com/security-and-access-policies/docs/data-contribution-settings/

In my experience, this seems a common situation for free license, internet products: the customer has limited expectations to owning the data entered in the product.

There is documentation on which Org configurations / licensing will be excluded from data contribution:

https://support.atlassian.com/security-and-access-policies/docs/data-contribution-settings-availability/#Atlassian-organizations-that-don%E2%80%99t-contribute-data

Kind regards,
Bill

Arkadiusz Wroblewski

@Liam

I don’t want to sound like I’m doing product placement, but if I were in your position, I would seriously consider spending a bit more on at least a Standard or Premium subscription.

Especially in a healthcare organization, where you usually need stronger control over your tools, permissions, and overall setup, the extra investment is often worth it.

Kris Klima _K15t_

Hi @Liam

You can use a no-login option to contact Atlassian and try argue a against data collection

Visit our support page: https://www.atlassian.com/company/contact
Select “Pricing, billing and licensing.”
Continue without logging in.
Enter your email.
In “How can we help you,” select “Other.”
Skip the URL fields if they don’t apply.
Describe your issue in “Your Question.” This will open a ticket with Atlassian Support.

Having said that.....

Compliance is a two way street - it governs what tools (and their vendors) can collect but also puts burden on users to select tools that are compliant in regards to specific industry regulations.

I don't need a FIM certified motorcycle helmet for regular traffic but I need one to ride on a race track (regulatory, insurance, etc. reasons).

Atlassian would argue that they do offer a no-data-collection option that is HIPAA compliant - https://www.atlassian.com/trust/compliance/resources/hipaa - on their Enterprise tier.

What I would do

Contact Atlassian using the no-login option and ask what data are collected.

There is a good chance that the scope of collected data is different across tiers and/or the data collected do not interfere with HIPAA requirements that apply to your use case.

From experience, non-Enterprise Confluence is used in health care (again, the devil might be in the details...) but there are Marketplace apps that teams use to ensure compliance (HIPAA, QMS, etc.).

For example, there's Password for Confluence by Acemood that encrypts your data and claims HIPAA compliance. And the app is free for up to 10 users. So you can reach out to the vendor and discuss your specific use case and compliance requirements.

marc -Collabello--Phase Locked-

Here's more information: Atlassian’s new data collection policy protects rich customers while AI eats the rest

Kate C_

Hi @Liam, Thanks for your questions - I'm happy to clarify. First up, data contribution settings are gradually rolling out and will be available in Atlassian Administration by May 19, 2026, so you may not see them in your instance just yet. Once your settings are available, you can review and manage them at any time.

You mentioned you are in the healthcare industry. To honour our customers' compliance requirements, Atlassian doesn’t use metadata or in-app data from Atlassian Cloud organisations that have notified us that HIPAA compliance is required. If you believe this is relevant for your organisation, please refer to our HIPAA Implementation Guide for the steps to take to configure your organisation for HIPAA compliance.

Lastly, we’ve gone ahead and created a support ticket on your behalf, so our support team can follow up with you directly. You should have received an email with ticket number JST-1301266; one of our team members will be in touch shortly.

Arend Feenstra

@kris do you have any information, how does the collection of metadata relate to the legal provisions of European GDPR legislation? Collecting 7 years of metadata seems really excessive to me. At the same time I am looking for which exact fields Jira uses for meta-app data.

Liam_eycg69

UPDATE: 25/07/26

I just got this email for Atlassian yesterday:

Screenshot 2026-07-25 at 11.14.46.png

Muhammad Awais

Thanks for the detailed clarification. Since this is a healthcare use case, I agree that confirming the organization’s HIPAA status and data-handling configuration is more important than simply upgrading plans.

Welcome!

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

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud