Platform
Where the data lives, and who can reach it
A shop handing over its estimates is handing over its commercial position. This page says what happens to it.
Your estimates are yours
A customer shop’s estimates are not published, sold, or used as examples. The cases published on this site are the operating shop’s own repair orders, never a customer account’s work.
Separation between shops
Vehicle history autofill is scoped to the shop that owns the history. A shop signing up does not receive a search box over another shop’s customers, and the account boundary is enforced in the database rather than in the interface.
Least privilege on the database
The application role has no access to the shop management database beyond a single read-only grant on one vehicle table, and no access at all to customer records. That is enforced by role grants, so an application bug cannot widen it.
Transport and hosting
Served over TLS on infrastructure operated directly rather than resold. Accounts are created by hand today, which is a deliberate consequence of running a private pilot rather than an open signup.
Before you ask
Do you train models on my data?
No.
Can another shop see my vehicles?
No. History lookup is scoped to the owning shop and enforced at the data layer.
Who has access internally?
The operator of the service. There is no support organisation with standing access to shop data.
Run it on damage you have already written
Accounts are created by hand, usually within a business day. Bring your own photographs and a repair order you have already closed, so you can see how close it lands before you decide. No card, no trial timer.