A connected device rarely works alone. The scale, the speaker, the doorbell all lean on a phone app for setup, and that app becomes the real product: the account, the data store, the sharing hub. Consent, if it happens at all, happens there.
It often happens badly. Setup flows are designed to get the device working in five delighted minutes, and consent is treated as friction in that race. The result is devices collecting from the moment they power on, governed by a single agree tap nobody remembers making.
The device starts before the consent
Many devices begin collecting the moment they join a network: usage signals, diagnostics, sometimes audio or video depending on the product. Setup consent that arrives after pairing is consent for a collection that already began.
Better flows stage it: minimal operation until the account exists, then clear choices before the richer features switch on. Where pre account collection is technically necessary, it should be limited, disclosed in plain words, and deletable when the account is created.
One agreement, many different data uses
A companion app commonly handles very different kinds of data under one roof: account details, device telemetry, location, health or home data, and recordings. One blanket permission for all of it fails both users and, in stricter jurisdictions, the legal standard for consent itself.
Granular choices by purpose are the fix, presented when each feature is first used rather than as a wall of toggles at setup. Just in time consent, at the moment a feature needs the data, is both clearer and easier to make honestly optional.
Sharing is a separate decision
Companion apps love integrations: share with a fitness platform, a voice assistant, a household member, an insurer's wellness program. Each share sends data to a new party and deserves its own explicit choice, with the recipient named.
Household sharing needs special care. The account holder consenting does not cover the partner, guest, or child whose voice, image, or habits the device records. Products that ignore bystander consent are building a complaint they have not met yet.
Withdrawal must reach the device
A consent setting that only changes the app's screens is theater. Withdrawing a permission should stop the collection at the device, end the sharing flows, and start the deletion process for stored data, with the app confirming each of those in words.
Test withdrawal like a feature, because it is one. Toggle a permission off and verify, in the product's behavior and in your own account data view, that the world actually changed.
Related reading
These earlier guides go deeper on connected questions: Consent and Email Preference Centers: Giving Subscribers Control Without Losing Them A preference center turns an unsubscribe into a choice. Designing consent options subscribers actually use, and honoring them everywhere the data travels., Dark Patterns in Subscription Checkout: Consent That Is Not Really Consent Pre-ticked add ons, hidden skip links, and roach motel cancellations turn subscription consent into a trap. Naming the patterns is the first step to removing them., and Consent for Subscription Boxes: Tracking That Renews Every Month Subscription boxes renew, swap products, and add partners over time. Consent collected at signup has to survive a relationship that keeps changing..
Frequently asked questions
When should a companion app ask for consent?
At account creation for the basics, and again at the moment each additional data use is first switched on, such as location, health syncing, or a third party integration. Just in time requests are clearer and more likely to be genuinely informed.
Does the person who owns the account consent for the whole household?
No. Other people recorded or tracked by the device, partners, children, guests, have their own interests and, in many places, their own rights. Good products provide household controls and guest modes instead of treating one account as universal permission.
What data do devices collect before setup finishes?
It varies, but commonly diagnostics, network and usage signals, and whatever the device's sensors gather while active. Responsible products limit pre account collection to what setup technically needs and say so plainly.
What should withdrawing consent in the app actually do?
Stop that collection at the device, end related sharing, and begin deletion of the stored data covered by the withdrawal, then confirm it in the app. If only the interface changes, the withdrawal is cosmetic and the practice is risky.