Send the policyholder a link with your own checklist. They photograph the damage before the clean-up, the file comes back sealed, and your adjusters and your claims system check it without taking anyone’s word for it.
Had damage yourself? How to photograph it for your insurer →
Whether the damage came from the storm or was there before, argued from photos nobody can date.
Pictures arrive by email and chat, without the serial numbers or the cause, and someone at your end types them into the claim.
An adjuster drives out for damage the policyholder could have photographed that afternoon, with the right checklist.
Whoever holds the phone, the file carries the same device signature, the same seal and the same registry entry.
You prepare a request with your checklist and a deadline. The policyholder completes it in the app, without an account, and the photos come back to the claim.
With the Damage assessment template or your own, on iPhone or Android, with a timestamp from an independent service.
Before and after the repair, with the Repair check template, delivered to the same claim.
The Damage assessment template asks for an overview, the damage in detail and the context, with room for serial numbers and the cause. In the dashboard you set up your own checklist per claim type, with your own fields.
A required step has to be there before the file closes, so a missing close-up shows up while the policyholder is still in the room. In your own checklist you can make the serial number required too.
A record of your house before the neighbours start digging or building.
Read more →A leak from upstairs, cracks in a wall, a dent in the car park.
Read more →Storm, water or a break-in, recorded before you start clearing up.
Read more →Requests to policyholders and the files of your adjusters meet in one dashboard, and through webhooks and the API they arrive where the claim already is.
For whoever wants to check, after a first conversation, exactly what is delivered. This comes with every file, also when the policyholder sends it through your link.
These two are made by whoever has the file in the app, and sent along when needed. They do not come with every file by themselves.
No. They open your link, see who is asking and why, and take the photos in the EverStamp app, which they install first if they do not have it yet.
Yes. A webhook tells your system when a request is complete, and the API delivers the file with its seal and registry entry. On Enterprise the archive is delivered to you.
Owners and administrators, and an API key of your organisation; field workers and readers cannot. Every opening through the dashboard or the API is written to your audit log, with who and when. Technically EverStamp can open them too, because we manage the key; we do that only at your organisation’s written request, or when a court or authority orders or demands it under the law.
No. No damage assessment, no fraud score, no AI looking at the image. We record when the photos were captured, on which device, and that nothing changed afterwards. What that means for the claim stays with your claims handler.
It shows where an image comes from: a file states that the photos were taken with our app on the device named in it, and the verification page confirms that against our registry. A photo of a screen is still a photo, so it does not rule anything out; your claims handler does see the difference between a file from the app and a loose image from a mailbox.
Nothing. Whoever takes the photos at your request pays nothing and takes out no subscription. You pay per file that comes in; sending a request costs nothing.
The timestamp is qualified under the EU eIDAS regulation. In the EU, Article 41 presumes that the date and time are accurate and that the photos have not changed since; in the United Kingdom the same rule applies through assimilated law. What the photos show, and what that means for the claim, is for your claims handler to weigh, and for the court in a dispute. EverStamp does not assess damage or score fraud.
Annex 1 of the terms points to the data processing agreement, which is in the dashboard and applies once you accept the terms; on Enterprise we sign it with annex B filled in, with DPIA material and a named contact. The data is stored in the EU, and how security is set up is at everstamp.app/security.
The price is on request, set by the number of claims and by how the files reach you: in the dashboard, through the API or delivered into your own system. Whoever has files delivered pays; whoever checks them never does. You pay for the files you have delivered, and checking through the link, the QR code on the report or the verification page is always free, without an account.
Pick one claim type, water damage or glass for instance, and run the requests alongside for three months. Measure what a claim costs in lead time and site visits, before and after. If you want to see it first, ask for a conversation; we bring the data processing agreement and the security page.
The property inside and out, with a dated record of the visit itself.
Read more →Check-in and check-out inspections, the same checklist in every home.
Read more →An observation on site, checkable by the other side without asking you.
Read more →