When the post you're studying gets deleted six hours after you screenshot it.
Researchers studying online speech, disinformation campaigns, hate networks, harassment patterns — your evidence is ephemeral by design. Accounts get suspended, posts get deleted, platforms purge entire datasets when policy changes. A sealed screenshot turns 'screenshot taken on Tuesday, account suspended on Friday' from your testimony into externally-anchored cryptographic proof: SHA-256 + ECDSA signature + OpenTimestamps anchor within thirty minutes of capture. The receipt URL slots into reviewer-facing methodology sections without 'how do we know you didn't doctor this.' It doesn't validate your interpretation — that's still peer review — but it removes a class of skepticism that wastes everyone's time.
Workflows researchers actually run
- 01
OSINT capture: seal screenshots as you take them, not at end-of-shift.
Investigative pace is fast; accounts disappear in hours. Seal each capture in the same browser session as the screenshot. The receipt timestamp = capture timestamp, ±seconds. Build your evidence corpus on a cryptographic foundation rather than reconstructing chain-of-custody later from filesystem mtimes.
- 02
Methodology section: cite the receipt URLs as supplementary material.
Reviewers and replicators can verify each screenshot independently — they don't need access to your raw capture archive. The receipt page shows timestamp, hash, signature, and (after thirty minutes) the OpenTimestamps anchor. Cite as 'screenshot sealed at <URL>; SHA <hash>'. Standard supplementary-material format.
- 03
Ethical review: receipts simplify IRB / IRB-equivalent submissions.
IRBs increasingly ask for evidence-preservation protocols. Documenting 'all captures sealed via receipts.you within session' is concrete, auditable, and externally verifiable. The data-minimization argument (only a hash leaves your machine) helps with privacy-of-subject objections.
- 04
Datasets: seal a hash of the dataset file, not the contents.
For research datasets too large to seal page-by-page, seal a single SHA of the bundle. The receipt proves the dataset was in this exact form at this timestamp — useful for replicating studies on deleted material, where the dataset itself might be the only remaining evidence of what existed.
What it maps to in your world
- OpenTimestamps anchor is a recognized scientific evidence preservation technique — used by archival projects and forensic tooling alike.
- Verification is offline-capable: with the receipt JSON, the public key, and the OTS proof, any replicator can verify your evidence without trusting us.
- Hash-only architecture is privacy-of-subject by design — useful for IRB submissions where preserving subject anonymity is mandatory.
- No per-seal cost at research-relevant volumes. Rate limits accommodate a working researcher's day (1000/min/IP, 10000/day/IP).
- Open-source verifier client; methodology sections can specify the verification command and reproduce the chain externally.
Questions this page answers
- “osint screenshot evidence chain of custody”
- “disinformation researcher evidence preservation”
- “academic research social media evidence”
- “ephemeral content preservation osint”
- “deleted account research evidence”
- “irb evidence preservation online research”
- “research provenance social media screenshot”
- “research reproducibility screenshot timestamp”
Specific answers
Is the OpenTimestamps anchor reviewer-acceptable for academic publishing?
OpenTimestamps is published research (Peter Todd et al., 2016) and is the de-facto standard for cryptographic timestamping of file hashes. Reviewers familiar with provenance literature will recognize it. For unfamiliar reviewers, cite the OTS paper alongside the methodology — the OTS reference client + the receipt JSON together replicate verification in two commands.
How do I cite a receipt in a paper?
Standard supplementary-material citation: 'Capture timestamped at receipts.you/r/<id>; SHA-256 hash <hex>; verifiable via OpenTimestamps proof at receipts.you/api/ots-status/<id>.' Reviewers can verify independently; the URL is permanent on our side.
What if my research subjects later request the screenshot be removed?
We never had the image — only a hash. There's nothing image-like to remove on our side. If the screenshot lives in your research archive and the subject requests its removal, that's a matter for your IRB and your research-data-management policy. The receipt's existence doesn't change subject-removal mechanics for the underlying material.
Can I batch-seal a corpus of N screenshots in one go?
Not in a single API call — each receipt is one seal. The /api/seal endpoint is unauthenticated and scriptable; you can wire a Python or Node script to seal N captures in sequence. At 1000/min/IP, the throughput supports any realistic research-capture volume.
What about live-capture from a research browser environment (Selenium, Playwright)?
Hash the screenshot bytes in your capture pipeline (Node's crypto.subtle or Python's hashlib), then POST the hash to /api/seal. The image never leaves your environment. The receipt URL is captured alongside the other metadata in your dataset row. We've seen this used for disinformation-monitoring pipelines at university research centers.
Is the receipt durable enough for longitudinal studies (5-10 year horizons)?
Yes. OpenTimestamps anchors are permanent (Bitcoin chain proof-of-work); our receipt rows are append-only; our public key is committed to lasting at least 20 years per our methodology. For decade-scale studies, also archive the receipt JSON and the public key locally — the receipt is portable independent of our continued operation.
Capture, seal, cite. Three steps to reviewer-resilient evidence.
Free, browser-only, no per-capture cost. Your research provenance becomes cryptographic rather than testimonial.