Preserve online content for disputes — sealed before it changes.
When a page is edited or deleted, the other side will call your screenshot fake. GetProofAnchor turns what you see into a sealed Evidence ZIP and a public proof link with a qualified eIDAS timestamp — anyone can check the result: Match / Modified.
NEWNo time? We capture it for you — from €49 + VAT→
Capture before it changes
Public URLs from the dashboard, behind-login content via the browser extension.
Package for the case file
Evidence ZIP with eIDAS qualified timestamp + Bitcoin anchor.
Verify anytime, anywhere
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.
Three steps, a few minutes
How legal teams use it
Designed for the “that was never published” and “your screenshot is edited” arguments.
Capture
Public URL via the dashboard, or behind-login views via the browser extension (the page exactly as your real browser shows it).
Seal and export the Evidence ZIP
Self-contained, offline-verifiable bundle: artifacts + capture metadata + SHA-256 manifest + hash chain entries + Bitcoin OpenTimestamps receipt + eIDAS qualified-timestamp kit + bilingual verification README.
Share and verify
Share the public proof link or hand the ZIP to the court, opposing counsel or an expert. Anyone can verify it online or offline — the result is Match or Modified, layer by layer.
Works for: articles, posts, claims, pricing, T&Cs, profiles, reviews, marketplace listings, analytics dashboards, internal admin pages.
What lawyers capture with GetProofAnchor
Built around real dispute triggers — content that often changes right after notice.
Misleading marketing claims
Websites, guarantees, comparisons, “certifications” that quietly disappear once the dispute starts.
Terms, pricing, policies
T&C, refund policy, SLA, price changes, disclosures — captured at the version your client agreed to.
Defamation & reviews
Posts, comments, review edits, statements on social profiles — captured before the author edits or deletes.
IP infringement
Copied content, listings, catalogs, product descriptions — including marketplaces with rapid takedowns.
Marketplace listings
Seller identity, product claims, availability, screenshots being argued as edited — preserved at capture time.
Behind-login dashboards
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.
Layer 1
SHA-256 file fingerprints
Every captured file in the ZIP is bound by its hash into the qualified timestamp. Editing a single byte fails the check. The report and manifest are not sealed.
Layer 2
Append-only hash chain
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.
Layer 3
Bitcoin anchor (OpenTimestamps)
Each proof's timestamped content is bound into a Merkle tree whose root is anchored to Bitcoin via OpenTimestamps. The ZIP includes the inclusion proof, so anyone can check offline that the anchor covers exactly this proof — independent of any company or authority.
Layer 4
Qualified eIDAS timestamp
RFC 3161 timestamp from an EU qualified trust service provider. Under eIDAS Art. 41(2) it carries a legal presumption of the accuracy of its time and the integrity of the sealed data.
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.
Cryptographic integrity verification
Evidence ZIP includes a SHA-256 manifest of every file. Subsequent edits — text, screenshot pixels, file replacement, even JSON whitespace reformatting — become detectable.
Two independent time anchors
Each proof gets two independent time anchors: an eIDAS qualified timestamp (with legal weight in the EU) and a Bitcoin OpenTimestamps anchor (preserved by the Bitcoin network). Any attempt to backdate a proof would be caught by verification.
What's inside the Evidence ZIP
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.jsonthe integrity baseline — SHA-256 hash of every other file in the packageproof.jsonmain record — source URL, final URL, capture time, SHA-256 fingerprints, eIDAS status, anchor infoscreenshot.pngfull-page screenshot at capture timepage.html + content.txtcaptured DOM/HTML and extracted plain-text contentcapture/capture_meta.jsonforensic capture metadata (engine, viewport, scroll, consent dialogs auto-handled)chain/*append-only hash chain entries linking this proof to the global chainanchor/anchor_receipt.otsbinary OpenTimestamps receipt with the Bitcoin merkle pathtimestamp/*complete eIDAS qualified-timestamp kit — RFC 3161 token, TSA certificate chain, frozen EU Trusted List snapshot, verification reportreport.pdfhuman-readable Evidence Report PDF — formatted summary suitable for case filesREADME.mdbilingual (EN + CS) verification guide with copy-paste commands using python3, openssl, ots
Verification result: Match / Modified.
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 gets an RFC 3161 timestamp from a qualified trust service provider on the EU trusted list. It is not a marketing label — it has a specific legal meaning under Regulation (EU) 910/2014 (eIDAS): it carries a legal presumption that its time is accurate and the sealed data are intact, recognised in all EU member states.
Qualified provider
The timestamp comes from a qualified trust service provider listed on the EU trusted list.
Legal presumption
Under eIDAS Art. 41(2) the date, time and integrity of the timestamped data are presumed correct unless proven otherwise. You don’t have to rely on GetProofAnchor’s word.
Verifiable offline
The certificate chain and a copy of the trusted list are inside the ZIP, so the timestamp can be checked without internet and without us — also after the timestamp certificate has expired.
Together with the Bitcoin anchor you get two independent time anchors — one with legal weight in the EU, one public and global — for the same evidence.
Common questions from legal teams
Straight answers to the questions we hear most.
Is GetProofAnchor a substitute for a notary, expert witness, or legal advice?
No. GetProofAnchor is a digital evidence preservation tool, not a legal service. It does not provide legal advice and does not guarantee admissibility. What it does provide is a tamper-evident, cryptographically anchored record of online content that any forensic expert can independently verify offline.
Can the evidence be admitted in court?
Admissibility depends on jurisdiction, court, procedure, and the specific dispute — that is decided by the court itself. GetProofAnchor's role is to provide a verifiable, tamper-evident, time-anchored record. The eIDAS qualified timestamp carries a legal presumption of the accuracy of its date and time and of the integrity of the timestamped data under Regulation (EU) 910/2014 (Art. 41(2)), and is recognised in all EU member states. The Bitcoin OpenTimestamps anchor adds a second, independent time anchor on a public blockchain.
Can you capture content behind login (admin dashboards, social media accounts, paywalled articles)?
Yes — that is what the browser extension is for. Available on every paid plan, including the 9 € Starter Pack, the Chrome extension captures exactly what your real browser is showing, including pages that need login, 2FA, paid subscription, or a specific session. Public URLs can also be captured server-side via the dashboard.
What is in the Evidence ZIP and how does an expert verify it?
The Evidence ZIP is a self-contained, offline-verifiable bundle of around 24 files: the captured screenshot, page HTML, extracted text, capture metadata, manifest with SHA-256 of every file, hash chain entries, Bitcoin OpenTimestamps receipt, and the full eIDAS qualified-timestamp kit (RFC 3161 token, TSA certificate chain, frozen EU Trusted List snapshot, verification report). The bilingual (English + Czech) README walks an examiner through verification using only python3, openssl, and the ots client. No GetProofAnchor service or account is required.
What happens if the evidence is challenged later?
Verification is deterministic. Any modification of a sealed file — editing the extracted text, changing a screenshot pixel or replacing a captured file — fails the check. The result is clear-cut: verified (the sealed files are byte-identical to the original capture and the trust layers check out) or failed (with a per-check report showing exactly what failed). The PDF report, proof.json and manifest are generated at download and are not sealed, so in a dispute rely on the verification result, not on the report alone.
How long does the evidence stay verifiable?
The package is designed for long-term offline verification. The TSA certificate chain and a snapshot of the trusted list that lists the TSA are bundled inside the Evidence ZIP at capture time, so the qualified timestamp can be checked without an internet connection and without us — also after the TSA's certificate has expired. The Bitcoin anchor is an additional, independent layer. The hash manifest is verifiable with standard SHA-256 tooling. Keep the original ZIP: it is the evidence.
Further reading
Deeper reading for legal teams and the forensic experts you'll hand the Evidence ZIP to:
How it works
How GetProofAnchor works — capture, sealing, Evidence ZIP, verification
Open →Getting started
How to create a proof — from a URL or with the browser extension
Open →Reference
Evidence ZIP — every file inside, verifiable offline
Open →Verification
How to verify evidence — proof link or ZIP, online and offline
Open →Assisted Capture
Don't want to do it yourself?
Send us the URL and our team creates the forensic capture for you — full Evidence ZIP with eIDAS qualified timestamp, delivered to your inbox. From €49 per capture.
Secure the evidence before it’s gone
Capture before content changes. Package it for the case file. Verify it later — online or fully offline.