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.
Subscriptions renew automatically at Atlassian's then-current rates unless either party provides notice of non-renewal before the current Subscription Term ends. The renewal period mirrors the prior term for terms under twelve months, or defaults to twelve months for longer terms.
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
This provision establishes an automatic renewal obligation at rates that may differ from the original Order price, creating a billing exposure if Customer fails to provide timely non-renewal notice before each Subscription Term ends.
Under this clause, subscriptions renew automatically at Atlassian's then-current rates unless the Customer actively provides non-renewal notice before the Subscription Term ends through account settings, support contact, or written notice.
Cross-platform context
See how other platforms handle Automatic Subscription Renewal and similar clauses.
Compare across platforms →Monitoring
Loom has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"Unless otherwise specified in an Order and subject to the Product, Support or Advisory Services continuing to be generally available, a Subscription Term will automatically renew at Atlassian's then current rates for: (i) if Customer's prior Subscription Term was for a period less than twelve (12) months, another Subscription Term of a period equal to Customer's prior Subscription Term, or (ii) if Customer's prior Subscription Term was for twelve (12) months or more, twelve (12) months. Either party may elect not to renew a Subscription Term by giving notice to the other party before the end of the current Subscription Term. Customer must provide any notice of non-renewal through account settings in the Products, by contacting Atlassian's support team or by otherwise providing Atlassian notice.Excerpt from Loom's Terms of Service
1. REGULATORY LANDSCAPE: Auto-renewal terms for business software subscriptions may engage FTC Act Section 5 unfair or deceptive practices standards in the US, particularly where rate changes at renewal are not prominently disclosed. California's Automatic Renewal Law (Business and Professions Code Section 17600 et seq.) imposes specific disclosure and consent requirements for automatically renewing contracts; applicability to B2B agreements under California law involves factual and legal nuance that may warrant counsel review. No specific EU-level regulation directly governs B2B auto-renewal terms, though EMEA customers contracting under Irish law may consider local commercial law requirements. 2. GOVERNANCE EXPOSURE: Medium. The provision states renewal occurs at Atlassian's then-current rates, which may differ from rates in the original Order. Enterprise customers on multi-year agreements transitioning to annual renewal cycles may face rate adjustments without a separate notification requirement beyond standard Agreement update processes. Internal procurement controls should track Subscription Term end dates to ensure non-renewal notice is timely. 3. JURISDICTION FLAGS: California-domiciled business customers face heightened exposure under California's Automatic Renewal Law, though that statute's applicability to purely B2B enterprise agreements is not settled. EMEA customers contracting under Irish law should evaluate whether local commercial law creates additional disclosure obligations for Atlassian or additional cancellation rights for Customer. 4. CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should confirm that internal contract management systems capture Subscription Term end dates and renewal notice deadlines. The provision states notice may be provided through account settings, support contact, or written notice, giving Customer multiple channels but requiring proactive action. The credit card billing provision in Section 10.1(f) operates in conjunction with this renewal clause, authorizing charges to stored payment methods on renewal. 5. COMPLIANCE CONSIDERATIONS: Legal teams should verify that budget approval workflows account for potential rate changes at renewal. Organizations subject to California law should assess whether the Automatic Renewal Law disclosure requirements are satisfied by Atlassian's current onboarding and renewal notification practices. Compliance teams should review whether the 30-day modification notice period in Section 20.9 is adequate to assess rate-related changes before renewal.
Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision establishes an automatic renewal obligation at rates that may differ from the original Order price, creating a billing exposure if Customer fails to provide timely non-renewal notice before each Subscription Term ends.
Under this clause, subscriptions renew automatically at Atlassian's then-current rates unless the Customer actively provides non-renewal notice before the Subscription Term ends through account settings, support contact, or written notice.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Loom.