Consent and Voice Assistants: Choices for Always Listening Devices
A smart speaker is a microphone that lives in a shared room. The person who set it up agreed to terms on a phone screen, but partners, children, guests, and cleaners all speak within its range, and most voice platforms record and review more audio than their owners realise.
This guide covers how consent should work for voice assistants: what setup can and cannot cover, how guests and children change the picture, what retention and human review mean for the consent story, and how deletion needs to work when the device has no screen.
Setup consent covers one person, not the room
The account holder accepts terms during setup, usually quickly and on a small screen. That acceptance can cover their own voice data, but it says nothing about everyone else the device hears. Platforms handle this gap badly when they treat the home as a single consenting unit. A more honest model treats the account holder choice as covering account features, and applies the most limited processing to voices the system cannot match to the account. If your platform offers a guest mode or voice match, the consent design should push people toward it rather than burying it.
Wake words, false triggers, and accidental recordings
Voice assistants wake on mistakes: similar sounding words, television audio, and conversations near the device. Those accidental clips are recordings of people who never intended to interact at all, and they are the hardest to justify keeping. Retention for unmatched and accidental audio should be short by default, with automatic deletion that does not depend on the owner auditing a history page. If human review of clips is part of quality work, that fact belongs in the setup flow in plain language, with an opt out that does not disable the device core functions.
Children change the default
Homes with children are the norm for these devices, and children cannot consent to voice profiling. Kids profiles should exclude advertising use and human review entirely, and voice data from unrecognised young voices should get the shortest retention the platform offers. Setup flows that ask whether children live in the home, and set defaults accordingly, do more real work than a paragraph in a policy. Schools and nurseries using voice devices face an even stricter version of the same problem and should treat the account holder consent as covering almost nothing beyond basic operation.
Deletion without a screen
Deleting voice history is usually possible in an app and nearly impossible from the device itself, which is backwards for a product whose whole interface is voice. A spoken delete command for recent recordings, a clear spoken answer about what was removed, and an app history that lists recordings with their purpose and age are the minimum usable set. Deletion should propagate to backups on the same rotation rules as other consent records, and a factory reset or resale should wipe local and cloud history as one action, not two separate hunts.
Related reading
These earlier guides cover connected questions in more depth: How Long to Keep Consent Records: A Practical Retention Schedule, Consent in Mobile Apps: Getting SDK Signals Right, and Consent Audit Trails: Exporting Records a Regulator Can Actually Read.
Frequently asked questions
Does buying a smart speaker mean my guests consented?
No. Guests never saw the terms. That is why guest and unmatched voice data should get limited processing and short retention by default, rather than being treated as covered by the owner choice.
Can I stop my voice clips being reviewed by humans?
Most major platforms offer an opt out in privacy settings, though it is rarely shown during setup. Look for a setting about improving services or voice history review, and turn off both storage and review if you want neither.
What happens to recordings when I sell or give away the device?
A factory reset should remove the device from your account and trigger deletion of its cloud history. Check the app afterward to confirm the device and its recordings are gone, because reset behaviour varies by platform.
Should voice assistants ask again over time?
Ask again when data use changes materially, such as a new review program or advertising use, not on a fixed nagging schedule. A change driven prompt gives owners a real reason to reconsider.