Capture posts, reviews, and profiles — before they're deleted, edited, or denied.
Posts get edited, comments get hidden, accounts vanish, and screenshots are dismissed as fake. GetProofAnchor preserves the moment in a portable Evidence ZIP and shareable Proof ID, anchored in four independent integrity layers — so any later modification is provably detectable: Match / Modified.
Public posts via the dashboard, login-protected content via the browser extension.
Evidence remains valid even after the post, comment, or entire account is deleted.
Offline-verifiable by any forensic expert with python3 + openssl + ots — even years later.
What this is: an evidence-preservation workflow for online reputation cases — cryptographic integrity verification + EU-qualified timestamp + Bitcoin anchor. The captured evidence remains valid even if the original content, profile, or platform disappears.
What this is not: legal advice, content moderation, takedown service, or a guarantee of court admissibility. Admissibility depends on jurisdiction and circumstances.
Designed for the “the post never existed” and “your screenshot is doctored” arguments.
Public URL via the dashboard, or login-only content (private profiles, paid platforms, restricted forums) via the browser extension — exactly as your real browser shows it.
Self-contained, offline-verifiable bundle: full-page screenshot + captured DOM + extracted text + SHA-256 manifest + hash chain entries + Bitcoin OpenTimestamps receipt + eIDAS qualified-timestamp kit + bilingual verification README.
Share the Proof ID URL with PR, legal, or platform trust-and-safety teams. Verification is deterministic: Match (intact) or Modified (per-layer report). Works online or fully offline.
What reputation teams capture with GetProofAnchor
Built around content that disappears or shifts the moment a dispute escalates — the exact moment evidence becomes critical.
X/Twitter, Facebook, Instagram, LinkedIn, TikTok, Threads — content that authors can edit or delete the moment pressure starts.
Google, Yelp, TrustPilot, Glassdoor, App Store, Booking, TripAdvisor — false or defamatory reviews that vanish during dispute or moderation.
Reddit, Discord, news-site comments, niche forums — pile-on comments and coordinated harassment threads that often get deleted en masse.
Posts targeting an individual or executive — including ones quietly removed once challenged or reported.
Brigading, dog-piling, mass replies, screenshots being reposted out of context — captured at the moment they occur, not after the platform cleans up.
Fabricated screenshots, false attribution of statements, misattributed quotes — preserved with the actual URL and capture metadata showing the original context.
Why this evidence holds up after the post is gone
A plain screenshot is easy to dismiss as fake — and once the original post is deleted, you have nothing to compare it to. GetProofAnchor anchors every capture in four independent integrity layers, and three of them keep working even if the post, profile, or entire platform disappears.
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 a 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 social platform.
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 believable. Any layer FAILS → modification is detected, with a per-layer report showing exactly which one was tampered with.
Why a screenshot dies the moment the post is deleted
In reputation disputes, the opposing side's first move is to delete or edit the original. After that, your screenshot is just a pixel array against their claim that “it never said that.” Without an integrity mechanism and an independent time anchor, a screenshot proves nothing about when or whether the content existed.
Evidence ZIP includes a SHA-256 manifest of every file. Subsequent edits — text, screenshot pixels, file replacement, even JSON whitespace reformatting — become mathematically detectable. No need to trust the screenshot alone.
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). The post can be deleted, the account can vanish — both anchors keep working.
A standardized, self-contained bundle of around 24 files (format: getproofanchor-evidence-1). Designed to be stored, sent to PR or legal teams, attached to platform takedown requests, 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, Bitcoin anchor info
- screenshot.png — full-page screenshot at capture time (the visible state of the page)
- 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 sharing with PR, legal, or platform teams
- 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 adds in reputation cases
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, even when the original platform is uncooperative or the content is gone.
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 or the original platform 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 about reputation evidence
Direct answers to the questions we hear most often. Tap to expand.
Can you capture a post that has already been deleted?
How is this better than just taking a screenshot?
Can it capture content behind login (private accounts, paid platforms, restricted forums)?
What about deepfakes, manipulated images, or fake quotes attributed to me?
Will the evidence still work if the platform removes the post or the user deletes their account?
Is this useful in defamation, harassment, or cyberbullying cases?
Reference material
Deeper reading for PR teams, reputation managers, and the lawyers or 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
Capture before the post vanishes
Tamper-evident snapshots of social posts, reviews, profiles, and forum threads. Capture once, prove later — even after the original is deleted.