Terms of engagement

Our binding terms are set out in the master services agreement attached to each engagement. This page summarises the principles that the MSA always contains — designed so the buyer's procurement and legal teams know what to expect before they sign.

Discovery outputs are portable.

The design document produced in a Discovery engagement is yours. You can take it to any implementation vendor. We do not bind you to a follow-on engagement to receive it.

SLAs are written, measured, and enforced.

Per-module accuracy SLAs sit in the maintenance contract from day one, with measurement methodology, reporting cadence, and service-credit triggers. We will not deploy a module under a maintenance contract without an SLA on it.

Hardware is yours, purchased directly.

We specify the hardware; you procure it. We do not invoice mark-up on hardware. The client owns every piece of hardware deployed at their site.

Data sovereignty is the default.

Video and biometric data does not leave the client's network unless explicitly contracted otherwise. Cross-border transfer requires written, project-specific authorisation.

Exit clauses are clean.

Maintenance contracts include a documented handover process — model files, configuration, runbooks — so the client can take operations in-house or to another vendor without re-engineering work.

This page summarises the contractual principles only. It is not the contract itself. The binding terms are in the MSA attached to each engagement.