Vendor Page Hash-Change Candidate Record
One retrospective, buyer-scoped record for a diligence, renewal, or dispute question about one vendor already present in our sealed archive.
Read this boundary first. A SHA-256 difference means only that the normalized bytes we stored for one URL changed between two capture dates. It is a review candidate, not evidence that a vendor promise, term, meaning, materiality, compliance status, or legal obligation changed. Formatting, CDN behavior, sessions, localization, and A/B variation can change a hash without changing the substance a buyer would read.
A dated pointer record for one vendor question
$249 one time
For a procurement, privacy-operations, or vendor-risk lead who already has a specific vendor and review interval in mind. The scope covers one archived vendor, one interval fully inside our sealed dates, up to three archived terms, privacy, acceptable-use, data-use, deprecation, or policy surfaces, and at least one observed normalized hash-transition candidate.
What the record includes
- The exact archived source URL for every scoped surface.
- Each pair of capture dates bracketing an observed transition.
- The before and after SHA-256 digests for normalized stored bytes.
- Daily manifest-hash and local Merkle-root references for the paired captures.
- Blocked, failed, dead, and missing observations inside the selected interval.
- A concise human disposition separating likely template or navigation churn from a candidate worth the buyer's own substantive review.
Stored page text, page titles, response headers, cookies, detailed error strings, and line-by-line change output are never delivered. Stored source expression remains withheld. The record supplies factual coordinates and digests, not copied vendor text.
Coverage is counted before payment
Before accepting an order, we state the eligible source URLs held for the vendor, the usable archive window, every known gap in the requested interval, and the exact number of transition candidates in scope. That suitability check prevents an empty record from being sold as a result.
We decline before payment when the vendor sits outside the frozen panel, the requested period predates the first seal, relevant seals are incomplete, suitable surfaces are unavailable, or the candidate count is zero. A missing or blocked capture is a coverage gap, never an unchanged page.
The archive supporting this offer
The verified archive currently spans 2026-07-10 through 2026-08-08. Its reader rechecks complete manifests, stored-content hashes, and seal bindings before exposing counts. It currently carries 30 sealed days, 74 companies, and 186 catalog surfaces. Across that window it found 261 normalized hash-transition candidates; that is archive coverage, not buyer demand and not a count of substantive policy changes.
Inspect the free aggregate Promise Archive. The free page shows aggregate coverage and recent public candidates. This paid record adds buyer-specific assembly, complete scoped gap accounting, human disposition, and an exportable dated PDF and CSV for one internal file.
Method and integrity boundary
Public pages in the frozen catalog are fetched on schedule with an identifying user agent and host pacing. Stored text is normalized, then hashed with SHA-256 as specified by the NIST Secure Hash Standard. Each complete daily manifest binds every attempted outcome, including blocked and failed rows, and a local Merkle root commits to the stored-content digests.
A transition localizes a difference to the window between two captures. It never establishes an exact change time. A local manifest and Merkle root can expose internal inconsistency, but they are not independent timestamps, notarization, certification, an affidavit, or proof that we could not rewrite our own archive. The public source and the buyer's own records remain necessary context.
How this differs from the monthly watch
The $499/month full-panel watch is prospective: it reviews the frozen panel across all catalog companies and surfaces after each month closes. This $249 record is retrospective and matter-specific. It answers one already-formed question about one vendor and one archived interval. It is not a discounted monitoring subscription and does not include future captures or renewal.
How the request works
- Name the vendor and question. State the diligence, renewal, or dispute interval you need reviewed.
- Receive the coverage count. We return eligible URLs, sealed dates, gaps, and candidate count, or decline with the reason.
- Confirm the boundary. Select one interval and up to three surfaces.
- Receive the record. After confirmation and payment, the private PDF and CSV arrive within three business days.
You decide what a transition means. We do not interpret vendor language, assess compliance, or label any candidate material, adverse, or breaching. Human dispositions are triage notes about the shape of an observed byte difference. This record is not legal advice and should be tested against the vendor's published sources, the buyer's own records, and qualified counsel.