VeriVox / Security
Security & sovereignty
We cannot lose
what we never hold.
Most vendors secure your data. VeriVox is architected to never have it. That single decision collapses the threat model: there is no server-side breach because there is no server side.
The posture
Properties, not promises.
Each of these is a fact of the architecture — verifiable on your own network monitor.
Zero egress
The evidence stays
Full pipeline — enhancement, STT, diarization, embeddings — executes locally. Airplane mode is a supported configuration.
Zero retention
No copies exist
No cloud cache, no “improve our models” clause, no support-access backdoor. Your files, your disk, your custody.
Zero telemetry
No phoning home
No analytics beacons, no crash reports carrying fragments of privileged audio. Silence, by construction.
Integrity
Chain of custody, cryptographically anchored.
SHA-256 at ingest; every derived artifact references the source hash; every enhancement recorded as a reproducible command. The question “was this altered?” has a mathematical answer.
The bridge (optional)
Shared infrastructure without shared data.
Teams that want centralized job routing can deploy the VeriVox bridge: it authenticates and routes — and never stores. Payloads traverse encrypted, terminate at the operator's machine, and leave nothing behind. The bridge is auditable; sovereignty survives scale.
Early access
Read the architecture,
then test it with the network cable out.
Security documentation available to pilot participants.
Request early access