Consent and Voice Assistants: When a Spoken Yes Is the Record
The television used to be the one screen that did not watch back. Now a smart TV can recognise what is on screen, a scene, a channel, a game, a home video played from a laptop, and report viewing habits to the manufacturer and its data partners. The agreement for this was technically obtained, during setup, in a hurry, probably by whoever plugged the TV in.
Streaming apps add their own collection on top: watch history, searches, device details, and advertising identifiers shared under each app's terms. This guide separates the two layers, the television and the apps, and gives the settings that return some privacy to the living room.
Wearable consent given at setup covers the device working as described then. Continuous health and location collection, sharing with apps and insurers, and research use each need clear information and, for optional sharing, a separate genuine choice.
Voice consent is fragile because a spoken yes leaves no visible record, can come from anyone in the room, and covers services the speaker barely described. Households should review voice history and purchase settings, and makers should confirm important choices in a companion app.
Consent without a screen
A screen based flow can show categories, link to detail, and log exactly what was displayed. A voice flow compresses all of that into a short spoken prompt and a yes or no. The person answering may be a guest, a child, or someone in the next room, and the device cannot always tell voices apart, especially in a noisy kitchen.
Purchases, subscriptions, and skill permissions get granted this way. The confirmation may be the first the account holder hears of it, days later on a statement. That delay is the core design problem: consent that the responsible person never saw, given through a channel that keeps no copy they can review at the time.
The household checks that matter
Turn on voice purchasing controls and a confirmation code if the device offers them, and review the voice history in the companion app monthly. That history is the closest thing to a consent record the household gets, and deleting it is a separate choice from switching off future recording, two settings people often confuse.
Guest use deserves a deliberate decision. A speaker in a rental or a shared flat records visitors who never agreed to anything. Muting the microphone during gatherings, placing devices out of bedrooms, and using guest modes where they exist are simple steps that respect people who never bought the product and cannot opt out of someone else's.
What better voice consent looks like
Makers should route anything significant through the app: purchases above a small amount, new data uses, and permissions for third party skills. The spoken prompt can start the process, but the record should land somewhere the account holder can read, search, and revoke without unplugging the device in frustration.
Revocation needs a voice route too. If a yes can be spoken, a no should be just as easy to say later, with the device confirming what changed. Consent that can only be withdrawn through five app menus was never really balanced, and regulators reading the flow will notice the asymmetry quickly.
Keep reading: Consent for Wearables: Health Data Collected on the Wrist, Shared Everywhere, Auditing Consent Banners for Dark Patterns: A Practical Checklist, and Consent on Smart TVs and Streaming Apps: Viewing Data Nobody Agreed To Share cover the nearby cases in this series.
Frequently asked questions
Who consents when a guest talks to my smart speaker?
In practice, nobody meaningfully does. The device responds to any voice it accepts, which is why owners should treat guest exposure as their responsibility: use mute and guest settings, and avoid placing always listening devices where visitors have no real choice about being recorded.
Can a child agree to purchases by voice?
Devices have repeatedly allowed it when voice purchasing was left on without a code, which is why platforms added confirmation settings after complaints. Turn on the code and child profiles where available, and do not rely on the device recognising a young voice.
Where can I see what consent my device holds?
In the companion app: voice history, enabled skills and their permissions, purchase settings, and recording retention choices. Reviewing that list is the household equivalent of a consent dashboard, and revoking a skill there ends its access.
Does deleting voice recordings withdraw consent?
No. Deletion removes stored recordings, while consent and skill permissions are separate settings that continue until changed. Do both if that is your intent: delete the history and switch off the permissions and retention options behind it.