EVACby Duress

Duress Evidence · For incident recordings

Evidence shouldn't ask for trust.
It should survive without it.

Court-grade management for body-worn and incident recordings. Every byte checked on the way in. A chain of custody that can only grow. And a verdict anyone — a lawyer, a regulator, the person in the footage — can check for themselves, offline, without asking us.

Verify a bundle — no account, no install

Verified ingest

Checked at the door.
Committed only when it proves itself.

A recording earns its place in the record. Every byte is checksummed on arrival, and the cryptographic gates run before commit — never after.

Segment 0 · sha256Matches
Segment 1 · sha256Matches
Merkle rootReproduced
ManifestCommitted

Every byte is checksummed at the door. Each segment's hash, the tree they build, the manifest that names them — all checked before anything is accepted as evidence.

A file that fails a check never enters the record. The gates are cryptographic, and they sit in front of the commit — there is no "accept now, sort it out later".

No quarantine pile. What is in the record passed its checks. What didn't, isn't in the record.

Today, recordings arrive through the API and the reference client. Capture hardware is on its way; the evidence pipeline it will feed is the one already running.

Built pipeline-first, on purpose. The guarantees live in the platform, not in any one device.

Chain of custody

A record that only grows.

Append-only by design. Every custody event chains to the hash of the one before it, and signed checkpoints of the whole record are anchored in a public transparency log.

Nothing is edited. Nothing is deleted. A correction is a new entry that says so, chained to everything before it — the history of the record is part of the record.

Hash-chained, end to end. Changing one entry years later breaks every link after it, visibly.

checkpoint · tree size 9 · signed 09:49:45

✓ Anchored in the transparency log

Signed checkpoints, published. The log is public and append-only, so the record's history is committed to copies we don't get to rewrite.

Viewed · 09:12

Reason: disclosure preparation

LOGGED

Viewed · 11:47

Reason: supervisor review

LOGGED

Exported · 14:03

Reason: brief of evidence

LOGGED

Every look at evidence is recorded, with the stated reason. Who, when, and why — "just browsing" is not a reason the system accepts.

Verification without trust

Don't take our word
for any of it.

Anyone holding a disclosure bundle can check it against the public log — offline, in a browser, with no account and nothing installed. The defence does not have to trust the prosecution's vendor.

segments ✓ · merkle root ✓ · log inclusion ✓

✓ Structure verified — offline, no account

Drag a bundle onto the page. That's the whole procedure. Open the verifier →

The verifier never claims more than it proved. Every check reports pass, fail, or "not checkable here" — and the verdict names exactly what it does and does not establish.

Honesty is the feature. A verifier that rounds up is worse than no verifier at all.

Separately secured by design. Evidence lives in its own store, under its own keys, with no shared credentials with the safety platform.

Two systems, deliberately apart. A problem in one is not a problem in the other.

Court-grade means anyone can check.

Verify a bundle

The verifier runs in your browser and works offline once loaded. No account, no install, no data sent anywhere. Questions? support@duress.com