Workflow guide
Compliance work often requires a record of what was publicly displayed on a particular date: a policy page, disclosure, terms page, vendor statement or published control description. A normal bookmark points to the current page, not the version a reviewer originally saw. Attest Capture can add a timestamped PNG, PDF or rendered HTML artifact to the record, together with a SHA-256 digest and a public evidence page that identifies the source URL and capture time.
The capture should sit inside a wider evidence process. Name the requirement or control you are reviewing, record why the public page is relevant, call the API, then store the returned capture ID, digest and evidence URL with the rest of the review material. If your organisation needs long-term access to the artifact, retrieve it while the signed link is active and retain it under your own approved records policy. Attest stores the artifact in a private bucket and issues a 24-hour signed retrieval URL; the public receipt does not expose the artifact bytes directly. Use consistent format and viewport settings when a repeated process needs comparable renders.
A successful capture is not proof that an organisation complies with a law, standard, contract or internal policy. It does not validate the truth or completeness of the captured statement, inspect controls behind the page or create a forensic chain of custody. Access rules, retention periods, reviewer identity, approvals and legal interpretation remain part of the customer's own system. Public pages can also include dynamic content, consent banners or regional variants, so review the resulting artifact before accepting it as evidence. Attest supplies a reproducible technical receipt; the compliance judgement stays with the responsible reviewer.