Capture provenance for insurance claims
Claim photos that prove themselves.
An AI editor can add damage to a photo in seconds, and genuine photos get reused from one claim to the next. Proofshot seals each photo on the policyholder's phone at the moment of capture, so anyone can check it later without trusting us.
Matches a photo sealed 12 Sept 2026, 14:05, but 1 of 16 regions was changed after sealing.
How it works
Sealed at capture
The policyholder takes the photo in Proofshot. One Face ID prompt signs it with a key that never leaves their phone, and a public ledger checks that signature before recording the seal.
Checked from any copy
Anyone holding any copy, even one compressed by a messaging app, can see when it was sealed and exactly which regions were changed since.
Reused photos caught
Carriers share fingerprints, never photos. A photo already used in another claim, at any carrier, raises a Duplicate Alert.
Don't take our word for it
Every claim on this page can be checked from public data.
Verified onchain, on Monad
The Registry contract checks each seal's passkey signature (P-256) with Monad's built-in support for it before recording it. No wallet, no extra app.
Reproducible without us
An open-source verifier reads the public registry and reaches the same result as this site, for any copy of a photo.
Fingerprints, never photos
Photos go only to the insurer. The registry holds hashes and visual fingerprints, which can't be turned back into the image.
What a Seal proves, and what it does not
It proves
- A specific device key signed these fingerprints.
- It happened within a tight, public time window.
- Whether the image changed since, and where.
- Whether the same picture already exists in another claim.
It does not prove
- That the pixels came from the camera sensor. Hardware attestation is our next milestone.
- That the scene is what the sender says it is.
- Who the person taking the photo is, legally.