The photo predates the claim
The date written in the file changes in one click. Nothing says when the photo was really taken, nor whether the damage existed before the policy was signed.
Business · Insurance and loss adjusting
The claim photo, taken inside the app, not sent over a messaging app.
You send the policyholder a link. The photo comes back dated, located, tied to the device, and your own tool decides whether the simple case goes straight through. Nobody squints at a photo to guess whether it was retouched.
30 days, 100 test proofs through the API. No card. Link requests and webhooks open in a pilot.
The problem as it is lived
Remote adjusting rests on photos sent by the policyholder. A photo received over a messaging app has no reliable date, no place, no origin.
It is not the insured property
A water leak photographed at a neighbour’s, a car that is not the one on the policy. With no place recorded at the shutter, the photo does not say where it was taken.
The image was edited
A crack widened, a scratch added, a photo found online. The case handler chooses between trusting and sending an adjuster.
What the proof establishes here
The same three checks as on any Evidiq proof, read in the terms of a claim file.
What it establishes
- That the photo was taken inside the app, on a device that attested it on submission, and at what level.
- The latest date at which the file existed, anchored outside our servers.
- The area recorded at the shutter, and whether it matches the risk location you stated in the request.
- That the file has not changed since it was sealed.
What it does not establish
- That the damage is real, nor its cause, nor its amount. A staged scene photographed live is still a staged scene.
- That the claim is covered. That is your decision, and it stays yours: the verdict has no button, and your rubric does not change what the proof says.
When a case goes to review, the verification page says why: which check failed, or could not be measured. The adjuster who receives the link reads the same page as you. Understand a proof.
How it works
Insurance’s channel is the capture link: the policyholder has no account and never will.
A request from the dashboard, or through the API.
Instruction (“the bathroom ceiling, then the water meter”), expected place, claim reference. Link, QR code or e-mail, revoked from here.
On site, inside the app, with your instruction in view.
They install the app (iPhone or Android), read who is asking what and what their data is used for, then capture live. Never from their gallery.
The proof arrives through a signed webhook.
The simple case goes straight through. The others go to review, with the reason written on the verification page. The full flow.
A real proof, as your adjuster will see it
The demonstration proof, the same as on the home page. The whole card is a link to the real verification page.
What a claims handler asks
Does my policyholder have to install anything?
Yes, the Evidiq app, on iPhone or Android. It is the app that captures live and asks the device for its attestation: without it there would be no proof, only a photo. They have no account to create: they open your link, read who is asking what and what their data is used for, capture, and watch their proof leave.
What does the policyholder see of my decision?
Nothing. They see your instruction, their capture, and the confirmation that their proof has left. The verdict, the checks and your rubric stay in your dashboard. You revoke the link from that same dashboard, at any time.
What if they photograph a photo, or a screen?
Capture happens inside the app, never by import: to cheat, you have to film a screen or a print. Measurements look for that re-capture and the verification page says what they noticed, or that they could not conclude on that device. They flag, they do not decide. What decides is the origin: the attested device, the date, the area, and the intact file.
The sourced figure on fraud is on the Business page. The other industries: construction, property inventories, delivery.
Start with one claim.
A pilot is scoped against your volume and your type of claim. The sandbox gives you the API right away, with no card.
Hosted in FranceEncrypted at restThe verdict has no buttonWhat proves it