Gusto updated its Developer Terms of Service on April 29, 2026, adding 131 new sentences that establish comprehensive rules for developers using Gusto's APIs and tools. The updated version (2.0) now explicitly includes mandatory arbitration and class action waiver provisions, defines the scope of the developer license, clarifies that Gusto can modify or discontinue developer tools at will, and requires developers to maintain compliance with all stated terms. This matters because developers integrating with Gusto's platform are now subject to stronger contractual restrictions and dispute resolution requirements they must accept to use the service.
Developers: You cannot file or join a class action lawsuit against Gusto and must resolve all disputes through individual arbitration.
Developers: Gusto can change or remove the APIs and tools you depend on anytime, and you have no recourse if your integration breaks.
Developers: If Gusto updates its APIs or tools, you must pay to upgrade your integration to stay current.
Developers: Gusto can cut off or limit your access to parts of its APIs without warning or explanation.
Developers integrating with Gusto's platform are now bound by mandatory arbitration and class action waiver provisions, meaning they cannot join or file class actions against Gusto and must resolve disputes through individual, binding arbitration. The updated terms also grant Gusto the right to modify, update, or discontinue developer tools at its sole discretion without notice or liability, which could disrupt integrations and require developers to absorb costs of upgrading to new versions. Developers should review Section 19 of the updated terms carefully before creating or maintaining integrations with Gusto's platform, and consider whether the arbitration and modification provisions align with their business and legal risk tolerance.
→ Review Section 19 of the updated Developer Terms carefully to understand the arbitration and class action waiver provisions before accepting the terms.
→ Assess whether mandatory arbitration is acceptable for your business and legal risk tolerance, and consider whether you need legal review before accepting.
→ Evaluate your dependency on Gusto developer tools and determine whether you can accommodate future Gusto modifications or discontinuations without service disruption.
Developers must resolve all disputes with Gusto through individual, binding arbitration and cannot participate in class actions.
Gusto can modify, update, or discontinue developer tools at any time without notice, liability, or developer recourse.
Developers receive only a limited, revocable, non-exclusive, non-transferable license to use Gusto APIs solely for creating integrations with Gusto's platform.
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
Gusto's Developer Terms version 2.0 (effective April 27, 2026) adds explicit mandatory arbitration and class action waiver language, defines developer license scope and restrictions, and asserts unilateral rights to modify or discontinue developer tools without …
Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.
Unlock the full institutional analysis — InsightConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-C-001476.
Gusto's updated privacy policy adds explicit language describing how the company sells or shares personal information under U.S. state privacy …
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.
Get alerted when this policy changes again, including what changed and why it matters.