Public data index › AI promise-surface archive

Which AI policy and terms pages changed between dated captures?

A hash-led record through 2026-08-08 across 186 public pages from 74 companies. Stored page bodies and line-level diffs are withheld.

261 normalized content-hash transitions were observed across 72 surfaces during 30 sealed capture days. A privacy counsel at an AI product company can request the $499/month reviewed change record below, including dates, source links, seals, coverage gaps, and human dispositions.

Mechanical observation, not legal interpretation. A hash transition is a review candidate, not a claim that contractual language changed. Navigation, timestamps, experiments, localization, or template changes can move a normalized hash without changing a policy's substance. Every candidate requires review against the public source.

5,580dated surface observations attempted
4,612normalized text captures stored and hash-verified
631blocked outcomes recorded, never treated as absence
30/30calendar dates carrying a complete local seal

Recent transition candidates with positive provenance

Each row names the catalog company and public source page, the two capture dates, and the SHA-256 values of our normalized text before and after. The table does not reproduce the text or claim that the source's contractual meaning moved.

catalog entrycapture windowpublic provenancenormalized text hashes
Snowflake
terms
2026-08-07 → 2026-08-08source page4bb61b0659a9fd9320d4c3ae37a614cb994afc0a393162b330b23d28d185cb86

108c392781315cf0a6077ad6cb36a41283b93a43400bee8255e9d58e3db0aeda
Openai
deprecation
2026-08-07 → 2026-08-08source page5b183fb5808d885d039233f92f1bc87fdc7553df6a2b09cf590b31a20acf0a06

bbe44ccc19442ee36700dd3495b338e2f15fc8780da97f73ba826e9ab2f3973c
Microsoft
terms
2026-08-07 → 2026-08-08source page936f69d8508b90e297b54728d93e42f1fd2c522f8b89fdcacefc5ce2a677a730

a157d328ba1b6201dfb94dca09694dcf73b78e2ea4bea889d500887c02500828
Microsoft
privacy
2026-08-07 → 2026-08-08source pageaee3ba5e5c414a84a51f73c448f435a67ae55dde1de48faf47e3d5f3a4fd18ad

e377697b7397c9bc7dc6a9304236498df040134c7c8357e83051d5886b207ce5
Microsoft
acceptable use
2026-08-07 → 2026-08-08source page2e8157d82fea7c78bcf4951e36c25801ac2bc2e60c775e31bf40f4c9838a81fa

d1bc4e9d7ce2596795a12376e08e1b7fc2ff442d9975557a7d556bda3bf7fda5
Google Deepmind
data use
2026-08-07 → 2026-08-08source page43c5bf4fdd35e84a8c43609dcc500f8ef96b2333d5d6eb966bc7aa3f4704c6b6

87244d9d3f0bd7f33e36fee8daa35e94baf2c5ddeb3625cf1b092e44b30c0f6e
Deepl
privacy
2026-08-07 → 2026-08-08source page668d63269a4439d010275c04b654d7ff421baa783d3227152949b39a9efec6c7

3102801e27a981e8fe737918a571da81f28701421d7087f74fdaaad52ab1eb04
Cloudflare
privacy
2026-08-07 → 2026-08-08source page39a1b20bd2f6f7499bdeb27c563998a58ab79203c81a16fb05c9a1cd94aae1cb

0b2d3f3887cea6f91866ea0572bc9b3a55d69eb1087b1cb60e098814ed6696d9
Runway
terms
2026-08-06 → 2026-08-07source page31808cb2d07e82d13c858b54434c118acc948bb2df3250d4c406a55883ea41d7

492a55353ed49bbac0319a8049cf97e2f96e57fd73417f60e82c9a63894f7d1f
Runway
privacy
2026-08-06 → 2026-08-07source paged2c77f7aba834d3a4a556c081d24c8d53a496a1252dc6a0b5883f05fae614bce

b63c725811b35f46248bc637ddcea4c263e213f104ddc1247fb1352abb0b7895
Openai
deprecation
2026-08-06 → 2026-08-07source page1c23d08fe3f9ae9d3edba0ddb69d5bc4e42f14b770ea3637236fc0c1cd69d7ba

5b183fb5808d885d039233f92f1bc87fdc7553df6a2b09cf590b31a20acf0a06
Nvidia
terms
2026-08-06 → 2026-08-07source page4842fa1d601c8b36c93bf2cacf7b19ebc2ad25b313d66c781261b3980386d107

f58d040cac7fa9b445d912397933a032c6c4d074092de7841389e825c7937f25

Monthly AI Promise-Surface Change Record

$499/month

For one privacy counsel at an AI product company: a private dated PDF and CSV covering the frozen 74-company, 186-surface panel, delivered within two business days after month end. Each reviewed candidate includes the source URL, capture window, before/after SHA-256 values, surface type, coverage status, and a concise human disposition separating likely page-template churn from a change worth legal or compliance review.

  • One monthly PDF and CSV over the existing frozen panel.
  • Blocked, dead, and missing captures travel with every issue.
  • No stored page body or unified diff is redistributed.
  • Cancel before the next monthly compilation.

Request a scoped sample →

This is a demand test. No checkout is active; the partner form opens a scoped request.

Coverage that constrains every count

The archive spans 2026-07-10 through 2026-08-08: 30 complete seals across 30 calendar days. Missing sealed dates inside that range: none. Newer directories without both a complete manifest and seal are excluded rather than guessed; pending unsealed dates: none.

On the latest sealed date, 155 of 186 catalog pages produced stored normalized text, 21 were blocked by robots or the source, and 10 were dead, empty, non-text, or failed. Across the full window, 337 outcomes were dead or failed. A failed or blocked fetch is never counted as an unchanged page.

Transition mix by page type

surface typecontent-hash transitions
privacy85
terms80
acceptable use36
data use35
deprecation24
enterprise1

The same adjacent-date comparison also recorded 30 newly captured outcomes, 15 capture disappearances, 1 newly blocked outcomes, and 0 unblocked outcomes. Those are observation-state events, not claims that a company launched, withdrew, or restored a policy.

How the seal and comparison work

  1. Fetch the frozen public catalog with an identifying user agent, honor robots policy, and pace requests by host.
  2. Strip executable markup and normalize whitespace; store compressed text privately and hash the uncompressed normalized bytes.
  3. Write one manifest containing every attempted outcome, including blocked and failed rows.
  4. Compute a daily Merkle root over the stored-content hashes in deterministic catalog order.
  5. Compare adjacent complete manifests. Different hashes become review candidates; no body or unified diff crosses the public reader.

Seal limitation: the daily root is a local tamper-evidence commitment. It is not, by itself, an independent timestamp, notarization, legal opinion, security audit, or guarantee that the source text was complete. The public source URL and capture date remain the provenance for each candidate.

Latest Merkle root: 251f71196528a12b61f117c3b2d75ac49d8ebd006405e774d44ce2e941a6be3e
Manifest SHA-256: cc1504b11d3a67c79f072c699c9ea1f58a89c85422cd9382d61a73cbef743250
Leaves: 155
Sealed at: 2026-08-08T23:13:21.276451+00:00

What is deliberately withheld

This page does not publish stored policy text, copied passages, unified diffs, page titles, fetch-error detail, block-reason text, cookies, response headers, or contacts. It does not assert motive, legal effect, effective date, or materiality. The public record is the smallest reproducible layer: source, dates, hashes, coverage, and method.

Browse other data services · Earlier sealed-evidence experiments · US Tech Automations