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.
Public URLs via the dashboard, login-protected views via the browser extension. The page exactly as your real browser shows it.
Four independent integrity layers — manifest, hash chain, Bitcoin anchor, eIDAS qualified timestamp. Verifiable by any third party, offline.
RFC 3161 qualified timestamp from an EU-qualified Trust Service Provider (SK ID Solutions). Recognized across EU/EEA under Regulation 910/2014.
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.
Litigation-grade web evidence with eIDAS + Bitcoin anchor
Preserve online content for disputes — admissibility-ready Evidence ZIP, hand to counsel or forensic expert, verify offline.
Volatile evidence with chain of custody
OSINT, fraud, due diligence — fast field capture (public + behind-login), forensic chain of custody, counsel-ready handoff.
Citation-grade evidence — preserve before stealth edits
Public Proof ID URL you can cite from the article — readers re-verify it themselves. Stealth-edit detector for newsrooms and fact-checkers.
Takedown-ready IP evidence — before the trail vanishes
Counterfeits, copycat shops, brandjacking, UDRP, DSA Article 16, marketplace VeRO — Evidence ZIP designed for the takedown form.
Point-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.
Capture 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.
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.
Every file in the Evidence ZIP has its hash recorded in manifest.json. Editing a single byte — even reformatting whitespace — fails the integrity 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 GetProofAnchor and of any platform involved.
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 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 | Citable Proof ID URL — readers re-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
Cross-audience answers — for role-specific FAQs, see the individual solution pages above. Tap to expand.
Are the six solutions different products, or the same product with different framing?
Which solution should I pick if my role isn't on the list?
Can I use multiple solution workflows on the same account?
Is the eIDAS qualified timestamp the same across all six solutions?
Can the Evidence ZIP be verified by someone who doesn't use GetProofAnchor?
Can I capture content behind authentication regardless of which solution I use?
Reference material
Deeper reading on the underlying technology — applies to all six workflows:
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
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.