Jira

Atlassian says Jira customer data is not used to train, fine-tune, or improve AI models or services.

Atlassian says provider request data is processed to generate a response and then returned without retention for training.

Organization admins can deactivate Atlassian Intelligence when they do not want Jira data processed with AI features.

Project permissions still limit which users and systems can reach issue content before AI features are even enabled.

AI features still process Jira issues, comments, and related data to generate responses unless disabled by admins.

Atlassian says AI provider requests are processed securely and not retained for training.

Jira project permissions and organization roles help limit who can view issues and attachments.

Atlassian documents privacy-rights, disclosure categories, and information-control paths.

Third-party services are typically connected by customer choice rather than forced as part of basic Jira use.

Jira data can still flow through Atlassian subprocessors, marketplace apps, organization admins, and legal requests.

Linked third-party services and other Atlassian products can widen disclosure beyond a single project team.

Atlassian and third-party partners use cookies and tracking technologies for analytics and advertising.

Atlassian uses information about service use for marketing and targeted advertising of products that may interest users.

Jira project and organization permissions keep core issue data separate from public ad-style surfaces.

Atlassian documents information rights and some communication controls for users.

Jira is primarily an internal work-management product rather than a consumer social or ad-targeting surface.

Organization admins can manage Jira product data and user access.

Atlassian documents privacy-rights requests including access, deletion, and restriction where applicable.

The reviewed AI flow says provider request data is not retained for training.

Project and organization governance make retention a managed process rather than only a per-user cleanup task.

Deletion and retention still depend on organization configuration, apps, backups, and compliance needs.

Marketplace apps and linked services can create extra copies or parallel retention obligations.

Admins can deactivate Atlassian Intelligence across Jira environments.

Project permissions and organization roles give teams practical control over issue visibility and access.

Privacy-rights requests and information-control paths are documented for Atlassian account holders.

Users and organizations can limit exposure by choosing which apps and third-party services to connect.

End-user privacy controls are still limited inside managed Atlassian organizations.

Important settings are split across Jira, Atlassian account, and organization administration surfaces.