Features
Evidence provenance customers and carriers can trust.
Every photo, every thermal frame, every report gets a SHA-256 hash recorded in your portal the moment we deliver. A year later, you can prove the bytes haven't moved — and so can we.
At a glance
Every photo, every thermal frame, every report gets a SHA-256 hash recorded in your portal the moment we deliver. A year later, you can prove the bytes haven't moved — and so can we.
Why this matters when a claim is disputed
"Is this photo really from June 12th?"
A signed PDF with an embedded SHA-256 hash of every photo it references can answer that without us. Your contractor or carrier recomputes the hash on the same file; if it matches, the bytes haven't changed since we handed them over. If it doesn't, something's been edited and they should ask why.
"Was this the same condition we quoted in spring?"
Every photo and thermal frame in your portal has a hash stamped at delivery and an immutable delivery timestamp. A year later, a contractor pulling the file gets the same hash; the bytes are the same bytes; the report is still attached to the same evidence — even if the file has lived on three of your devices in the meantime.
"Do you have records?"
The audit row in your portal is the answer. Each row names a delivered asset, its hash, who delivered it, when, and to whom. It's the chain you'd want if you ever had to argue your case in front of someone you didn't pick.
What's in the audit row
Each row records: the asset name; the content type (photo, thermal frame, report PDF, cinema reel); its SHA-256 hash at delivery; the source capture it was derived from (so a flagged thermal anomaly traces back to its raw frame); the staff member who delivered it; the timestamp; and the customer the row belongs to.
Rows are immutable. A correction creates a new row alongside, never replaces the old one. If you ask us to delete an asset, the imagery goes but the row stays so the deletion itself is provable — "asset X was delivered on date Y and deleted on date Z at the customer's request."
How to read it without an engineering degree
The portal shows a green check next to each asset and the literal hash string if you click into the row. If a contractor or carrier asks for verification, you forward them the asset and the hash. They recompute on their side and compare. That's it.
For the report PDF specifically, the document carries an Ed25519 signature in addition to its content hash, so a third party can verify the file was signed by Plenoptary's key without contacting us at all. The public key sits on the trust page; the verification command is published next to it.