SAN FRANCISCO, August 17, 2026, 10:05 PDT
- Atlassian started new customer-data contribution terms on Monday.
- All cloud plans have the option to turn off in-app content contribution.
- Turning off metadata contribution is only available to Enterprise organizations.
Atlassian Corporation (NASDAQ:TEAM) rolled out new customer-data contribution settings starting Monday. The update lets eligible metadata and content from user activity help boost products and AI features for other customers.
Control is the main difference. Organization admins on all cloud plans have the option to reject in-app data sharing. But just Enterprise accounts can also switch off metadata contribution.
So now, three of Atlassian’s four plan tiers don’t offer a way to opt out of metadata. Free and Standard start with in-app contributions turned on. Premium and Enterprise launch with it off.
| Top cloud plan | Default metadata | Metadata opt-out | Default in-app data | In-app data opt-out |
|---|---|---|---|---|
| Free | Enabled | No | Enabled | Allowed |
| Standard | Enabled | No | Enabled | Allowed |
| Premium | Enabled | No | Disabled | Allowed |
| Enterprise | Enabled | Allowed | Disabled | Allowed |
The top active plan in each cloud org sets the defaults, even for trials. Admins can check these in Atlassian Administration under Security, then Data contribution. Each organization needs to be reviewed on its own.
Metadata covers things like stats and regular patterns. These can be Jira story points, how complex a Confluence page is, or what topics people search for a lot in Rovo. Atlassian says it strips out names and emails and puts the data together.
In-app data is straightforward. This covers Confluence page content, Jira titles, descriptions and comments. It also includes custom workflows, status names and emoji names.
| Data category | Verified examples | Company safeguards | Admin control |
|---|---|---|---|
| Metadata: content attributes | Story points, page complexity, sprint dates, service levels | De-identified, only shared in aggregate | Enterprise only |
| Metadata: common patterns | Top search terms, Rovo Chat subjects, config patterns | Leaves out unusual org-level patterns | Enterprise only |
| In-app data | Page content, work-item titles, descriptions, comments, custom labels | De-identified, aggregated with others before cross-customer use | All plans |
Arseny Tseytlin, who runs product communications at Atlassian, said lower-tier metadata contribution is “always on” and customers in those tiers don’t have an opt out. The Register
The first group includes Jira, Confluence and Jira Service Management, as well as platform apps like Rovo, Assets and Analytics. Products like Loom, Trello, Bitbucket, Data Center offerings and Marketplace apps aren’t part of it yet.
| Product or organization | Current status | Important detail |
|---|---|---|
| Jira, Confluence, Jira Service Management | Included | Settings are set at the organization level |
| Rovo and other platform apps | Included | Same organization settings manage these |
| Loom, Trello, Bitbucket | Not included yet | Atlassian says it will give a heads up before any changes |
| Data Center and Marketplace apps | Not included | No data is shared as part of this change |
| Government, Isolated Cloud, HIPAA, CMK or BYOK | Excluded | Contribution can’t be switched on for these |
Atlassian said customer data that users provide isn’t used to train language models hosted by third parties. Those vendors work under zero-data-retention deals. Atlassian may fine-tune open-source models on its own systems using certain metadata.
Switching off contribution doesn’t remove data right away. Atlassian says in-app data will be taken out of improvement datasets within 30 days. Metadata goes within 90 days, and models using that data get retrained.
| Milestone or action | Timing | Status |
|---|---|---|
| Started rolling out settings | April 16, 2026 | Done |
| Settings rollout wrapped up | May 19, 2026 | Done |
| New terms and data policy in force | August 17, 2026 | Active |
| Remove in-app data if user opts out or deletes | Within 30 days | Pledged |
| Remove metadata after user opts out or deletes | Within 90 days | Pledged |
Risks: The company says it controls safeguards and data removal, but that’s their own claim. Customers have to judge for themselves if de-identification works for their security. If an admin leaves a setting unchecked, eligible content could be used in product improvement across customers until someone updates it.
The immediate work is on admin steps. Free and Standard users need to check the in-app toggle. Each organization should keep a record of which plan manages its defaults.
Related articles: News
