What changes after you sign
Twelve shapes a change to a vendor's published terms can take, what each one costs the person who signed, and what to check before you do.
This page reads the record. It is not the record. The Diff states what changed in a tracked document and interprets nothing; this guide draws general shapes out of those changes, which is interpretation, and it is kept separate for that reason.
What this is
Twelve shapes that a change to a vendor's published terms can take.
They come from 91 recorded changes to documents published by 17 AI operators between August 29 and November 14, 2026. Every change was captured from the operator's own page, hashed into an append-only chain, and timestamped by an outside authority, so each instance below can be checked rather than taken on trust. The changes are listed individually in The Diff and grouped by shape at kinds of change.
The shapes are the useful part, because they are not about those 17 companies. A vendor you are signing with this week is probably not in the archive. The moves available to it are the same ones.
What this is not
Not legal advice. Not a claim about what any company intended — the captures show what changed and when, and nothing in them shows why. Not a prediction about your vendor.
And a limit that matters more than the others: everything here is drawn from published terms. A negotiated enterprise agreement may not incorporate the public pages at all, or may freeze them at a version. If you have a signed master agreement, the question of which document governs you is the first one to answer, and it is not answered here.
Before the list: two things the record establishes
Most changes are nothing. Of the 91, 24 moved only entity names, dates, section numbering, punctuation or navigation. Another 34 described a practice or feature the previous version had not described, most of them routine. The changes that moved an obligation were a minority — 7 reallocated responsibility, 5 narrowed the scope of a promise, 4 withdrew a commitment, 4 relocated terms into another document, 3 changed a number, 1 changed dispute resolution. This guide is not a warning that your vendor is up to something. It is a list of where to look when something does move.
The date on the document is not the date the text changed. This is the most practically useful finding in the collection. Anthropic's Usage Policy, captured on October 10, carried an effective date of November 12, 2026. OpenAI's Usage Policies, captured October 24, carried November 20, 2026. In both cases the text was live weeks before the date it claimed to take effect. A vendor's own date line cannot establish what a page said on a given day. A dated copy can — which is the one concrete recommendation this whole guide reduces to: when you sign, keep your own copy of every document the agreement incorporates. Not a link. A copy.
1. Scope changed
5 recorded.
The move. The sentence you would check stays exactly where it is. What narrows is the subject underneath it — a qualifying phrase added, removed or rewritten.
What changes for you. The promise remains literally true and covers less. A reader looking for the sentence finds it, and a reader comparing versions by length or tone sees almost nothing.
What to check. Read every qualifier in any promise you are relying on. Does the promise name a category of data, a product line, or another document? If it does, the thing to establish is what sits outside the named category — because that is what the promise no longer reaches. Qualifiers worth stopping on: governed by this policy, in the conventional sense, where applicable, a core set of, certain products.
Recorded. Zoom's statement that it does not sell personal data acquired the qualifier "governed by this Privacy Statement," and two sentences were added referring business contact data to a separate Common Room privacy statement (2026-09-19-zoom-privacy-statement.md). Apple changed what newly supported regions receive from unqualified wording to "a core set of" features (2026-09-19-apple-intelligence-availability.md).
2. Commitment withdrawn
4 recorded.
The move. A stated commitment, compliance reference, protective instruction or user-facing section is deleted.
What changes for you. You lose something you may have relied on without ever having been told it was conditional. The removal can arrive in the same revision as additions, which makes the document read as though it improved.
What to check. Sort the commitments you care about into two piles: those in the document you sign, and those on a web page the vendor edits alone. The second pile can empty without notice. Compliance certifications, regulatory framework participation, and dispute-resolution paths belong to the second pile more often than people expect.
Recorded. Perplexity removed an entire EU-U.S. Data Privacy Framework section — the certification, the clause making the Framework's principles govern in a conflict, regulatory jurisdiction over compliance, responsibility for onward transfers, and a third-party dispute path — in the same revision that added a "Third-Party Applications/Websites" section and an expanded data subject rights section (2026-10-24-perplexity-privacy-policy.md). xAI removed an instruction asking users not to include personal information in prompts (2026-10-17-xai-privacy-policy.md).
3. Responsibility reallocated
7 recorded — the most common of the consequential shapes.
The move. The document changes who bears the consequences of inputs, outputs, or reliance on a feature.
What changes for you. Risk you did not price moves onto you. In the recorded cases this shape tracks the product: it appeared in the same revision that introduced or expanded a generative or agentic capability. If your vendor ships an agent, expect this document to move.
What to check. Find three things and read them together: the sentence saying who is responsible for outputs, the carve-outs to the vendor's indemnification obligations, and any "at your own risk" phrasing attached to a specific feature. A feature-specific carve-out is easy to miss because the general indemnity above it still reads as protective.
Recorded. OpenAI added a synthetic-voice subsection that puts consent and AI-disclosure duties on the user and carves that feature out of OpenAI's indemnification obligations (2026-10-17-openai-service-terms.md). xAI added language that users are responsible for actions taken on their behalf "including providing payment information, as if taken themselves," in the same revision that removed its instruction not to put personal information in prompts (2026-10-17-xai-privacy-policy.md). Snap added a summary stating AI feature outputs may not be accurate or appropriate and are used at the user's own risk (2026-11-14-snap-terms.md).
Roblox is the subtler case and worth stating precisely, because it shows the shape at its least visible. Who bears the responsibility did not change: the user bore it before and bears it after. What changed is where it sits and how far it reaches. A clause titled "Responsibility for AI Features" was recast from assigning the user a duty into disclaiming one for Roblox, and the user's own list in that clause lost the use of outputs. A new section on reliance took it up, restated it as sole responsibility, widened it to any action taken in relation to outputs and to any other content the features generate, and added duties the document had not stated before: evaluate and verify an output before using or sharing it, and do not rely on one as professional advice or in any decision, system or application where relying on it could cause harm. The same revision added a clause stating Roblox does not assert ownership of intellectual property created in outputs, which runs the other way (2026-11-07-roblox-terms-of-use.md).
Read at the level of the entry, that revision looks like a vendor disclaiming a duty it had already placed on the user. The reallocation is visible only in the document itself, which the entry's capture preserves. An entry states what changed; where this guide reads a clause more closely than an entry's excerpt does, the capture behind it is the source.
4. Terms relocated
4 recorded.
The move. An obligation leaves this document for a separate one, named by reference.
What changes for you. You are bound by documents you have not opened, and the vendor can add another at any time. The document you did read gets shorter and more reasonable with each relocation. This is the shape with the most direct consequence, because it is the one that defeats the act of reading carefully: diligence on the agreement no longer covers your obligations.
What to check. Before you sign, list every document the agreement incorporates by reference, and read them or at least count them. Then ask the question that matters more: can the vendor add to that list unilaterally? If the answer is yes, the agreement's length tells you nothing about its scope.
Recorded. Canva retitled its AI products section and added that use of certain products may be subject to additional obligations in separate Feature Specific Terms (2026-10-31-canva-terms-of-use.md). OpenAI's service terms now route wallet payments to separate wallet terms and a separate privacy notice (2026-11-14-openai-service-terms.md) and credit score services to separate credit score terms (2026-09-26-openai-service-terms.md). Zoom's referral of business contact data to the Common Room statement, in shape 1, is the same move.
This shape is a problem for the archive too. Each of those satellite documents was an obligation nobody was tracking. Six were added to the archive on November 14, 2026 and get their first capture on the following pass.
5. Limit changed
3 recorded.
The move. A number governing access, notice, retention or eligibility moves.
What changes for you. Whatever the number governs. A single digit can carry the entire effect of a revision, and it is invisible to every way people normally review a change — it does not alter the structure, the tone, or the length.
What to check. Before you sign, write the numbers down somewhere outside the document: notice period, inactivity window before termination, retention period, data export window, any threshold that gates access. Then you have something to compare against. Nobody re-reads these sections, which is what makes them a good place to put a change.
Recorded. xAI's grounds for termination without notice moved from an account inactive over a year and not paid, to an account inactive more than 120 days. The paid-account exemption was deleted rather than moved, and no refund provision changed (2026-09-19-xai-terms-of-service.md). Roblox moved a parental email notification window from 24 hours to 7 days, one of 53 changed spans (2026-11-07-roblox-privacy-policy.md).
6. Disclosure removed
9 recorded.
The move. A notice, banner, changelog entry or itemized table is deleted from the page. The underlying text often stays; the pointer to it goes.
What changes for you. Mostly this one matters after the fact rather than before. It affects your ability to establish later what a page said — a specific date, a specific price, a specific commitment that was once citable and now is not.
What to check. Nothing, before signing. The lesson is the copy: if you may ever need to prove what a vendor published, the vendor's page is not where that proof will be. This is the shape that most directly argues for keeping your own dated copies.
Recorded. Meta's privacy policy carried a banner announcing an update about agentic AI capabilities; the following capture does not have it, with one changed span on the page and no difference in the policy text itself (2026-10-10-meta-privacy-policy.md). OpenAI replaced a table of individual fine-tuned model shutdown dates with a single sentence deferring to the base models' schedule, after which no page states the shutdown date of any individual snapshot (2026-10-31-openai-model-deprecations.md).
In fairness: the likeliest reading of the OpenAI removals is housekeeping after the shutdowns had passed. That does not change the effect on anyone who needs the old specifics.
7. Dispute resolution changed
1 recorded.
The move. Venue, governing law, arbitration, or collective-action provisions change.
What changes for you. Where you would have to go, under which state's law, and whether you can join with others. These terms decide the practical availability of a remedy — a county-level venue clause can make a small claim not worth bringing, whatever the claim's merits.
What to check. Read this section every time, even when nothing suggests it moved, and read it with a map. Specifically: the named venue down to the county, the governing law, whether arbitration is a fallback if the venue clause fails, and whether there is a class-action or representative-action waiver.
Recorded. xAI inserted a paragraph setting venue in one of two named Texas counties under Texas law, with arbitration as a fallback if the forum selection clause proves unenforceable, plus a waiver of any right to bring a class or representative action. It arrived among 139 changed spans in one revision, most of the rest being section numbering and capitalization. The captures bound its arrival to a five-day window, tighter than the document's own effective date (2026-09-05-xai-terms-of-service.md).
One instance is not a pattern. It is on this list because of what it was buried in: 139 changed spans is enough noise to hide a clause in, and this clause is the one that decides whether any other clause can be enforced.
8. Use restriction added
4 recorded.
The move. A new limit appears on what users or third parties may do.
What changes for you. Work you are currently doing, or plan to do, may stop being permitted. The restriction can reach further than the customer relationship — to work you do for other people, and to conduct that does not involve the vendor's product at the moment of the restriction.
What to check. Read new restrictions against what your business actually does, including work performed for clients, and including work by contractors and vendors acting on your behalf. Then check whether the carve-back you are relying on is bounded by language from the restriction itself, which can make the permission hard to depend on.
Recorded. OpenAI added a training and development section prohibiting the use of its models or outputs to generate, prepare, select or supply training material or signals for models intended as alternatives to its own, itemizing training data, rubrics, reinforcement-learning environments, labels, scores, rankings, preferences, rewards, corrections, and the selection, filtering or validation of training data. The restrictions apply whether the work is done for yourself or another party, "even if you do not train the resulting model." A carve-back permits research, software development, evaluation and benchmarking, and product development "within these boundaries" (2026-10-24-openai-usage-policies.md). Anthropic revised its usage policy across fifteen spans, including new high-risk recommendation categories for employment, education, healthcare access, public benefits and legal adjudication (2026-10-10-anthropic-usage-policy.md).
9. Effective date ahead of the capture
2 recorded — computed, not assigned by hand.
The move. The document's own stated effective date is later than the date the capture was taken — so the text was live before the date it claims to take effect.
What changes for you. The date line stops being usable as evidence. If a dispute ever turns on what the terms said when you did something, the printed date will not answer it, and the version history the vendor publishes is the vendor's.
What to check. Record the date you accepted, and keep the copy from that date. If a change notice arrives, note the date you received it alongside the effective date the document claims, because the two routinely differ and only one of them is yours.
Recorded. The instances are above, under Before the list. This shape is computed by comparing each entry's own stated effective date against the date of the capture, rather than assigned by a person, because it is a comparison of two dates and not a judgment about anything.
10. Practice disclosed
34 recorded — the second most common shape, and usually unremarkable.
The move. A data practice, feature or capability is described that the previous version did not describe.
What changes for you. Usually nothing. Samsung added two tablets to a supported device list and raised a minimum OS version (2026-10-10-samsung-galaxy-ai-processing.md). Snap added AI-powered replies to the list of features that use generative AI (2026-09-19-snap-generative-ai-disclosure.md). That is what most of these look like, and reading them as ominous would be reading them wrong.
Occasionally, though, a disclosure is the first notice you get of a new data flow, and once in a while it is a company becoming candid about something that was already happening.
What to check. When a privacy policy grows, read the part that is new rather than the summary of what changed. A new section heading in a privacy policy is worth two minutes; a changed sentence inside an existing section usually is not.
Recorded. Amazon disclosed that reporting an issue or using the thumbs-down icon causes transcripts and related feedback to be retained — a disclosure of something presumably already happening (2026-10-10-amazon-alexa-privacy.md). Replika replaced its description of face-and-head-movement and depth-camera data collection with new location and biometric age-verification sections, and separately stated plainly that it sells personal data and engages in targeted advertising, which was more candid than the text it replaced (2026-10-31-replika-privacy-policy.md).
11. Lifecycle notice
19 recorded.
The move. A deprecation, retirement, shutdown or model-status change.
What changes for you. If you have built on a specific model, this is the shape with a date attached, and the date is the thing to extract. It also has a second layer worth watching: the policy governing deprecations can itself change in the same revision that announces one.
What to check. Two questions, not one. What is being retired and when — and separately, what is the minimum notice period the vendor commits to, and which classes of model does it cover? The second question is the one that tells you how much warning you get next time.
Recorded. OpenAI restructured past deprecations into a table, added October shutdown entries for the gpt-3.5-turbo and gpt-4-0613 families, defined three lifecycle states, extended the minimum notice period for generally available models to also cover image generation models, and removed language reserving the right to retire a model sooner for safety or compliance reasons — a change that runs toward the customer, in the same revision as the rest (2026-11-14-openai-model-deprecations.md). Microsoft replaced a Cortana services description with a single sentence stating support ended in 2024 (2026-10-03-microsoft-services-agreement.md).
12. Administrative
37 recorded — the most common shape, and almost always nothing.
The move. Entity names, dates, renumbering, punctuation, site navigation, section ordering, index dating.
What changes for you. Nearly always nothing at all. 24 of the 91 recorded changes were administrative and nothing else. This shape is on the list mostly to say so: if you are checking a vendor's change log for signs of trouble, this is where most of the volume is, and it is noise.
What to check. One thing only, and it is worth the ten seconds: who is the agreement with, and did that name change? The counterparty's identity is filed as administrative because no obligation moves when it changes, but it is the one administrative edit that changes the answer to "whom would I be making a claim against."
Recorded. xAI changed the contracting entity from SpaceXAI LLC to SpaceX Super Intelligence LLC throughout its terms, including in the regulatory representative and copyright lines, with no other substantive change in the revision (2026-10-31-xai-terms-of-service.md).
What this guide cannot tell you
- Why. The captures establish what changed and when. Nothing in them establishes intent, and no instance above should be repeated as though it did.
- Whether a change is lawful, enforceable, or binding on you. That depends on your jurisdiction, your agreement, and facts not in the record.
- Whether it applies to your contract at all. Negotiated terms differ from published ones.
- Whether any of this is a trend. Eleven weeks is not a trend. Several of these shapes rest on a single vendor, and one rests on a single instance. They are shapes that have occurred, not rates at which they occur.
- What is in the documents nobody is tracking. The archive covers 62 documents from 17 operators. Shape 4 exists precisely because obligations move into documents outside any list.
The short version
If you read nothing else: keep your own dated copy of every document your agreement incorporates, write down the numbers, read the dispute resolution section every time, and count the documents named by reference — because that count, not the length of the agreement, is the size of what you agreed to.
How this page is built
Generated from thediff/READERS-GUIDE.md by
tools/build-diff.py. Every count above is filled from
thediff/kinds.json at build time, and every entry named
above is resolved to that entry's anchor on The Diff, so a citation
that stopped matching an entry would stop the build rather than sit
here broken.
The Diff lists every recorded change newest first. Kinds of change groups the same changes by shape, which is the index this guide is written over.