Pick your workflow — capture, export, verify.
GetProofAnchor preserves online content as tamper-evident evidence — six role-tailored workflows backed by the same 4-layer cryptographic trust stack (SHA-256 manifest, hash chain, Bitcoin OpenTimestamps anchor, eIDAS qualified timestamp). Recognized across EU/EEA under Regulation (EU) 910/2014. Same forensic-grade Evidence ZIP, every role.
Verify a proof link or ZIP → · No time? We capture it for you — from €49 + VAT →
Capture (public + behind-login)
Public URLs via the dashboard, login-protected views via the browser extension. The page exactly as your real browser shows it.
Cryptographic chain of custody
Four independent integrity layers — manifest, hash chain, Bitcoin anchor, eIDAS qualified timestamp. Verifiable by any third party, offline.
Legal weight in the EU
RFC 3161 qualified timestamp from an EU qualified trust service provider, with a legal presumption of accurate time and data integrity under eIDAS.
Six tailored workflows
Each role page is built around how that work actually happens — the capture targets, the typical disputes, the handoff to counsel or auditor, the FAQs that matter to that audience. The cryptographic foundation underneath is identical.
LawyersLitigation-grade web evidence with eIDAS + Bitcoin anchor
Preserve online content for disputes — a sealed Evidence ZIP for counsel, the court or an expert, verifiable offline.
See the solution →
InvestigatorsVolatile evidence with chain of custody
OSINT, fraud, due diligence — fast field capture (public + behind-login), forensic chain of custody, counsel-ready handoff.
See the solution →
JournalistsCitation-grade evidence — preserve before stealth edits
A public proof link you can cite in the article — readers verify it themselves. Catches silent edits for newsrooms and fact-checkers.
See the solution →
Brand ProtectionTakedown-ready IP evidence — before the trail vanishes
Counterfeits, copycat shops, brandjacking, UDRP, DSA Article 16, marketplace VeRO — Evidence ZIP designed for the takedown form.
See the solution →
Compliance & AuditPoint-in-time evidence — what was published on date X
Audit-ready, versioned snapshots of disclosures, T&Cs, prices, and policies. Verifiable offline throughout your retention period.
See the solution →
ReputationCapture posts before deletion — survives account removal
Social posts, reviews, comments, profiles. Tamper-evident snapshots that stay valid even after the original post or account is gone.
See the solution →One trust stack underneath all six workflows
Whichever role page you arrive at, the underlying integrity guarantee is identical. Every capture is anchored in four independent integrity layers, each with its own files in the Evidence ZIP, each independently verifiable by a third party. Defeating any single layer doesn't break the others.
Layer 1
SHA-256 file fingerprints
Every captured file in the Evidence ZIP is bound by its SHA-256 hash into the qualified timestamp. Editing a single byte — even reformatting whitespace — fails the integrity check. The report and manifest are generated at download and 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 GetProofAnchor and of any platform involved.
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 well-organized. Any layer FAILS → modification is detected, with a per-layer report showing exactly which one was tampered with — turning a vague tampering accusation into a deterministic technical question.
Which solution fits your work?
A quick orientation table — pick by use case, not job title. The technical workflow is the same regardless of which row you land on.
| Role / Solution | Primary use case | Killer feature |
|---|---|---|
| Lawyers | Online content for disputes — claims, T&Cs, marketplace listings, posts that vanish after notice | Forensic-expert handoff — Evidence ZIP verifiable offline by independent counsel |
| Investigators | Volatile sources — OSINT subjects, banking dashboards, fraud sites, scam profiles, behind-login views | Cryptographic chain of custody — math instead of sworn affidavit |
| Journalists | Public statements — press pages, official posts, articles before stealth edits, source URLs | A public proof link to cite — readers verify it themselves |
| Brand Protection | Counterfeits, copycat shops, brandjacked profiles, MAP violations, domain squatting | Takedown-ready Evidence ZIP — VeRO, Brand Registry, UDRP, DSA Article 16 |
| Compliance & Audit | Disclosures, T&Cs, prices, consent banners, marketing claims at the version published on date X | Audit-trail timeline — versioned snapshots, verifiable through retention period |
| Reputation | Social posts, reviews, comments, profiles — before deletion, before account removal | Survives deletion — eIDAS anchor and Bitcoin anchor stay valid after the post is gone |
All six produce the same Evidence ZIP format (~24 files, format getproofanchor-evidence-1) and share the same 4-layer trust stack. Pick the role page closest to your use case — the technical capabilities are identical.
Common questions across all six solutions
Straight answers to the questions we hear most.
Are the six solutions different products, or the same product with different framing?
Same product, same trust stack — six workflows. Every solution exports the identical Evidence ZIP format (around 24 files, format: getproofanchor-evidence-1) anchored in the same four integrity layers: SHA-256 file manifest, append-only hash chain, Bitcoin OpenTimestamps anchor, and eIDAS qualified timestamp from an EU-qualified Trust Service Provider. The role pages differ in framing, use cases, and FAQs — not in the underlying integrity guarantee. A lawyer, a brand-protection officer, and a compliance auditor receive the exact same forensic-grade package.
Which solution should I pick if my role isn't on the list?
Pick the closest fit by use case rather than job title. Capturing online content for a contentious dispute → Lawyers. Volatile sources, behind-login pages, chain of custody → Investigators. Citing public statements before they change → Journalists. Marketplace listings, IP infringement, takedowns → Brand Protection. Auditor-facing point-in-time records → Compliance & Audit. Social posts, reviews, profiles before deletion → Reputation. Insurance investigators, fraud teams, internal auditors, OSINT analysts, NGO researchers — all map cleanly onto one of the six. The technical workflow is identical regardless.
Can I use multiple solution workflows on the same account?
Yes. There is no per-role configuration — a single GetProofAnchor account works across all six workflows. The role pages exist to show how the same capabilities map to your specific use case, not to gate features. If your team handles compliance one day and a reputation case the next, the same account, dashboard, browser extension, and Evidence ZIP format cover both. Plan limits (capture quota, behind-login capture availability) apply at the account level, not per workflow.
Is the eIDAS qualified timestamp the same across all six solutions?
Yes — every capture, on every workflow, receives the same RFC 3161 qualified timestamp from an EU-qualified Trust Service Provider (listed on the EU Trusted List). It carries the same legal presumption under Regulation (EU) 910/2014 (Art. 41(2)) in every EU member state, regardless of which role page you came from. Brand-protection captures, compliance attestations, journalist citations, and lawyer evidence packages all carry identical qualified time anchoring.
Can the Evidence ZIP be verified by someone who doesn't use GetProofAnchor?
Yes — that is a primary design goal across all six solutions. The Evidence ZIP is fully self-contained and offline-verifiable using only python3, openssl, and the ots client (from the standard opentimestamps-client package). The TSA certificate chain and a copy of the trusted list are bundled inside the ZIP, so eIDAS verification works even without internet, also after the TSA certificate has expired. A bilingual EN+CS README walks through each verification step. No GetProofAnchor account, service, or website access is required for the integrity check.
Can I capture content behind authentication regardless of which solution I use?
Behind-login capture (private dashboards, paywalled content, internal admin views, restricted seller portals) is available via the Chrome browser extension on every paid plan, including the 9 € Starter Pack. The capability is identical across all six workflows — a lawyer capturing a banking dashboard, a brand-protection team capturing a private seller portal, a journalist capturing a paywalled article, and a compliance officer capturing an internal control attestation all use the same extension and produce the same Evidence ZIP format. Cookies, passwords, and browsing history never leave your machine — only captured page artifacts are uploaded.
Further reading
Deeper reading on the underlying technology — applies to all six workflows:
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 →Same trust stack, your workflow
Tamper-evident web evidence with cryptographic integrity, EU-qualified timestamp, and a Bitcoin anchor. Verifiable offline by anyone, regardless of which solution you started with.