Preserve online content for disputes — with a 4-layer cryptographic trust stack.
When a page is edited, removed, or denied, screenshots alone are easy to challenge. GetProofAnchor creates a portable Evidence ZIP and a shareable Proof ID, anchored in four independent layers (manifest, hash chain, Bitcoin, eIDAS) — so any modification is provably detectable: Match / Modified.
Public URLs from the dashboard, behind-login content via the browser widget.
Evidence ZIP with eIDAS qualified timestamp + Bitcoin anchor.
Offline-verifiable by any forensic expert with python3 + openssl + ots.
What this is: an evidence-preservation workflow with cryptographic, tamper-evident integrity verification — including an EU-qualified timestamp and a Bitcoin anchor.
What this is not: legal advice, a notary act, or a guarantee of admissibility. Admissibility depends on jurisdiction and circumstances.
Designed for the “that was never published” and “your screenshot is edited” arguments.
Public URL via the dashboard, or behind-login views via the browser extension (the page exactly as your real browser shows it).
Self-contained, offline-verifiable bundle: artifacts + capture metadata + SHA-256 manifest + hash chain entries + Bitcoin OpenTimestamps receipt + eIDAS qualified-timestamp kit + bilingual verification README.
Online via the Proof ID, or offline by any forensic expert using python3 + openssl + ots. Result is deterministic: Match or Modified, with a per-layer breakdown.
What lawyers capture with GetProofAnchor
Built around real dispute triggers — content that often changes right after notice.
Websites, guarantees, comparisons, “certifications” that quietly disappear once the dispute starts.
T&C, refund policy, SLA, price changes, disclosures — captured at the version your client agreed to.
Posts, comments, review edits, statements on social profiles — captured before the author edits or deletes.
Copied content, listings, catalogs, product descriptions — including marketplaces with rapid takedowns.
Seller identity, product claims, availability, screenshots being argued as edited — preserved at capture time.
Account state, internal notices, portal terms, customer interfaces — captured with the extension from your real session.
Why GetProofAnchor evidence holds up under challenge
A plain screenshot is easy to dispute — anyone with a graphics editor can produce something convincing in minutes. GetProofAnchor anchors every capture in four independent integrity layers, each with its own files in the Evidence ZIP. Defeating any single layer doesn't break the others.
Every file in the ZIP has its hash recorded in manifest.json. Editing a single byte fails the check.
Each capture is part of a global SHA-256 chain. Each entry contains the hash of the previous one, so inserting or modifying any past entry breaks the chain mathematically.
The chain head is anchored to the Bitcoin blockchain. Once confirmed, the timestamp is preserved by the entire Bitcoin network — independent of any company or authority.
RFC 3161 timestamp from an EU-qualified Trust Service Provider (currently SK ID Solutions, Estonia). Recognized as legal-grade proof of existence at a point in time under Regulation (EU) 910/2014.
All four layers PASS → the package is cryptographically intact, not just trusted. Any layer FAILS → modification is detected, with a per-layer report showing exactly which one was tampered with.
Why a plain screenshot gets challenged
In disputes, the opposing side will argue the screenshot was edited — or that the content never existed in that form. Without an integrity mechanism, your only counter is your own credibility. GetProofAnchor adds independent, third-party-verifiable evidence on top of the screenshot.
Evidence ZIP includes a SHA-256 manifest of every file. Subsequent edits — text, screenshot pixels, file replacement, even JSON whitespace reformatting — become detectable.
Each proof gets two independent time anchors: an eIDAS qualified timestamp (legally recognized in EU/EEA) and a Bitcoin OpenTimestamps anchor (preserved by the Bitcoin network). Backdating becomes infeasible.
A standardized, self-contained bundle of around 24 files (format: getproofanchor-evidence-1). Designed to be stored in your case folder, sent to co-counsel, or handed to a forensic expert for independent verification.
- manifest.json — the integrity baseline — SHA-256 hash of every other file in the package
- proof.json — main record — Proof ID, source URL, final URL, capture time, SHA-256 fingerprints, eIDAS status, anchor info
- screenshot.png — full-page screenshot at capture time
- page.html + content.txt — captured DOM/HTML and extracted plain-text content
- capture/capture_meta.json — forensic capture metadata (engine, viewport, scroll, consent dialogs auto-handled)
- chain/* — append-only hash chain entries linking this proof to the global chain
- anchor/anchor_receipt.ots — binary OpenTimestamps receipt with the Bitcoin merkle path
- timestamp/* — complete eIDAS qualified-timestamp kit — RFC 3161 token, TSA certificate chain, frozen EU Trusted List snapshot, verification report
- report.pdf — human-readable Evidence Report PDF — formatted summary suitable for case files
- README.md — bilingual (EN + CS) verification guide with copy-paste commands using python3, openssl, ots
For a file-by-file walkthrough see the Evidence ZIP — every file inside tutorial.
eIDAS qualified timestamp — what it means in practice
Every GetProofAnchor proof receives an RFC 3161 timestamp from an EU-qualified Trust Service Provider. This is not a marketing label — it has specific legal meaning under Regulation (EU) 910/2014 (eIDAS) and gives your evidence a defensible time anchor in the EU and EEA.
Currently SK ID Solutions AS (Estonia), listed on the EU Trusted List as a Qualified Trust Service Provider.
Recognized in EU/EEA courts and regulatory proceedings as proof of existence at the timestamped moment, with no need to trust GetProofAnchor itself.
The full TSA certificate chain and a frozen snapshot of the EU Trusted List are inside the ZIP — verification works offline, even years later, even if the TSA later ceases operation.
Common questions from legal teams
Direct answers to the questions we hear most often. Tap to expand.
Is GetProofAnchor a substitute for a notary, expert witness, or legal advice?
Can the evidence be admitted in court?
Can you capture content behind login (admin dashboards, social media accounts, paywalled articles)?
What is in the Evidence ZIP and how does an expert verify it?
What happens if the evidence is challenged later?
How long does the evidence stay verifiable?
Reference material
Deeper reading for legal teams and the forensic experts you'll hand the Evidence ZIP to:
How GetProofAnchor works — capture, trust stack, Evidence ZIP, verification
How to create a proof from a URL — Dashboard + Browser Widget
Evidence ZIP — every file inside, offline-verifiable
How to verify evidence — Proof ID, ZIP, online & offline
Preserve online evidence in minutes
Capture before content changes. Package it for the case file. Verify it later — online or fully offline.