destill.ai · Insurers · Six roles · Trust Center

For claims adjusters and SIU

The damage photo you received: was it changed after it was taken, and where?

The policyholder photographs the damage live in ProofCam. The photo is sealed in that moment. When the file reaches you, you drop it into the heatmap: no red means no pixel block differs from the seal; red blocks show exactly which 16×16 pixel areas were edited. It runs in your browser, the photo does not leave your device.

Open the heatmapOpen ProofCam (camera)

ProofCam in 35 seconds

Full film with the live walkthrough (2:06)

Voice: neural text-to-speech · Deutsche Kurzfassung

The claim in four steps

  1. Capture liveThe policyholder opens ProofCam on the phone and photographs the damage with the in-app camera. Gallery uploads cannot get this seal.
  2. Sealed at captureProofCam stores a signed fragility map of the photo inside the PNG file.
  3. Send the original PNGThe policyholder sends the sealed PNG file to you (e-mail attachment or file upload, not as a chat “photo”, see below).
  4. CheckYou drop the received file into the heatmap. Green: unchanged since sealing. Red blocks: changed exactly there.

What the heatmap told us, measured

A local test on 28 October 2026 with one synthetic scene, sealed in ProofCam, then changed:

What happened to the fileHeatmap
Nothing (original sealed PNG)no red block: “Unchanged since sealing”
A scratch painted onto the damage23 red blocks, exactly on the scratch
Saved again as JPEG (quality 0.82), nothing else4,096 of 4,096 blocks red (12.52 % sign flips): the whole photo counts as changed

One scene, one edit, one re-encode: this shows that the method localises an edit, not how often it does so across real claim photos. A pilot measures that on your material.

How the photo must travel

ChannelWhat arrivesResult
E-mail attachment, upload portal, cloud link (original PNG)the file as sealedcheckable
WhatsApp or Telegram sent as photore-compressed JPEG; the certificate is strippedwhole map red; to check at all you need the original sealed PNG as photo 2
Telegram sent as fileexpected: the unchanged PNGnot measured yet; ask for e-mail or upload until it is

Any re-compression counts as a change on purpose: the seal is meant to break when pixels change. If photo 1 is a re-compressed copy, the heatmap accepts the original sealed PNG as photo 2; the pixels are still read from photo 1.

What a green result proves, and what it does not

It proves: the pixels are unchanged since the photo was sealed.

With the Android app (ProofCam 0.3) the seal file (FORTRESS-SEAL/1.0) is signed by a hardware key in the phone, and Google's attestation of that key also proves that the genuine, unmodified ProofCam app on a genuine, boot-verified phone sealed exactly these bytes. A seal made in the browser version has no such anchor: it proves only "unaltered since sealing", and a certificate built by someone else would also verify.

It does not prove what was in front of the lens: a photo of a screen gets a valid seal, and we do not detect that reliably today. It does not say who took the photo or whether the damage is real, and it does not say the photo is “not AI-generated”. The badge says “Captured live & unaltered”, nothing more.

Live capture only: the fragile seal is applied only to photos taken in the ProofCam camera, never to an uploaded or imported file, because an uploaded file could already be AI-generated.

Limits: the map reads brightness in blocks of 16×16 pixels on a 1024×1024 working size. A colour change that keeps brightness almost the same may be marked only in part, or reported as “changed, not located”.

What this means for fraud: edited, borrowed and old photos are the part of claims fraud a live seal can shut out. Which part that is, which part it is not, and the pilot threshold we measure against: the fraud audit.

Check a photo nowRequest a pilot