Why local
Their privacy is a policy.
Ours is an architecture.
A cloud vendor promises not to misuse your data. That promise survives exactly as long as their management, their finances, their jurisdiction, and their security do. VaultScaler's systems have no uplink, no vendor account, no server, and no remote access — including for VaultScaler.
This describes the systems VaultScaler builds where an Exposure Assessment finds one is needed — they follow an assessment, they don't lead it. The architecture holds regardless of what prompted the build.
The checkable consequences
There is nothing to breach, subpoena, or browse.
No copy of what your system sees exists anywhere else. There's no second location for a court order to name, no vendor database for an attacker to reach, no backup on infrastructure you've never seen.
If someone wants what your system saw, they come to you.
Not to a vendor, not to a data center in another country. There is one copy, and it is in your building, under your control.
Support happens in person, because there is no other way in.
There's no remote-access account for VaultScaler to sign into, no support tunnel, no admin backdoor. A change to your system means someone is physically there to make it.
For Europe, specifically
This is a compliance argument, not a values one.
No third-party processor sits in the chain. No personal data crosses a border. No retention terms are written by a vendor. Biometric processing can be demonstrated, room by room, to be either enabled by the owner's choice or absent entirely.
That is a materially easier position under GDPR than any cloud-based system — and it is the same product. Only the register changes.
Ask us what a vendor can't answer.
Where your data actually goes today, and what it would take to keep it home.