Workflow guide
A customer, supplier or platform dispute can turn on what a public page appeared to say at a particular time. Saving only the URL leaves the record exposed to later edits. Attest Capture can render that public page as PNG, PDF or HTML, store the artifact privately and return a timestamp, SHA-256 digest and public evidence-receipt URL. The receipt records the source URL and lets a reviewer check that retrieved artifact bytes match the digest shown on the record.
Capture the page as soon as the issue is identified, then inspect the returned artifact. Record the capture ID, exact UTC time, source URL, digest and evidence URL in the case file. If the artifact may be needed after the signed retrieval URL expires, download it within the 24-hour window and retain it using your organisation's approved storage and access controls. A PDF can be convenient for paged review, while PNG preserves the visual render and HTML preserves rendered markup. If several pages matter, capture each URL separately so every artifact has its own receipt and digest.
Attest deliberately does not call this a forensic chain of custody. The service records what its renderer saw; it does not identify who authored the page, prove that no other version existed, validate the truth of the content or establish legal admissibility. Dynamic elements, regional delivery and public access conditions can affect the result. Do not alter the downloaded bytes if you intend to verify them against the receipt's digest, and document any handling that occurs after retrieval. Legal teams or external decision-makers may require additional evidence, witness statements, platform records or collection procedures. Use the capture as a precise technical record inside that broader process, not as a replacement for it.