What changed in the terms you agreed to

New AI Features terms clarify how GitHub uses your data for AI training with opt-out options, define AI-related terms, update content ownership and license grants, and add detailed rules on private repository access and public repository content.

• high

  License grant expanded to include AI training

  You now grant GitHub and its Affiliates rights to use Your Content to train and improve AI and machine learning models, explicitly including AI Features, clarifying this use is not a sale or restricted transfer.

  Before

  You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time.

  After

  You grant GitHub and our Affiliates the right to store, host, archive, parse, display, and make copies of Your Content as necessary to provide, develop, and improve the Service, including by training AI Features, and for the purpose of training, developing, and improving artificial intelligence and machine learning models and technologies of our Affiliates. … For the avoidance of doubt, use of Your Content to develop, train, and improve artificial intelligence and machine learning models and technologies of GitHub and our Affiliates is within the scope of this license and does not constitute a sale or other restricted transfer of Your Content.

  Quote taken word for word from the document by the monitor.

• high

  New section on AI Features, training, and your data with opt-out

  A new section details how GitHub uses your Inputs and Outputs to train AI models unless you opt out, clarifies ownership of Input and Output, disclaimers about Output accuracy, and your responsibility for Output use and indemnity.

  Before

  Not in the old version.

  After

  J. AI Features, Training, and Your Data 1. Applicability This section applies to all AI Features unless a specific feature has additional terms that expressly modify them. The training and data-use provisions in Section J.3 apply only to individual licenses. If your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement, those agreements govern the use of your data in connection with AI Features and Section J.3 does not apply to you. 2. Ownership GitHub does not claim ownership of your Input or Output. Output may contain material that resembles code or content in the model's training data or that is subject to third-party copyrights or open source license terms. You are responsible for determining whether your use of Output requires a third-party license and for complying with any such license. 3. Development and Improvement Using Your Input and Output We use your Inputs to generate Outputs and provide the AI Features. You also grant GitHub and its Affiliates a license to collect and use your Inputs and Outputs to develop, train and improve artificial intelligence and machine learning models and technologies including those that power AI Features, unless (a) you opt out through your account settings, or (b) your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement. If you opt out, GitHub will not collect or use your Inputs and Outputs for the purposes described in this paragraph from the effective date of your opt-out going forward. Unless you opt out, GitHub's Affiliates may use your Inputs and Outputs under this license in accordance with their applicable privacy and contractual obligations. This license does not, however, permit GitHub or its Affiliates to share your Inputs or Outputs with third-party AI model providers for their own independent model training purposes. The license in this Section J.3 is in addition to, and does not limit, the rights granted to GitHub and its Affiliates under Sections D.4 and D.8. This license does not extend to Your Content stored in repositories that are not provided as Input to an AI Feature. The opt-out right described in this section applies solely to the use of your Inputs and Outputs as described in this section, and does not apply to the license granted in Sections D.4-D.8 or to any Content that does not constitute Input or Output (including Content stored in public repositories). 4. Disclaimers Output is provided "as-is" and subject to the disclaimers in Section O. Without limiting Section O: Output may be inaccurate, incomplete, or non-functional. Output may resemble third-party code, including code under open source licenses. We do not guarantee that Output is free of errors, vulnerabilities, or intellectual property claims. You are responsible for reviewing, testing, and validating any Output before use. 5. Your Responsibility and Indemnity You are responsible for your use of Output, including ensuring it complies with applicable law and does not infringe third-party rights. Your indemnity obligations in Section Q apply to your use of AI Features and Output, including claims arising from Output you incorporate into your products or services.

• high

  Detailed rules on access to private repository content

  GitHub clarifies that private repository content is confidential and will only be accessed with your consent or for specific reasons including security, support, legal compliance, and if you provide content as Input to AI Features, with opt-out options for AI use.

  Before

  Short version: We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.

  After

  Short version: We treat the content of private repositories as confidential, and we only access it as described in Section E.3 below—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent. … You control access to the content of your private repositories. … GitHub considers the contents of private repositories to be confidential to you, as set forth in Section E.2, and GitHub personnel will not access private repository content without your consent except in the following circumstances: … - for security purposes; … - for automated scanning or manual review for known vulnerabilities, active malware, or other content known to violate our Terms of Service; … - to assist the repository owner with a support matter; … - to maintain the integrity of the Service; or … - to comply with our legal obligations if we have reason to believe the contents are in violation of the law. … - If you provide your private repository content as Input to AI Features, we may use that Input to provide, develop, train, and improve the Service, including AI Features. … Your ability to opt out under Section J.3 applies to this use of private repository content. … We will not otherwise use your private repository contents to develop or improve the Service.

  Quote taken word for word from the document by the monitor.

• medium

  New definitions for AI Features, Affiliates, and content types

  The terms add definitions for AI Feature, Affiliate (including Microsoft as an Affiliate), Content, Input, Output, User-Generated Content, and Your Content, clarifying AI-related terminology and content ownership.

  Before

  Not in the old version.

  After

  - "AI Feature" means any feature of GitHub or our Affiliates that uses machine learning or artificial intelligence to generate Output, including GitHub Copilot, Copilot Autofix, and any other feature identified as using machine learning or artificial intelligence in our documentation. … - “Affiliate” means any entity that directly or indirectly controls, is controlled by, or is under common control with a party, where "control" means having more than fifty percent (50%) ownership or the right to direct the management of the entity. … For the avoidance of doubt, Microsoft is an Affiliate of GitHub. … - "Content" means code, text, data, documentation, images, graphics, software, packages, and other materials made available through the Service. … - “Input” means any content or context provided to an AI Feature, including prompts, attachments, code in your workspace, and conversation history. … - "Output" means responses and suggestions, including code or other material, generated by an AI Feature. … - "User-Generated Content" means Content that you or other users upload, submit, or create through the Service. … - "Your Content" means User-Generated Content that you upload, submit, or create, including your modifications to Content you have forked or cloned. … It does not include the underlying Content created by others.

  Quote taken word for word from the document by the monitor.

• medium

  Clarification on private repository access

  GitHub added a statement that it accesses private repositories only as described in Section E.

  Before

  Not in the old version.

  After

  We access private repositories only as described in Section E.

• medium

  Clarification on public repository content and lawful access

  By contributing to public repositories, you direct GitHub to make that content accessible to everyone, and these terms do not restrict lawful access or use of public repository content by third parties or GitHub Affiliates.

  Before

  Not in the old version.

  After

  8. Public Repositories and Lawful Access By choosing to contribute Content to a public repository, you are choosing to and directing us to make such Content accessible to everyone on the internet. Unless specifically set forth herein, these Terms do not restrict lawful access to or use of the contents of public repositories by third parties, or by GitHub or its Affiliates.

• medium

  Terminology and content responsibility updates

  Terminology was refined (e.g., 'Personal Accounts' to 'Accounts', 'User-Generated Content' to 'Your Content'), responsibility for content clarified, and license grant language simplified and updated to reflect current practices.

  Before

  - “GitHub,” “We,” and “Us” refer to GitHub, Inc., as well as our affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees. … - The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews. … - “The User,” “You,” and “Your” refer to the individual person, company, or organization that has visited or is using the Website or Service; that accesses or uses any part of the Account; or that directs the use of the Account in the performance of its functions. … We have a few simple rules for Personal Accounts on GitHub's Service. … You may create or upload User-Generated Content while using the Service. … We are not responsible for any public display or misuse of your User-Generated Content. … We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or GitHub terms or policies. … User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms. … 3. Ownership of Content, Right to Post, and License Grants … If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post. … These license grants apply to Your Content. … If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. … The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it. … Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. … By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). … If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). … You may grant further rights if you adopt a license. … If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users. … However, you waive these rights and agree not to assert them against us, to enable us to reasonably exercise the rights granted in Section D.4, but not otherwise.

  After

  Removed.

  Quote taken word for word from the document by the monitor.

• low

  Updated section numbering and references in Access Reciprocity

  The section number for Access Reciprocity was updated from 8 to 9, and the exception clause was updated to refer to Section D.9 instead of D.8.

  Before

  8. Access Reciprocity … This Section D.8 does not apply to Access solely for the purpose of academic research or if, on the date you Access the Content, the number of monthly active users of the products or services made available by you is less than 700 million in the preceding calendar month.

  After

  9. Access Reciprocity … This Section D.9 does not apply to Access solely for the purpose of academic research or if, on the date you Access the Content, the number of monthly active users of the products or services made available by you is less than 700 million in the preceding calendar month.

  Quote taken word for word from the document by the monitor.

• low

  Updated effective date

  The effective date of the Terms of Service was updated from November 16, 2020 to April 27, 2026.

  Before

  Effective date: November 16, 2020

  After

  Effective date: April 27, 2026

• low

  Correction of section reference for injunctive relief

  The section reference for claims for injunctive relief was updated from section D.8 to section D.9.

  Before

  However, any claim for injunctive relief with respect to a violation of section D.8 may be brought in any jurisdiction.

  After

  However, any claim for injunctive relief with respect to a violation of section D.9 may be brought in any jurisdiction.

• low

  Expanded acronym for API

  The acronym API was expanded from 'Application Provider Interface' to 'Application Programming Interface'.

  Before

  Short version: You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Provider Interface), including use of the API through a third party product that accesses GitHub.

  After

  Short version: You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Programming Interface), including use of the API through a third party product that accesses GitHub.

• low

  Section letter updated for Beta Previews

  The section letter for Beta Previews was updated from J to K.

  Before

  J. Beta Previews

  After

  K. Beta Previews

• low

  Typo correction in Beta Preview feedback

  Corrected typo from 'improve of products' to 'improve our products'.

  Before

  We’re always trying to improve of products and services, and your feedback as a Beta Preview user will help us do that.

  After

  We’re always trying to improve our products and services, and your feedback as a Beta Preview user will help us do that.

• low

  Removed or replaced minor or outdated text

  Removed some single-letter summary placeholders, old definitions of Content and User-Generated Content, some redundant or outdated clauses, and updated section numbering.

  Before

  - “Content” refers to content featured or displayed through the Website, including without limitation code, text, data, articles, images, photographs, graphics, software, applications, packages, designs, features, and other materials that are available on the Website or otherwise available through the Service. … "Content" also includes Services. … “User-Generated Content” is Content, written or otherwise, created or uploaded by our Users. … "Your Content" is Content that you create or own. … You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. … You retain ownership of and responsibility for Your Content. … Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. … You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. … We need the legal right to do things like host Your Content, publish it, and share it. … This license does not grant GitHub the right to sell Your Content. … It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program. … GitHub personnel may only access the content of your private repositories in the situations described in our Privacy Statement. … L. Cancellation and Termination … M. Communications with GitHub … N. Disclaimer of Warranties … O. Limitation of Liability … P. Release and Indemnification … Q. Changes to These Terms … This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version in accordance with Section Q.

  After

  Removed.

  Quote taken word for word from the document by the monitor.

Full page and a fresh check on WhatChanged →
✓ Every change found by code is explained or listed as minor, and every quote is checked against both versions. Explanations are written by AI and reviewed by a person; the quotes are the documents' own words. 6 minor edits (dates, numbering, menus) not shown.

Cursor removed mandatory arbitration and replaced it with litigation in Texas courts, added a limitations period for claims, and updated governing law and dispute resolution procedures.

• high

  Mandatory arbitration replaced with litigation in Texas courts

  Cursor removed the entire mandatory arbitration agreement and related procedures, including class action waivers, arbitration rules, confidentiality, and opt-out rights, replacing it with litigation in specified Texas courts.

  Before

  Agreement to Arbitrate. This Dispute Resolution by Binding Arbitration section is referred to in these Terms as the “Arbitration Agreement.” You agree that any and all disputes or claims that have arisen or may arise between you and Anysphere, whether arising out of or relating to these Terms (including any alleged breach thereof), the Service, any advertising, or any aspect of the relationship or transactions between us, will be resolved exclusively through final and binding arbitration, rather than a court, in accordance with the terms of this Arbitration Agreement, except that you may assert individual claims in small claims court, if your claims qualify. Further, this Arbitration Agreement does not preclude you from bringing issues to the attention of federal, state, or local agencies, and such agencies can, if the law allows, seek relief against us on your behalf. You agree that, by entering into these Terms, you and Anysphere are each waiving the right to a trial by jury or to participate in a class action. Your rights will be determined by a neutral arbitrator, not a judge or jury. The Federal Arbitration Act governs the interpretation and enforcement of this Arbitration Agreement. You may opt out of arbitration within 30 days of account creation or of any updates to these arbitration terms within 30 days after the update has taken effect, by sending an email to legal@cursor.com from the email address used to create your account, and providing your first and last name and a clear statement of intent that you intend to exercise your right to opt out of mandatory arbitration.

  After

  Removed.

• high

  New dispute resolution and governing law provisions

  Cursor added new dispute resolution terms requiring parties to attempt informal resolution first, then allowing litigation exclusively in Texas courts, with Texas law governing the Terms, and extended these provisions to U.S. corporate affiliates.

  Before

  Not in the old version.

  After

  Governing Law, Forum Selection, Jurisdiction, and Venue. … Unless prohibited by your country’s applicable law, the laws of the State of Texas, excluding its choice of law provisions, will govern these Terms and any dispute that arises between you and Anysphere, notwithstanding any other agreement between you and us to the contrary. … Notwithstanding any other agreement to the contrary, unless prohibited by your country’s applicable law, all disputes related to these Terms, the Service, or any patents – including without limitation disputes related to or arising from any Content (whether your or others' Content), or your or others' use of the Service or the complete or partial termination thereof – shall be brought and must proceed exclusively in the federal or state courts located in Wichita County or Tarrant County, Texas, United States, and you and Anysphere consent to personal jurisdiction in those forums and waive any objection as to inconvenient forum. … For the avoidance of doubt, the choice of law and forum selection provisions of this paragraph shall apply regardless of whether a dispute or any claims contained therein are based in contract, tort, statute, common law, or otherwise, and the choice of law and forum selection provisions of this paragraph shall apply to pending and future disputes and shall apply to your dispute regardless of when the conduct relating to the dispute arose or occurred. … The choice of law and forum selection provisions of this paragraph shall also extend to disputes involving our U.S. corporate affiliates, who consent to and are intended third-party beneficiaries of this paragraph. … In the event of a dispute, claim or controversy relating to this Agreement (“Dispute”), the Parties will first attempt in good faith to informally resolve the matter. … The Party raising the Dispute must notify the other party (“Dispute Notice”), who will have thirty (30) days from the date of delivery of the Dispute Notice to propose a time for the Parties to meet to attempt to resolve the Dispute. … If the Parties have not resolved the dispute within forty-five (45) days of delivery of the Dispute Notice, either Party may seek to resolve the dispute through litigation as stated in Section 16.1. … Governing Law, Forum Selection, Jurisdiction, and Venue. … Unless prohibited by your country’s applicable law, the laws of the State of Texas, excluding its choice of law provisions, will govern these Terms and any dispute that arises between you and Anysphere, notwithstanding any other agreement between you and us to the contrary. … Notwithstanding any other agreement to the contrary, unless prohibited by your country’s applicable law, all disputes related to these Terms, the Service, or any patents – including without limitation disputes related to or arising from any Content (whether your or others' Content), or your or others' use of the Service or the complete or partial termination thereof – shall be brought and must proceed exclusively in the federal or state courts located in Wichita County or Tarrant County, Texas, United States, and you and Anysphere consent to personal jurisdiction in those forums and waive any objection as to inconvenient forum. … For the avoidance of doubt, the choice of law and forum selection provisions of this paragraph shall apply regardless of whether a dispute or any claims contained therein are based in contract, tort, statute, common law, or otherwise, and the choice of law and forum selection provisions of this paragraph shall apply to pending and future disputes and shall apply to your dispute regardless of when the conduct relating to the dispute arose or occurred. … The choice of law and forum selection provisions of this paragraph shall also extend to disputes involving our U.S. corporate affiliates, who consent to and are intended third-party beneficiaries of this paragraph. … In the event of a dispute, claim or controversy relating to this Agreement (“Dispute”), the Parties will first attempt in good faith to informally resolve the matter. … The Party raising the Dispute must notify the other party (“Dispute Notice”), who will have thirty (30) days from the date of delivery of the Dispute Notice to propose a time for the Parties to meet to attempt to resolve the Dispute. … If the Parties have not resolved the dispute within forty-five (45) days of delivery of the Dispute Notice, either Party may seek to resolve the dispute through litigation as stated in Section 16.1.

  Quote taken word for word from the document by the monitor.

• high

  Added limitations period for claims

  New limitations periods require federal claims to be initiated within 1 year and state claims within 2 years, or the shortest period allowed by law, with permanent waiver of claims after these periods.

  Before

  Not in the old version.

  After

  15.3. Limitations Period. You and Anysphere agree that you must initiate any proceeding or action asserting a federal claim within one (1) year of the date of the occurrence of the event or facts giving rise to a dispute that is arising out of or related to these Terms or the Service, or if such limitation period is unenforceable under applicable law, then the shortest limitation period permitted by applicable law. You and Anysphere agree that you must initiate any proceeding or action asserting a state law claim within two (2) years of the date of the occurrence of the event or facts giving rise to a dispute that is arising out of or related to these Terms or the Service. Otherwise, to the extent permitted by applicable law, you forever waive the right to pursue any claim or cause of action, of any kind or character, based on such events or facts, and such claims or causes of action are permanently barred.

• medium

  Class and representative actions language changed

  The language about class and representative actions changed from arbitration-specific to a mutual agreement not to seek consolidated or class proceedings.

  Before

  UNLESS BOTH YOU AND ANYSPHERE AGREE OTHERWISE, THE ARBITRATOR MAY NOT CONSOLIDATE OR JOIN MORE THAN ONE PERSON’S OR PARTY’S CLAIMS AND MAY NOT OTHERWISE PRESIDE OVER ANY FORM OF A CONSOLIDATED, REPRESENTATIVE, OR CLASS PROCEEDING.

  After

  UNLESS BOTH YOU AND ANYSPHERE AGREE OTHERWISE, YOU AND ANYSPHERE AGREE NOT TO SEEK TO CONSOLIDATE OR JOIN MORE THAN ONE PERSON’S OR PARTY’S CLAIMS AND NOT TO OTHERWISE SEEK ANY FORM OF A CONSOLIDATED, REPRESENTATIVE, OR CLASS PROCEEDING.

• medium

  Relief provisions updated to mutual agreement

  The relief provisions changed from arbitration-specific language to mutual agreement language about seeking relief only for individual claims, with exceptions for public injunctive relief.

  Before

  ALSO, THE ARBITRATOR MAY AWARD RELIEF (INCLUDING MONETARY, INJUNCTIVE, AND DECLARATORY RELIEF) ONLY IN FAVOR OF THE INDIVIDUAL PARTY SEEKING RELIEF AND ONLY TO THE EXTENT NECESSARY TO PROVIDE RELIEF NECESSITATED BY THAT PARTY’S INDIVIDUAL CLAIM(S), EXCEPT THAT YOU MAY PURSUE A CLAIM FOR AND THE ARBITRATOR MAY AWARD PUBLIC INJUNCTIVE RELIEF UNDER APPLICABLE LAW TO THE EXTENT REQUIRED FOR THE ENFORCEABILITY OF THIS PROVISION.

  After

  ALSO, YOU AND ANYSPHERE AGREE TO SEEK RELIEF (INCLUDING MONETARY, INJUNCTIVE, AND DECLARATORY RELIEF) ONLY IN FAVOR OF THE INDIVIDUAL PARTY SEEKING RELIEF AND ONLY TO THE EXTENT NECESSARY TO PROVIDE RELIEF NECESSITATED BY THAT PARTY’S INDIVIDUAL CLAIM(S), EXCEPT THAT YOU AND ANYSPHERE MAY PURSUE A CLAIM FOR PUBLIC INJUNCTIVE RELIEF UNDER APPLICABLE LAW TO THE EXTENT REQUIRED FOR THE ENFORCEABILITY OF THIS PROVISION.

• low

  Terms acceptance includes Acceptable Use Policy

  The Terms now explicitly state that by using the Service, you agree to these Terms including the Acceptable Use Policy.

  Before

  By using the Service, you agree to these Terms.

  After

  By using the Service, you agree to these Terms including our Acceptable Use Policy.

• low

  Section title changed from Pre-Arbitration Dispute Resolution to Dispute Resolution

  The section title was changed to remove arbitration reference, now simply 'Dispute Resolution.'

  Before

  Pre-Arbitration Dispute Resolution.

  After

  Dispute Resolution.

Full page and a fresh check on WhatChanged →
✓ Every change found by code is explained or listed as minor, and every quote is checked against both versions. Explanations are written by AI and reviewed by a person; the quotes are the documents' own words. 2 minor edits (dates, numbering, menus) not shown.

The agreement adds terms for benchmarking, usage-based offerings, updates data processing references, clarifies customer obligations, and adjusts confidentiality and definitions related to Free, Beta, and Usage-Based Offerings.

• high

  New rules for benchmarking and public disclosure

  Customers can conduct benchmarks of Atlassian products but must include all info to replicate them when disclosing results, and cannot disclose results for Free or Beta Products.

  Before

  Not in the old version.

  After

  If Customer, directly or through a third party, conducts or publicly discloses the results of an Assessment, (i) the disclosure must include all information necessary to replicate the Assessment and (ii) Customer grants Atlassian a right to conduct Assessments of Customer’s products and services and, except for beta products or services, publicly disclose the results with all information necessary to replicate the Assessments. Customer must not publicly disclose the results of any Assessment of Free or Beta Products, or cause such results to be disclosed.

• high

  Introduction of Usage-Based Offerings and related terms

  The agreement adds Usage-Based Offerings as a new product type with specific terms, includes them in definitions, and references a new Usage-Based Offering Terms document.

  Before

  4. Cloud Products…“Product-Specific Terms” means terms that apply only to certain Products or features, available at https://www.atlassian.com/legal/product-terms, including the AI Terms.…“Scope of Use” means Customer’s entitlements to the Products.…Such entitlements may be based on: (a) number of licenses, copies or instances, (b) entity, division, business unit, website, or field of use, (c) number and type of Users, (d) number of queries, requests or other usage-based subscription units, or (e) other restrictions or billable units.

  After

  4.7 Usage-Based Offerings. … Cloud Products may be, or include access to, Usage-Based Offerings. … Atlassian provides Usage-Based Offerings under the Usage-Based Offering Terms. … “Product-Specific Terms” means terms that apply only to certain Products or features, available at https://www.atlassian.com/legal/product-terms, including the AI Terms and Usage-Based Offering Terms. … “Scope of Use” means Customer’s entitlements to the Products and Usage-Based Offerings. … Such entitlements may be based on: (a) number of licenses, copies or instances, (b) entity, division, business unit, website, or field of use, (c) number and type of Users, (d) number of queries, requests or other usage-based units, or (e) other restrictions or billable units. … “Usage-Based Offerings” means Usage-Based Offerings as described in the Usage-Based Offering Terms. … “Usage-Based Offering Terms” means the Atlassian usage-based offering terms available at https://www.atlassian.com/legal/usage-based-offering-terms.

  Quote taken word for word from the document by the monitor.

• medium

  Updated reference for processing Customer Data in Cloud Products

  The clause about Atlassian processing Customer Data for Cloud Products now refers to the DPA Schedule 1 Section 6 instead of the agreement directly.

  Before

  Atlassian may process Customer Data to provide the Cloud Products and related Support or Advisory Services in accordance with this Agreement.

  After

  Atlassian may process Customer Data as specified in Section 6 (Purposes of the Processing) of Schedule 1 of the DPA.

• medium

  Clarified customer obligations for data and materials use

  Customer must ensure disclosures and consents for Atlassian's use of Customer Data and Materials as specified in particular sections rather than generally for Cloud Products, Support or Advisory Services.

  Before

  Customer must ensure it has made all disclosures and obtained all rights and consents necessary for Atlassian to use Customer Data and Customer Materials to provide the Cloud Products, Support or Advisory Services.

  After

  Customer must ensure it has made all disclosures and obtained all rights and consents necessary for Atlassian to use Customer Data as specified in Section 4.1 (Customer Data) and Customer Materials as specified in Section 8 (Support and Advisory Services).

• medium

  Changes to confidentiality of Free or Beta Products

  Atlassian’s Confidential Information now explicitly includes Free or Beta Product source code and performance info, but the statement that features and performance info of Free or Beta Products are confidential is removed.

  Before

  Atlassian’s Confidential Information includes any source code and technical or performance information about the Products.…Free or Beta Products may be inoperable, incomplete or include errors and bugs or features that Atlassian may never release, and their features and performance information are Atlassian’s Confidential Information.

  After

  Atlassian’s Confidential Information includes any Product source code and technical or performance information about Free or Beta Products.…Free or Beta Products may be inoperable, incomplete or include errors and bugs or features that Atlassian may never release.

• low

  Updated effective date

  The effective date of the agreement changed from October 7, 2025 to October 1, 2026.

  Before

  Effective starting: October 7, 2025

  After

  Effective starting: October 1, 2026

• low

  Added new section heading and benchmarking introduction

  A new subsection 2.4 Benchmarking is added, introducing the concept of Assessments.

  Before

  Not in the old version.

  After

  2.4. Benchmarking. Customer may conduct benchmarks or comparative assessments of the Products (each, an “Assessment”).

Full page and a fresh check on WhatChanged →
✓ Every change found by code is explained or listed as minor, and every quote is checked against both versions. Explanations are written by AI and reviewed by a person; the quotes are the documents' own words.

Dropbox announces upcoming changes to its Terms of Service effective January 1, 2027, with a link to review the new terms.

• low

  Announcement of upcoming Terms of Service change

  Dropbox informs users that its Terms of Service will change starting January 1, 2027.

  Before

  Not in the old version.

  After

  Dropbox’s Terms of Service will be changing effective January 1, 2027.

• low

  Link provided to review new Terms of Service

  Dropbox provides a clickable link for users to review the updated Terms of Service.

  Before

  Not in the old version.

  After

  Click here to review the new terms.

Full page and a fresh check on WhatChanged →
✓ Every change found by code is explained or listed as minor, and every quote is checked against both versions. Explanations are written by AI and reviewed by a person; the quotes are the documents' own words.

Nothing that changes your rights: 1 small edit to the page (menus, numbering, wording).

✓ Every change found by code is explained or listed as minor, and every quote is checked against both versions. Explanations are written by AI and reviewed by a person; the quotes are the documents' own words.