EverStamp
Home › Features

EverStamp features

Make the captures, work through the checklist, close the file. That is all the person making the captures has to do: the app puts the date, time and place into the image, works without a signal, and has an independent service timestamp the file. Below is everything the app and the dashboard do, part by part.

Overview

From the first capture into your own system

The EverStamp camera with the stamp bar in the viewfinder

Capturing

On site, with wet hands: the app says what is still missing and draws the details into the image.

The stamp barDate, time, address and company name drawn into the image, on a printout too. The time is the device clock.
ChecklistsSteps with a minimum number of photos, so the file says what is still open.
Fields per stepLicence plate, meter reading, serial number, date, a choice from a list. Under the same signature as the photo.
Text recognitionThe app reads along in the viewfinder at that step and proposes the plate or the meter reading. You confirm it, and your confirmation is what counts.
Signed on the deviceiPhone and Android both. The key lives in secure hardware and cannot be exported.
Share linksEncrypted on the device; the key sits in the link and never reaches us. On Basic up to 30 days; on Plus up to 90 days, with a password if you want one.
A sealed file in the app, with the stamp and the entry in the registry

Sealing and checking

Signed on the device and sealed by an independent service. Every check but one works without us, and the confirmation for green comes from our registry.

VideoVideo in the file too, up to 10 minutes, with sound. The stamp bar is in every frame, and each video gets a timestamp of its own. The recipient checks it in the browser. On Plus to try, more with Plus Video or the video module of Business.
The qualified sealA timestamp from a supervised service on the European trust list, applied when the file closes.
Check it yourselfDrag the file onto a page. Every check but one works without us; the confirmation for green comes from us, as the registry’s signature in the file or as a question to our registry.
Strike-through with a reasonRemove a capture and the fact that you did stays visible, with the reason next to it.
Getting a file ready to share: the archive, the report, the capture list or a share link

Report, sharing and storage

What you send on, how you share it, and where your captures stay.

Works with no signalThe device signs every capture straight away. The signing service’s signature and the seal follow when you are back online, and the file records the gap.
The reportA PDF with the photos embedded, the file number, the verification URL and a QR code on the cover.
The archiveEvery photo at full resolution with all the metadata and the timestamp. Complete, and checkable without us for every check but one. The videos sit next to the zip, as files of their own.
The public logA 108-byte fingerprint per file in a public log; every hour in which a file is added is timestamped afterwards, and anyone can verify it.
Customer signature on siteSigned on the phone, inside the file rather than on a separate form. In a checklist with a signature step: Key handover asks for it, and Vehicle handout, Vehicle intake, Completion, Extra work and Equipment rental offer it; on Business also a checklist of your own.
Your logo on the reportOn Plus, Business and Enterprise. The stamp bar you set up yourself in the app; on Business the organisation sets it for everyone.
The dashboard with open orders and their status
The file list in the app, with the orders set out for this person

Business

Orders set out, captures gathered from outside, and everything in your own system.

Backup to your own cloudTo your own storage, not ours. The counterweight to photos that stay on your device.
The dashboardOrders, templates, members and the status of every file. The registry by default; previews and captures only where the organisation asked for them.
Templates of your ownYour checklist, your steps, your fields, versioned. The file records which version was used.
RequestsCaptures from someone without an account: a link and the free app. The same file and the same seal as from your own people.
Webhooks and an APIFiles land in your own system. Search by licence plate or meter reading. With Business by quote and Enterprise.
Captures stay yoursOn your device. Refuse the location permission and the app carries on without one. No cookies on this site.
Storage at EverStampOn Business and Enterprise, once the organisation turns it on: every file kept with us, encrypted, for as long as the subscription runs, with the key held by us for the organisation. Photos at no extra cost; video up to the storage that comes with your plan, above it you pay afterwards.
Organise in the galleryPut files in a project or give them labels, and download a selection as a zip: copies of the originals, with the file and the hash for each capture. Only an overview: each file remains the record.
In detail

The six that make the difference

A smashed window pane close up, with the stamp bar at the bottom of the image: date and time, address, position, file and name

The stamp bar sits in the pixels

Date, time to the second, address and your company name, drawn into the image rather than stored beside it. It is on a printout, a screenshot and a photocopy too, and it stays readable in black and white, because a report often arrives on paper. Nothing to set up: the first capture already carries it.

The time in the bar is the device’s clock; the file carries the timestamped time next to it, and that one is fixed.

An open file with its checklist: the exterior done, the gas reading still missing

Checklists with fields, not just photos

A step asks for a minimum number of photos and for the things a photo cannot show: a licence plate, a meter reading, a serial number, a date, a choice from a list. The app can read the plate or the meter in the viewfinder and propose it; you confirm, and your confirmation is what goes in. Every value travels inside the capture, under the device signature and the seal, so it sits under the same signature as the photo.

The verification page of a file made on an iPhone: it checks out, device Apple, App Attest (Secure Enclave)
iPhoneSecure Enclave, App Attest
The verification page of a file made on Android: it checks out, device Android, hardware attestation (StrongBox)
Androidhardware keystore, Key Attestation

iPhone and Android, the same file

The signing key is created inside the secure hardware of the phone and cannot be exported, on either platform: the Secure Enclave on iPhone, the hardware keystore on Android. Apple attests it through App Attest, Google through hardware key attestation. Every capture carries a sequence number and the fingerprint of the one before it, under that signature.

To the person receiving the file it is the same file, the same report and the same verification page, with the same checks. Two differences remain: who vouches for the key, Apple or Google, and where the counter comes from: on iPhone from App Attest, on Android kept by the app. A team where half the crew is on Android does not end up with two kinds of file.

12 captures in the stamp, capture 3 struckthe reason stays visible

Nothing leaves a file quietly

The number of captures is part of what is stamped, together with every image and their order. Leave a capture out of the archive afterwards, and the check shows it.

While the file is open you can strike a capture through, for example a photo of your own feet. The image goes, but the strike stays visible with your reason, and it still counts. A file that shows its own corrections is worth more than one where something quietly disappeared.

That is also why you share a file as a whole: the report, the archive or a share link. For a single photo from the archive the verification page verifies only its own Content Credentials; only the whole file shows that it was in the sealed series.

The dashboard with open orders and their status
The app’s file list, with the orders prepared for this person

The dashboard, and the API underneath it

A company with five people on the road has a different question from a single user: who is going where, with which checklist, and is it done. The dashboard answers that. You set up orders with an address, a template and a person; they appear on that person’s phone under “Prepared for you”; and you watch the status move from prepared to picked up to registered. Members, roles and your own templates live there too, and you can search across everything your field staff recorded, including licence plates and meter readings.

With Business by quote and Enterprise, the same thing is available as an API with webhooks, so files land in your own system instead of in an inbox. That is the route for an insurer or a lender who wants the files to arrive where the claim already is.

The dashboard opens captures only where an organisation asked for it: for the delivery on a request, and for files kept at EverStamp. For a kept file the gallery shows previews straight away, for recognition: small images the app made when storing, not checked against the file. The original, photo or video, comes only after a click, checked against the file; in the export it fetches everything. A file without previews the gallery opens only after a click. Every opening goes into the audit log, with who and when: a page of previews as one line naming its files, and the originals as one line per file. EverStamp opens them only at the organisation’s written request, or when a court or authority orders or demands it under the law.

A request for photos in the app, with the statement the person confirms

Requests: captures from someone outside your team

An insurer needs photos from the policyholder. An energy supplier needs a meter reading when someone moves house. A valuer needs photos of the property before a desktop valuation. None of those people want an account or a subscription.

So you send a link. They see who is asking and what for, they work through the checklist, and what comes back is a file with the same device signature, the same seal and the same registry entry as one made by your own field worker. They make the captures in the EverStamp app, which they install first if they do not have it yet.

What is fixed. That the captures and their order existed in this form at the time of the stamp, and that a later change shows up. The clock in the bar and the place are statements by the device, and what the captures show is for the other side to judge. How it works, exactly →

Support

A question? You email the people who build EverStamp

About the app, a file, your plan or Business: write to support@everstamp.app, in Dutch or English. Your answer comes from the people who make the app and the registry. The answers to most questions are already on the support page, and in the user guide in the app, under Settings, Help, User guide. With Enterprise you have a named contact, and a service level by agreement.

Go to support Email support@everstamp.app