Capture the web as tamper-evident evidence — not just screenshots.

GetProofAnchor captures web pages as tamper-evident evidence. It creates a verifiable record of what was visible online at a specific time and lets others later verify whether the evidence still matches the original captured state.

A screenshot shows appearance, but by itself it does not reliably prove source, capture time, or later integrity. GetProofAnchor adds structured metadata, cryptographic hashes, timestamps, and verification artifacts so later changes become detectable.

Tamper-evident means changes are detectable. The captured files (screenshot, page.html, extracted text and the other sealed artefacts) are bound by their SHA-256 hashes into a qualified timestamp. If someone modifies any of them later, verification fails. The PDF report, proof.json and manifest.json are generated at download and are not sealed — the sealed files and the verification result are what count.

A Proof ID is the permanent identifier of a capture. You can share it as a reference and later use it to load the public proof record or connect it to an exported Evidence ZIP.

The Evidence ZIP is a portable evidence package. Depending on the capture, it can contain a screenshot, extracted content, page.html, proof metadata, a manifest with SHA-256 hashes, timestamp artifacts, and blockchain anchoring artifacts.

It lets evidence leave the platform in a portable form while preserving later verifiability. Instead of sharing just an image, you can share a package that can be independently checked for integrity.

The manifest lists the files in the package together with their SHA-256 hashes. During verification, hashes are recalculated and compared, and the hashes of the captured files are also checked against the payload sealed by the qualified timestamp. The manifest itself is generated at download and is not sealed, so a changed captured file fails verification even if someone rewrites the manifest.

Yes. The Evidence ZIP is designed for offline or independent verification workflows because it contains the files and integrity data needed to re-check whether the package still matches its original recorded state.

SHA-256 is a cryptographic hash function. It creates a fingerprint of a file or payload. Even a very small change produces a different hash, which is why it is useful for integrity verification.

If someone changes a sealed file — the screenshot, page.html, extracted text, network log or capture metadata — its hash no longer matches the payload sealed by the qualified timestamp and verification fails. The report, proof.json and manifest.json are not sealed: rely on the sealed files and the verification result, not on the report alone.

An eIDAS-qualified timestamp proves that a specific hash existed at a specific time, based on a trusted timestamping authority. It does not store the webpage itself; it timestamps the cryptographic fingerprint of the evidence payload.

OpenTimestamps anchors a cryptographic hash into the Bitcoin blockchain. That provides public, independently checkable existed-before evidence for that hash. Because the anchor is tied to the hash, it also supports later integrity verification.

Not for the sealed files. Their hashes are fixed inside the qualified timestamp, which cannot be re-signed without the timestamp authority's private key — recalculating them only creates a mismatch. The report, proof.json and manifest.json are not sealed, so always verify the package (gpa-verify or the Verify page) instead of trusting those files alone.

Yes, it can be submitted — the Evidence ZIP is prepared for use as evidence. A qualified eIDAS timestamp carries a statutory presumption of the accuracy of its date and time and of the integrity of the timestamped data, and electronic evidence may not be denied legal effect merely because it is electronic. Whether and how a specific piece of evidence is used is always decided by the court — which is why the package can be independently verified by the court and the opposing party alike.

Yes. The browser extension captures what you actually see, including authenticated pages you lawfully have access to.

Yes — if you captured it in time. The evidence shows what was published or visible at that moment, even if the page later changes or disappears.

Chain of custody describes how digital evidence is captured, handled, and preserved over time. For credibility, it is essential to demonstrate content integrity, capture time, and traceability of the evidence. GetProofAnchor supports these principles using cryptographic hashes (SHA-256), file manifests, timestamps (including eIDAS), and blockchain anchoring, so that any modification of the sealed evidence files can be detected.