Atlassian · Atlassian Sub-Processors · View original document ↗

Subprocessor Change Notification

Medium severity Medium confidence Inferredfromcontext Unique · 0 of 352 platforms
Get alerted the next time Atlassian changes these terms. Get same-day alerts →
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for Atlassian Monitor emails you the same day this changes. The archive stays free.
Get same-day alerts →

Get the weekly 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. No account.

Document Record

What it is

Consistent with Atlassian's DPA, this list represents the mechanism through which Atlassian discloses subprocessor additions and replacements, with customers entitled to receive advance notice and to exercise objection rights as specified in the DPA.

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision establishes the operational mechanism for GDPR Article 28(2) compliance, requiring Atlassian to provide prior notice of subprocessor changes and permitting customers to object to new subprocessors before they begin processing customer data.

Interpretive note: The specific notice period, objection mechanism, and consequences of objection are governed by each customer's individual DPA with Atlassian and are not stated in this public subprocessor list.

Consumer impact (what this means for users)

This provision establishes that customers are entitled to advance notice when Atlassian adds or replaces a subprocessor, and may object to such changes under the terms of their DPA. The agreement requires customers to monitor this list or subscribe to change notifications to exercise this right in practice.

What you can do

⚠️ These actions may provide transparency or partial mitigation but may not fully address the underlying issue. Effectiveness varies by jurisdiction and individual circumstances.
  • Export Your Data
    Within 30 days
    Monitor the Atlassian subprocessor list for changes and, upon receiving a change notification per your DPA, review the new subprocessor against your data processing requirements and submit any objection within the notice period specified in your DPA.

Cross-platform context

See how other platforms handle Subprocessor Change Notification and similar clauses.

Compare across platforms →

Monitoring

Atlassian has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
Atlassian subprocessors who process customer data.

Excerpt from Atlassian's Sub-Processors

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

1) REGULATORY LANDSCAPE: GDPR Article 28(2) requires that data processors obtain prior specific or general written authorization from the data controller before engaging subprocessors, and requires notification of intended changes. Failure to provide adequate notice could constitute a breach of the processor's Article 28 obligations, triggering supervisory authority scrutiny. UK GDPR imposes equivalent requirements. 2) GOVERNANCE EXPOSURE: Medium. The practical enforceability of the objection right depends on the notice period specified in the DPA and whether Atlassian's notice mechanism (email notification, public webpage update) constitutes adequate prior notice under applicable law. Customers with short objection windows may have limited practical ability to object before a new subprocessor begins processing. 3) JURISDICTION FLAGS: EU and UK customers have the strongest statutory basis for exercising objection rights under their respective data protection laws. Australian and US customers' objection rights depend entirely on their contractual DPA terms, as no equivalent statutory right applies in those jurisdictions. 4) CONTRACT AND VENDOR IMPLICATIONS: DPAs should specify a minimum advance notice period for subprocessor changes (commonly 30 days), the mechanism for delivering notice (email to a designated contact), and the process and consequences for exercising an objection. Procurement teams should confirm that the designated notification contact is actively monitored. Where the DPA permits Atlassian to continue using a new subprocessor absent an objection within the notice period, the practical consequence of not monitoring the list is that new subprocessors will be deemed approved. 5) COMPLIANCE CONSIDERATIONS: Legal teams should establish an internal process for reviewing subprocessor change notifications, including a defined review timeline and escalation path. Changes affecting AI subprocessors or subprocessors in new jurisdictions may require updated Transfer Impact Assessments. Records of processing activities should be updated to reflect any subprocessor changes.

Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Start Professional · $99/mo Start with Monitor · $29/mo

Provision details

Document information
Document
Atlassian Sub-Processors
Entity
Atlassian
Document last updated
July 6, 2026
Tracking information
First tracked
July 7, 2026
Last verified
July 7, 2026
Record ID
CA-P-013473
Document ID
CA-D-00938
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
c0e40771c27ef2ab6cb0610288266f89dd934528062513e5a5324aee9f29e429
Analysis generated
July 7, 2026 00:31 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Atlassian
Document: Atlassian Sub-Processors
Record ID: CA-P-013473
Captured: 2026-07-07 00:31:59 UTC
SHA-256: c0e40771c27ef2ab…
URL: https://conductatlas.com/platform/atlassian/atlassian-sub-processors/provision/CA-P-013473/subprocessor-change-notification/
Accessed: July 23, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Governance intelligence across arbitration, AI governance, data rights, indemnification, and retention
Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.
Start Professional · $99/mo Start with Monitor · $29/mo

Frequently Asked Questions

What does Atlassian's Subprocessor Change Notification clause do?

This provision establishes the operational mechanism for GDPR Article 28(2) compliance, requiring Atlassian to provide prior notice of subprocessor changes and permitting customers to object to new subprocessors before they begin processing customer data.

How does this clause affect you?

This provision establishes that customers are entitled to advance notice when Atlassian adds or replaces a subprocessor, and may object to such changes under the terms of their DPA. The agreement requires customers to monitor this list or subscribe to change notifications to exercise this right in practice.

Is ConductAtlas affiliated with Atlassian?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Atlassian.