Digital evidence must withstand challenge, whether captured from the web, from a smartphone, or brought from your own files. Provena preserves and seals every record with an auditable chain of custody and independent external proofs, making your evidence verifiable at any time.
A video, a photo, a screenshot, a message — any of it can be altered or faked from scratch. And digital content rarely waits: by the time a dispute reaches review, the page has changed or the post is gone. Provena turns online activity into a structured record: captured in a controlled environment, preserved with cryptographic integrity, and prepared for scrutiny.
The visible image matters, but so do the environment, the chronology, the source material, and a way for another person to test the record later.
| What reviewers need | Informal screenshot by itself | Provena record |
|---|---|---|
| Collection context | Usually supplied later from memory | Recorded with the capture session |
| Integrity history | No native modification trail | Files hashed and custody events linked |
| Source material | A single flattened image | Images, video, files, logs, and metadata |
| Later review | Depends on the sender's explanation | Public match checks and offline review methods |
Public verification checks a session code or local file hash. It does not open private evidence content.
Work in a dedicated remote browser while Provena preserves screenshots, MP4 video, downloads, page snapshots, and technical context, with a provenance mark rendered into each screenshot.
Captured files are hashed, custody events are linked in sequence, and the evidence package and material custody chain are sealed separately. When configured, their fingerprints can be submitted for independent external proof.
Reviewers can compare session and file hashes, validate the custody chain, and inspect confirmed external-proof references through public and offline workflows without opening private evidence.
The operator works in a controlled remote browser while the session preserves material and records custody as the work happens.
The session runs in an isolated remote browser rather than depending on the operator's everyday browser state.
Screenshots, MP4 video, downloads, page snapshots, and technical context are preserved during the session.
File hashes and custody events create a chronology that can be reviewed after collection.
Each completed session produces related outputs for different kinds of review. The evidence package preserves the collected material; the report, custody export, and external-proof records remain distinct review surfaces.
View a fictional sample report →When configured, Provena can register the sealed package hash and custody-chain seal with independent providers. Confirmation can complete asynchronously, and the report records whether each production proof is pending, confirmed, or failed.
Only cryptographic fingerprints are sent to external-proof providers. Evidence content is not written to a blockchain or uploaded to a timestamp authority.
How external proofs work →Supported provider families shown here: Solana, Hedera, Algorand, OpenTimestamps · Bitcoin, Sectigo, and DigiCert. Availability depends on deployment configuration.
Provena documents what the technical record can support and where factual, identity, or legal analysis must come from elsewhere.
A dedicated remote browser with an enforced interaction policy, visual provenance, and session context recorded as the work happens.
→Files are fingerprinted as they enter the record, transfers are checked, and custody events remain linked throughout the session lifecycle.
→Sealed package and custody fingerprints can be registered with independent public networks and timestamp providers.
→Reading modes, PDF/A-2B output, custody analysis, package inspection, logs, and audit guidance support different reviewers.
→The public check compares a session or locally computed file hash without uploading file content or opening private evidence.
→Every Provena report includes methodology, threat-model context, and audit instructions. Reviewers can inspect what was preserved, how integrity can be checked, and what the platform does not claim.
The same structured record can support legal, institutional, investigative, and individual workflows without changing its underlying integrity references.
Preserve online material before it changes and give reviewers a traceable technical record.
Standardize capture, custody, retention, and technical review across institutional workflows.
Create a structured record of disappearing pages, messages, listings, and publications.
Use the public check to compare a session code or a file hash. Local file content stays in your browser, and verification does not open private evidence.
Talk to us about pilots, workflows, and institutional adoption.