Retroactive Terms Changes

A retroactive terms change applies new contract or privacy rules to the past: to disputes that already began, or to data a vendor collected under older, stricter promises.

What are retroactive terms changes?

A retroactive terms change is a change that reaches back in time. It applies the new rules not only to what happens from now on, but also to things that already happened under the old rules.

Two kinds come up most often with vendors:

  • Past disputes: new dispute rules, such as an arbitration clause, that the vendor says cover claims that arose before the change.
  • Data already collected: a new use, such as AI training or sharing with partners, applied to data you gave the vendor under an older, stricter privacy policy.

The opposite is a forward-only change, sometimes called "prospective." It applies only to events and data after the effective date.

What it looks like in a vendor's terms

Retroactive wording is not always labeled. It can sit inside broad phrases. A typical clause reads like this:

The updated Terms apply to your use of the services and to any claims between you and us, whether they arose before or after the effective date. Our current Privacy Policy governs all information we hold about you.
  • "Any claims ... before or after": new dispute rules reach claims that already exist.
  • "All information we hold about you": the new policy covers data collected under the old one.

Protective wording looks the opposite. As of October 2026, the separate X Purchaser Terms of Service, which cover X's paid services, say plainly: "The changes will not be retroactive."

What the FTC has said

In February 2024, staff at the Federal Trade Commission, the US consumer protection agency, published a blog post titled "AI (and other) Companies: Quietly Changing Your Terms of Service Could Be Unfair or Deceptive." It is staff guidance, not a rule.

The post says a company that adopts more permissive data practices, such as sharing data or using it for AI training, and tells people only through a "surreptitious, retroactive amendment" to its terms or privacy policy may be acting unfairly or deceptively. It points to two past FTC cases: Gateway Learning in 2004, which changed its privacy policy to allow sharing data with third parties without telling consumers or getting their consent, and 1Health in 2023, which the FTC said retroactively expanded the third parties it could share data with.

Law firm Ballard Spahr summed up the guidance this way: companies cannot erase existing privacy promises by applying new policy terms retroactively, and should tell people before starting new uses of their data.

What courts and lawyers say

Contract law starts from the idea that a changed contract is a new offer, which needs notice and acceptance. In Douglas v. U.S. District Court (9th Cir. 2007), a customer was not bound by revised terms, including an arbitration clause, that were only posted on a website.

Law firm Morgan Lewis says terms of use "can't be retroactively updated," and its sample clause for website owners reads "The changes will not be retroactive." The details depend on the state and the facts.

A real change we caught

Venpo flagged that X's new terms drop the promise that changes will not be retroactive. The new terms took effect on October 9, 2026, and X's own summary of the update did not mention the deleted sentence. Once it is gone, the terms no longer give you that assurance in writing. A deleted sentence like this is easy to miss in a long update.

Why it matters to you

You made decisions based on the terms you saw. You chose what data to send a vendor under the privacy promises in place at the time. A retroactive change can reuse that data in ways you never agreed to, such as AI training on customer data.

That can affect your own customers. If you told them their data would not be used for certain purposes, a vendor's retroactive change can put you out of line with your own promises.

For disputes, a retroactive change can move an argument you already have with a vendor out of court and into private arbitration, or shorten the time you have to raise it.

What to check

  • Whether the terms say changes are not retroactive, and whether that sentence is still there after each update.
  • Whether new dispute rules claim to cover claims that arose before the change.
  • Whether a new privacy policy or DPA says it covers data collected earlier.
  • Whether new data uses, such as AI training, come with an opt-out or need your consent.
  • In a negotiated contract, ask for a clause saying changes apply only to events and data after the effective date.

How Venpo helps

Retroactive wording often arrives as a deleted sentence or a broadened phrase. Venpo watches your vendors' terms, privacy policies and DPAs and emails you a plain-English alert when they change, with what changed and why it matters. Its Fine Print Scan also answers whether each vendor trains AI on your data.

Start for free

Frequently asked questions

Can a company change its privacy policy retroactively?

A company can publish a new policy at any time, but applying looser rules to data collected under older promises is risky. FTC staff warned in 2024 that doing so quietly may be unfair or deceptive.

Can new terms apply to a dispute that already started?

Some terms try to. Whether a court enforces that depends on the wording, the notice you got and the law that applies.

How do I know if a change is retroactive?

Look for phrases like "whether arising before or after" or "all information we hold," and check whether a non-retroactivity promise was removed. Comparing old and new versions side by side makes this easier.

Related terms

Sources

Last reviewed