Data Security

Separation is enforced in the database on every table, so a request for someone else's project returns nothing even if the address is guessed. It does not rely on the interface hiding a button.

Roles are enforced on the server too. A field technician cannot run a review or build a package by calling the underlying endpoint directly.

Estimates, reports, photographs and finished packages live in private storage. They are reachable only through short-lived links issued to a signed-in member of the owning company.

Finished packages are stored privately too; downloading one always goes through a fresh, expiring link.

Extracted estimate values are protected once read. Your corrections are stored alongside them so the original reading stays provable.

Photographs are evidence. The uploaded file is never edited, retouched or replaced. Markup is a separate layer, and an annotated copy is a separate image that is clearly labelled in reports.

Completed analyses are versioned and immutable, so an earlier review can always be shown as it stood.

Uploads, analyses, finding decisions, markup changes, package finalisation and downloads are recorded with the person and the time.

Files uploaded without an account are stored privately, used for that one result, and deleted automatically within 7 days.