For your IT team
Built to be easy to say yes to.
Delivery Book was designed from the first migration to pass an IT review, not to survive one.
Data stays in Canada
All data resides in Canada, in AWS Canada Central, on a dedicated and isolated database instance provisioned for this application alone. It is the only environment the vendor operates: one project, one region, in Canada.
The application holds the minimum
A delivery board needs to know which vehicle belongs to which customer and who owns each step. It does not need to be able to contact the customer. So the application holds no customer contact information of any kind, no documents or files, no payment data, and no financing terms. Customer communication stays in the dealership's CRM, where the contact record already lives.
Access control lives in the database
Row-level security on every table, role-based views resolved server-side, and column-level write ownership enforced by the database itself. A detailing user cannot write to a field owned by the F&I office, and that holds no matter how a request is written. Permission changes are proven by tests that attempt the forbidden action with real restricted credentials and confirm the database refuses it.
An audit trail that survives everything
Every change to a delivery record is logged with the acting user and a server-generated timestamp, in an append-only log no application role can modify or delete. Deleting a record does not erase its history.
Discipline in the build
More than four hundred automated tests run before every release. Every schema change is a numbered migration with a tested rollback. Test data is synthetic, with an automated check that fails the build if real customer identifiers are detected.
The full picture, on request
A complete Security and Privacy Overview, including current state and roadmap stated plainly, is available to your IT team on request. Written questions get written answers.