Ten controls, and when each one is decided.
Most of these are design decisions, which is why they are cheap to honour and expensive to retrofit. One of them, the human approval points, cannot be removed later, by us or by you.
Data minimisation
Fields a step does not need are removed before anything leaves your systems. An answer about delivery gets an order status, not a customer history.
Design stageNamed providers
Every model, hosting, telephony and verification provider is named in writing before build, with its processing region and retention policy.
Before buildNo training on your data
Providers are configured, where the provider supports it, so submitted data is not used to train their models. Where a provider cannot guarantee it, it is not used.
ContractualJurisdiction constraints
If your policy prohibits data leaving a region, that is a design input that changes which providers are eligible, not a launch-week discovery.
Design stageHuman approval points
Customer-facing output held by default, low-confidence work escalated to a named person, destructive and financial actions always behind a human step.
Not removableAudit record
Every system action, escalation, approval and override is written with who, when and what changed.
Per actionAccess control
Role-based access in the operator interface, credentials held in your accounts, and a transfer of admin rights at handover.
Your accountsRetention schedule
Stated in one sentence per system, verified against the provider settings rather than assumed.
Written downIncident route
A named contact, a defined response window and a written record. Nexvix reports rather than waits to be asked.
One business dayExit
The system runs without a Nexvix retainer. Support is optional and priced separately.
No lock-in