Gusto updated its Developer Terms of Service on April 29, 2026, introducing a new version (2.0) with substantially expanded terms governing access to its API and developer tools. The document now explicitly requires developers to resolve disputes through mandatory binding arbitration with a class action waiver, establishes Gusto's right to modify or discontinue developer tools without notice, and clarifies that developers can only access the API to build integrations that benefit users who are customers of both Gusto and the developer's application. This change materially narrows developer rights and strengthens Gusto's ability to unilaterally control access and modify the platform.
Developers who build integrations with Gusto's API are now required to resolve any disputes with Gusto through mandatory individual binding arbitration rather than pursuing class action lawsuits, which may limit their legal remedies and transparency into disputes with Gusto. Additionally, Gusto explicitly reserves the right to modify, restrict, or discontinue its developer tools and API access at any time without notice or liability, meaning developers could lose access to critical platform capabilities that their business depends on without warning or recourse. Developers should review Section 19 of these terms carefully and consider whether the arbitration requirements and lack of access guarantees are acceptable before continuing to build on the Gusto API.
The updated terms introduce mandatory binding arbitration and remove developers' class action rights, while explicitly reserving Gusto's right to modify or discontinue the API without notice or liability. For developers whose business depends on the Gusto integration, the loss of legal remedies and API access guarantees materially increases operational and legal risk.
→ Review Section 19 of the updated Developer Terms carefully before continuing to build or maintain an integration on the Gusto API.
→ Assess whether your business-critical integrations or products depend heavily on continuous Gusto API access and evaluate contingency plans or alternative platforms.
→ Consider whether to pursue a service level agreement, notice period commitment, or other contractual protections from Gusto to mitigate discontinuance risk.
→ You will be bound by mandatory arbitration and unable to pursue a class action lawsuit against Gusto, limiting your legal remedies if a dispute arises.
→ Gusto can restrict, modify, or discontinue API access at any time without notice or liability, potentially disrupting integrations your business depends on.
→ If Gusto updates the developer tools, you may be required to upgrade at your own expense with no control over timing or cost.
→ Your integration may only serve Joint Users (customers of both Gusto and your application), narrowing the use cases and revenue potential you can support.
This is the 5th significant Arbitration Expansion change Gusto has made since ConductAtlas began monitoring.
ConductAtlas has recorded 4 material changes to this document (since April 2026). An additional minor or cosmetic changes were excluded.
Across all monitored documents, Gusto has made 7 significant changes.
5 of Gusto's significant changes have been classified as negative for consumers.
All disputes with Gusto must be resolved through binding individual arbitration, not litigation or class action, limiting developers' legal remedies and visibility into disputes.
Gusto can modify, update, or discontinue the API and developer tools at any time without notice or liability, creating supply chain risk for developers.
API access is now explicitly limited to integrations serving only users who are customers of both Gusto and the developer's application, narrowing the use cases developers can support.
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
If you have a dispute with Gusto, you must go through private arbitration rather than a court or class action lawsuit.
Gusto can change or shut down the API and tools you depend on whenever it wants, with no warning or compensation.
+ 3 more obligation changes. Full breakdown available with Watcher.
Track changes →Gusto introduced a new version (2.0) of its Developer Terms of Service effective April 27, 2026, adding mandatory arbitration with class action waiver, unilateral platform modification rights, and explicit scope limitations on API use. Organizations with developers on the Gusto platform need to assess whether their vendor risk management framework adequately addresses the removal of class action rights and Gusto's unilateral discontinuance authority. This change may trigger review of integration dependencies, SLAs, and whether contractual backstops exist. No specific regulatory requirement mandates the arbitration structure, but FTC oversight of unfair practices and state consumer protection laws may apply contextually. Review is advisable within 30 days to determine if contractual protections or integration alternatives should be evaluated.
FTC Act Section 5 (unfair or deceptive practices); state consumer protection statutes (unfair contract terms); Federal Arbitration Act (enforceability of arbitration clauses); potential GDPR implications if any EU-based developers or joint users are affected.
Full compliance analysis
Obligation analysis, escalation trigger, board language, and recommended action.
Watcher: regulatory citations + obligations. Professional: full compliance memo.
ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-C-001477.
See the full side-by-side comparison of every sentence added, removed, and modified.
🔒 Full diff — WatcherGusto's privacy policy was updated on May 9, 2026 to add two new document references in its table of contents: …
Gusto updated its Terms of Service on May 9, 2026 with five technical corrections. The changes include updating contact email …
Gusto updated two email addresses in their Terms of Service contact sections on May 6, 2026. The opt-out form submission …
Get alerted when this policy changes again — including what changed and why it matters.
Prefer a weekly summary instead?
Get the biggest policy changes across 320+ platforms every Sunday.