Atlassian collects personal information you directly provide (like your name and email), information generated by your use of their products (like files you upload and messages you send), and information from third-party sources such as data enrichment providers.
This analysis describes what Atlassian's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
The policy states that content created or uploaded within Atlassian products, including messages and files, is collected as personal information, meaning material you create in Jira or Confluence may be processed under this policy.
Users' names, email addresses, job titles, billing information, device identifiers, IP addresses, usage activity, and content uploaded or created within Atlassian services are all within the stated scope of collection. This includes content shared in Confluence pages, Jira tickets, and similar collaborative workspaces.
How other platforms handle this
to request that your data be transferred to a third party (data portability)
Your organization may allow you to access and export your data in order to back it up or transfer it to a service outside of Google.
To stop us collecting your location information, you can update your device settings, stop using the Service, or uninstall our mobile apps.
"We collect information about you when you provide it to us, when you use our Services, and when other sources provide it to us, as further described below. We collect information about you when you input it into the Services or otherwise provide it directly to us. We collect content you provide while using the Services. This includes messages you send and receive, files and other content you upload to the Services.Excerpt from Atlassian's Privacy Policy
(1) REGULATORY LANDSCAPE: Collection of content data including messages and files may engage GDPR Article 5 data minimization and purpose limitation principles, as well as CCPA categories for professional and employment-related information when used in …
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
The policy states that content created or uploaded within Atlassian products, including messages and files, is collected as personal information, meaning material you create in Jira or Confluence may be processed under this policy.
Users' names, email addresses, job titles, billing information, device identifiers, IP addresses, usage activity, and content uploaded or created within Atlassian services are all within the stated scope of collection. This includes content shared in Confluence pages, Jira tickets, and similar collaborative workspaces.
ConductAtlas has identified this type of provision across 290 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Atlassian.