A surprising spec decision is quietly appearing in serious outdoor security devices: no microphones at all. Not “microphone disabled by default” — no audio input hardware, no live listening, no two-way talk. It deserves a closer look, because it is both a compliance strategy and a product story.
The compliance math
Audio capture law is a patchwork: consent rules differ by jurisdiction, and two-way audio turns a camera into a communication device with a different regulatory weight. Removing the microphone collapses an entire compliance chapter — there is nothing to consent to, nothing to encrypt differently, nothing to redact in exports.
The privacy story strengthens
“Video only” is a line buyers instantly understand. It also disciplines the firmware team: no audio analytics, no ambient recording, no voice uplink — the absence is verifiable in the bill of materials, not just in a settings menu. For shared and multi-tenant properties, this is the difference between an acceptable device and a negotiation.
Deterrence does not need microphones
The deterrence loop — siren plus voice warnings from a stored clip library — is one-way audio output. It needs a speaker, not a microphone. Everything a security device does to an intruder works without listening to anyone.
What you give up, honestly
Two-way talk for doorbell-style products, and audio analytics like glass-break detection. For a perimeter device whose job is to see, classify and alert, that trade is cheap. If a future product needs audio, it is a new hardware revision — which is exactly why the decision should be made deliberately at the start.