Atlassian Flips the Switch: Jira and Confluence Data Now Feeds AI Training by Default

After months of warnings, community pushback, and a competitive marketing barrage from rivals, the deadline has arrived: as of August 17, 2026, Atlassian is changing how it uses customer data across its cloud products. Customer metadata and in-app data from Jira, Confluence, and the rest of the Atlassian cloud suite will now be used by default to improve the company’s apps and AI experiences for all customers — unless administrators act, and in some cases, even if they do.

For the millions of teams that run their engineering, planning, and documentation on Atlassian Cloud, this is not a hypothetical policy debate anymore. It is a live change to how one of the world’s largest work-management platforms treats the content sitting inside its systems.

What exactly changed

Atlassian’s “data contribution” framework, first announced in spring 2026 and documented on its trust center, splits collected data into two distinct categories — each with a very different risk profile and, crucially, different opt-out rights.

Metadata includes information about how products are used — events, settings, and interaction patterns. Atlassian says this data is de-identified and aggregated before use, and that it does not contain health, location, workforce, or financial information. The catch: for Free, Standard, and Premium customers, metadata contribution is always on and cannot be disabled. Only Enterprise customers can opt out of metadata collection.

In-app data is the more sensitive category. It can include the actual content users create — Confluence page content, Jira issue text, and similar material. This tier can be turned off by any organization admin, regardless of plan, via Atlassian Administration → Security → Data contribution.

That asymmetry — “your content can be excluded, but your usage patterns cannot” — has been the core of the community’s objections since the policy was announced. Critics argue that for non-Enterprise customers, there is no truly complete opt-out.

Who is automatically excluded

Not every organization is affected. Atlassian’s FAQ states that cloud organizations associated with government entities are excluded from data contribution entirely. Industry analysis and Atlassian community documentation indicate that certain other regulated configurations — such as HIPAA-aligned deployments and some financial-services setups — are also excluded from collection.

For everyone else, the August 17 date marked the end of the grace period. Organizations that did not toggle off in-app data collection before the deadline will now have their content flowing into Atlassian’s AI improvement pipelines.

Opting out after the deadline — and what it actually does

Administrators who missed the deadline can still act, but the mechanics matter. According to Atlassian’s documentation and third-party analyses, opting out of in-app data contribution triggers removal of in-app data within 30 days, and content attributes within 90 days. Atlassian has also committed to retraining models that were previously trained on an organization’s data within that 90-day window.

One figure that has drawn particular attention: collected data may be retained for up to seven years under the policy’s terms. Even if you opt out today, data already gathered doesn’t vanish instantly — and the retention horizon is long.

Rivals smell blood

The change has been a marketing gift for Atlassian’s competitors. GitLab published a bluntly titled blog post — “Atlassian will train on your data: Opt out with GitLab” — walking through the policy’s details and positioning GitLab’s own data practices as the safer alternative for privacy-conscious organizations. Expect that messaging to intensify now that enforcement has begun.

The community reaction has been simmering for months. Obsidian CEO Stephan Ango amplified the issue to his followers with a simple summary: unless you opt out by August 17, 2026, data from Jira and Confluence will automatically be used for AI training. Reddit threads on r/jira and Atlassian’s own community forums filled with administrators asking whether Premium plans could escape metadata collection — and discovering they could not.

The broader pattern

Whatever Atlassian’s intent — and the company frames this as building “data practices for responsible AI” — the move fits a familiar industry playbook. Zoom walked back a similar terms-of-service change in 2023 after public outcry. Slack, Google, and Microsoft have each faced scrutiny over how customer content feeds model improvement. The difference now is the follow-through: where earlier backlashes forced retreats, vendors in 2026 are increasingly holding the line, structuring policies so that the default favors collection and the burden of protection falls on the customer.

For AI-hungry product teams, this tension is structural. Features like Atlassian’s AI experiences and Rove-style agents get materially better when trained on realistic work data — tickets, specs, retros, documentation. That improvement is precisely why the data is valuable, and precisely why customers are uneasy. A Jira issue can contain architecture notes, security decisions, customer names, and roadmap details all in one place. Aggregation and de-identification reduce some risks, but they are not the same as consent.

What teams should do now

1. Check your data contribution settings today. Atlassian Administration → Security → Data contribution. If in-app data collection is on and you don’t want it, turn it off — removal timelines run from there.
2. Know your tier’s limits. If you’re on Free, Standard, or Premium, metadata collection stays on. If that’s unacceptable, Enterprise is the only contractual exit, or migration to another platform.
3. Audit what lives in Confluence and Jira. Sensitive material that shouldn’t be in a cloud work tool is now a bigger liability than it was last week.
4. Watch for follow-on changes. Opt-out mechanics, exclusions, and retention terms have already shifted several times since April; treat current terms as a moving target.
5. Ask whether the trade is worth it. Some organizations may genuinely prefer better AI features over stricter data boundaries. That’s a legitimate choice — but it should be an explicit one made by admins, not a default inherited from a deadline that passed quietly.

The bottom line

August 17, 2026 is a quiet but real inflection point for enterprise AI. Atlassian is betting that customers will accept default data contribution in exchange for better AI, and that the outcry will fade as the features improve. Rivals are betting the opposite. The organizations most exposed are the ones that haven’t looked at their settings yet — because as of today, silence counts as consent.