X's new terms drop the promise that changes will not be retroactive

The change

X's new Terms of Service took effect on October 9, 2026. They replace the version of April 10, 2026 for users outside the European Union, EFTA States, and the United Kingdom, and the version of January 15, 2026 for users inside them. X posted the new text a month earlier and kept the old one on the same page until the switch.

X also published a short summary of the update on September 9, 2026. It lists four things: how disputes are resolved, the class action and jury trial waiver, responsibility for autonomous features, and a clarification for European users. All four show up when the two versions are compared. So do several edits the summary does not mention, and one of them is the sentence that used to limit how future changes apply.

What changed

• Retroactive changes. The clause on future revisions used to say, right after its opening sentence: "The changes will not be retroactive." That sentence is gone in both regional versions.

• Autonomous features. You were responsible for your use of the Services and your Content. You are now responsible for your use of the Services "including any features that perform autonomous actions," and for complying with the laws that apply to "autonomous actions on your behalf."

• Arbitration as a fallback. For users outside Europe, disputes still go to courts in Texas. If that clause is found unenforceable, the dispute now goes to binding arbitration in Tarrant County, Texas.

• Jury trial waiver. A new paragraph has both sides "WAIVING THE RIGHT TO A TRIAL BY JURY," next to the class action waiver that the old terms already had.

• Named affiliates. The dispute rules extend to X's corporate affiliates, which the new text says include "any U.S. SpaceXAI, Cursor, or SpaceX entities."

• Smaller edits. The deadline for state law claims moved from "two (2) years" to "two (2) years and one day," and the definition of the Services no longer links to a list of covered services.

What X's summary leaves out

X's summary is accurate about the four points it covers. It is a summary, though, and several edits that the comparison shows are not in it.

• The removal of "The changes will not be retroactive."

• The terms of the new arbitration: the summary says disputes will be resolved through arbitration if the court venue cannot be used, and stops there.

• The change to the definition of the Services, which used to cover "our other covered services" with a link to a page listing them, and now covers "our other services" with no link.

None of these is hidden. They are on the public page for anyone who compares the two versions line by line. The point is narrower: a vendor's own summary tells you what the vendor chose to highlight, and the full list only comes from the comparison.

The promise that changes will not be retroactive

The old sentence was six words long and sat in the paragraph that lets X revise the terms. With it, a user could read the clause as saying that a new version governs from its effective date forward. Without it, the clause says only that the most current version governs the relationship, that X will try to give notice of material revisions, and that continued use means acceptance.

Removing a promise is not the same as announcing the opposite. The new terms do not say that changes will be retroactive. But one part of the document already reaches backward, and it grew in this update. The dispute section says its provisions "shall apply to pending and future disputes" and apply "regardless of when the conduct relating to the dispute arose or occurred." In the old terms that sentence covered the choice of law and the choice of court. In the new terms it also covers the arbitration provisions.

Autonomous actions are now your responsibility

The terms do not define a feature that performs autonomous actions, and they do not list any. The sentence simply places such features inside "your use of the Services." A second edit in the same paragraph is easy to miss. The duty to comply with laws, rules, and policies used to apply to "you or your Content." It now applies to "you, autonomous actions on your behalf, or your Content," including on third-party services.

This is the same move other large vendors made in recent weeks. Stripe made AI agent actions legally binding on its users, and HubSpot made customers answer for what its AI agents do. X's version is shorter than either, and it sits in a consumer agreement that also binds every company with an account.

If the Texas court clause fails, the dispute goes to arbitration

The court clause itself did not move. Disputes for users outside Europe still belong in the federal or state courts of Wichita County or Tarrant County, Texas. What is new is the fallback, which applies only if that clause is found unenforceable for a given dispute.

• The case is heard by "a retired federal district or appellate court judge" through the American Arbitration Association.

• The arbitrator "shall be prohibited from granting injunctive relief," which means no order telling a party to do or stop doing something.

• The parties "waive any right to appeal the award" as far as the law allows.

• Unless the law requires otherwise, "the arbitration shall be confidential."

• It runs on an individual basis only, with no class, collective, or representative proceedings.

Arbitration clauses have been moving in other vendor terms too, as we covered when PayPal stopped paying the fees for small disputes brought against it.

What did not change

• Texas law and Texas courts still govern disputes for users outside the European Union, EFTA States, and the United Kingdom.

• The class action waiver was already in the old terms, which X's summary also notes.

• Federal claims still have to be brought within one year.

• For European users, disputes still go to the courts of Ireland under Irish law, and the new text adds that this does not remove protections that cannot be waived under the law of the country where they live.

Why this matters

X is not only a place where individuals post. Companies run brand accounts on it, buy advertising, connect scheduling and support tools, and build on its API. The new waiver paragraph says it applies to all users, "BOTH NATURAL PERSONS AND ENTITIES," whatever the purpose of their use. A company account is bound by the same sentences as a personal one.

For a SaaS company, two of the changes have practical weight. The first is the autonomous actions sentence, because anything automated that acts under the company's account is now expressly the company's responsibility under X's terms. The second is the retroactivity sentence, because it changes what a company can assume about the next revision. Terms like these are part of vendor contract monitoring even when nobody signed anything.

The update also shows the limit of relying on what a vendor says about its own changes. X did publish a summary, on time and in plain language. It still took a comparison of the two texts to see the full list, which is the difference between manual and automated vendor monitoring.

Potential impact

For a company that uses X, the update raises five practical questions:

• Which tools, integrations, or AI features can act under your X accounts without a person approving each action?

• Who in the company is accountable for what those automated actions post, send, or do?

• Did anyone compare the new terms with the old ones, or only read the summary and the in-app notice?

• Does your legal team know that a dispute with X could end up in confidential arbitration with no injunctive relief?

• Do you keep a copy of the terms that applied on a given date, now that the promise about retroactive changes is gone?

How Venpo detected it

Venpo monitors X's legal documents as part of continuous vendor risk monitoring. It flagged the new version when X posted it, a month before it took effect, while the outgoing version was still on the same page for comparison. Every quote in this article was checked against both versions and the live page. The record of the change is on the X change page, and every monitored X document is listed on the X vendor profile.

Business outcome

Teams that track X had the complete list of edits a month before the effective date, including the ones outside X's summary. That was enough time to review automations running under company accounts and to file a copy of the outgoing terms. A team that relied on X's summary had four bullet points and a date.

Key takeaway

X's new terms make users responsible for autonomous features, add arbitration behind the Texas court clause, add a jury trial waiver, and remove the sentence that said changes will not be retroactive. X announced the first three, and the fourth shows up only when you monitor vendor terms of service line by line.