Atlassian shares personal data with third-party vendors and service providers who help operate its products, including potentially cloud infrastructure, analytics, and AI service partners.
This analysis describes what Loom'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
Data shared with third-party sub-processors leaves Atlassian's direct control and creates a chain of data handling obligations that may be difficult for individual users to trace or audit.
Interpretive note: Specific sub-processor sharing clause language could not be extracted from the truncated HTML document; this provision is inferred from Atlassian's known privacy policy structure and standard enterprise SaaS disclosure practices.
Personal data including account information, usage patterns, and potentially video content may be shared with third-party providers under Atlassian's sub-processor framework; users who want to know which specific vendors receive their data should review Atlassian's sub-processor list.
How other platforms handle this
We may share your personal data with third-party vendors, service providers, contractors, or agents who perform services for us or on our behalf and require access to such information to do that work. We may also share your personal data with advertising partners to display relevant advertising to y...
We may share your personal information with third-party vendors and service providers that perform services on our behalf, such as payment processing, data analysis, email delivery, hosting services, customer service, and marketing assistance.
We may share your information with third-party advertising partners to provide you with targeted advertising. We also work with third-party analytics providers who help us understand how users interact with our Services. These third parties may use cookies, web beacons, and similar tracking technolo...
Monitoring
Loom has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
1) REGULATORY LANDSCAPE: GDPR Article 28 requires that data processors engage sub-processors only under binding contractual terms, and data controllers must be informed of sub-processor changes. CCPA requires that service providers receiving personal data are contractually restricted from using that data for purposes outside the service. FTC Act Section 5 covers material misrepresentations about third-party data sharing. 2) GOVERNANCE EXPOSURE: Medium. Sub-processor frameworks are standard in enterprise SaaS but the breadth of Atlassian's product suite and the sensitivity of Loom video content means the sub-processor list warrants specific review. Changes to sub-processors without adequate notice could affect enterprise DPA compliance. 3) JURISDICTION FLAGS: EU/EEA users have rights under GDPR to be informed of sub-processors and the transfer mechanisms in place. California users may request disclosure of categories of third parties to whom personal information is disclosed. Cross-border transfers to US-based sub-processors require appropriate safeguards under post-Schrems II standards. 4) CONTRACT AND VENDOR IMPLICATIONS: Enterprise procurement should request and review Atlassian's current sub-processor list, confirm notification procedures for sub-processor changes, and assess whether audit rights extend to material sub-processors. Particular attention should be paid to AI and transcription service sub-processors given the sensitivity of Loom content. 5) COMPLIANCE CONSIDERATIONS: Compliance teams should map Atlassian sub-processors against their own third-party risk management frameworks. Any sub-processors located in jurisdictions without EU adequacy decisions require specific transfer mechanism confirmation. Organizations with sector-specific data restrictions (e.g., legal privilege, healthcare, financial confidentiality) should assess whether Loom's sub-processor chain is compatible with those restrictions.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
ConductAtlas detected a major restructuring of Meta’s privacy policy that removed detailed consumer rights disclosures and relocated them to separate documents.
Your genetic data may be transferred to a new owner as a business asset. Here is what the Terms of Service actually say and what you can do right now.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
Data shared with third-party sub-processors leaves Atlassian's direct control and creates a chain of data handling obligations that may be difficult for individual users to trace or audit.
Personal data including account information, usage patterns, and potentially video content may be shared with third-party providers under Atlassian's sub-processor framework; users who want to know which specific vendors receive their data should review Atlassian's sub-processor list.
ConductAtlas has identified this type of provision across 3 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Loom.