Terms-versions evidence pack

Read this before anything else

A terms page can be rewritten quietly. If nobody saved what it said on the day you collected the data, that evidence is gone. This pack is the dated copies we hold for the sites you name, with the lines that changed quoted verbatim.

What the $179 pack is

One evidence pack covers the sites you name. After you pay, a person emails you the dated, quoted change-history, each line tied to a stored read and a fingerprint, plus the per-subject chain for those reads.

• Quoted lines that appeared or disappearedEach line is copied from a stored read. We do not paraphrase it.
• A fingerprint and a read time on every lineThe fingerprint is a seal over the stored bytes. If those bytes were rewritten, the seal would not match.
• A chain per site-and-fileEach new stored read is linked to the one before it. If a stored read is dropped or skipped, the chain no longer verifies. That is what “no read was removed” means here.
• A safe answer when we cannot claim a changeOne read is not two dates. Two reads with the same bytes are not a change. We say so, and we still quote what we hold.

If you want us to keep reading those same sites, a $199 per month watch is quoted in the email thread, not on this page’s price rail.

Example change-historyprototype on local fixtures, not a live-web read

Three named example sites in the prototype fixtures, read at 1 Aug 2026 and 15 Aug 2026 where a second read exists. Every quote below is fixture output, not a live fetch. 17 quoted fields in the prototype run; the backing check re-proved all 17 against the store.

gamma-shop.example was read once. One date cannot prove a change, so the prototype does not claim one. That refusal is part of the product.

What the chain proves11 links across 6 subject chains in the fixture run

Each stored read already carries a fingerprint, so we can prove that read was not rewritten. That is not the same as proving a read was not taken out. The pack now also carries a hash chain per site-and-file: the first read hangs off a fixed start value, and each later read is linked to the tip before it. The prototype checks that chain. Appending a read extends it. Deleting a stored read fails the check. Skipping a stored read fails the check.

11 chain links in that run, matching 11 stored reads. The prototype also refused a fake change built from one read, and it answered a permission-shaped question with quotes only — the same quotes-only shape, no verdict.

What this is not

• Not legal advice.We are not your lawyer. A quoted line is not a permission slip.
• Not a yes or no on whether you may crawl.That call depends on facts about you that we do not have. The software will not emit it.
• Not the AI-vendor policy feed.That other feed cannot store vendor wording. This pack exists because a data lead needs the dated wording itself.
• Not a live-web sample on this page.The tables above are the prototype on local fixtures. A paid pack is the sites you name, from reads we actually hold.
• Not a complete archive of the internet, and not a court affidavit.We store the reads we took. The chain covers those reads. A stranger has not countersigned the hashes.

How to use a pack

You email the sites you care about. We reply with which dated copies we hold, before you spend anything. If you pay, a person emails the quoted history, the fingerprints, the read times, and the chain. You can re-check the fingerprints against the bytes. You still make the crawling call yourself.

The record can only be built forward. We cannot sell you a past week we did not read.