Our story
EverStamp grew out of frustration. Returning a hire car on a business trip, we ended up in an argument about damage to the vehicle. We had taken photos carefully, and still the return turned into a real dispute. With a great deal of effort we were proved right, but on the flight home we thought: this has to change. When we brainstormed, we saw many more situations where photos can be a source of argument:
A deposit held back for a mark that was already there. A snag the builder says appeared after the handover. A leak from upstairs that, according to the neighbour, is old. Damage to property where the insurer wants to see evidence. Every time there was a photo, and every time it settled nothing, because the other side had no reason to believe when or where it was taken.
For a long time a photograph was close to an argument-ender. Pictures could always be doctored; what changed is that everyone now knows it. The moment anybody can say “that could be fake”, a real photo loses its weight too, and the person who took it has no way to show otherwise.
The usual answer is a bigger claim: apps that promise ‘tamper-proof’ or ‘court-ready’ photos without naming a standard or explaining a mechanism. We think the answer runs the other way. Say precisely what is established, say precisely what is not, name the standard, and make the whole thing checkable by someone who has never heard of us.
‘When and where a photo was taken is often what the argument is about. With EverStamp the other side can check for themselves what is established, and what is not.’
So we built the opposite of a bigger claim. The app puts the date, time and place into the image, keeps the photos together as one file, and has an independent service timestamp the file when it is closed. Whoever receives it checks it in the browser, and every check but one also runs on ordinary public tooling.
That makes the product smaller than the promises around it, and that is the point: a claim you can check is worth more than one you have to believe.