Technology#wearables#data-resale#privacy#gdpr#ftc

Wearable Data Resale: What the Policy Doesn't Say

Privacy Watchdog SamPrivacy Watchdog Sam||5 min read
Wearable Data Resale: What the Policy Doesn't Say
TL;DR

Your wearable's privacy policy is a pipeline map written by the people who profit from you not reading it — so read clause eleven, kill research sharing and partner access before the first sync, and treat a vendor's silence on law-enforcement requests as an answer.

Why does a sleep ring need an account, a cloud sync, and a partner list? The device works fine offline. The less honest answer lives in the terms-of-service update, framed as research collaboration. Start with the threat model, not the feature list. What leaves the device, where does it land, and who can query it a year from now?

The pitch: what they say it does

The marketing copy is modest enough. A band counts steps, a ring reads temperature, a watch reports heart rate variability overnight. The vendor promises insight, not surveillance. Fitbit's statement when Google announced the acquisition was that the company never sells personal information and that health and wellness data would not feed Google ads. That is a narrow promise, carefully worded. It says nothing about Google health projects, and a spokesperson confirmed Fitbit would come under Google's privacy policy. Under GDPR, fitness data is treated as integral to service provision, so both Fitbit and Google can process it — with consent already baked into the framework you clicked through. Consent is not control. The pitch describes a product. The paperwork describes a pipeline.

What they collect: often more than the feature needs

Continuous heart rate is a biometric. A step trace over weeks reveals your home, your workplace, and roughly when you sleep. Add GPS and the picture sharpens. Add a partner integration and it leaves the building. The EFF's review of ten major wearable makers found most lack basic transparency reports and key privacy features, including end-to-end encryption — meaning the company itself can read the health data it holds. Two questions follow. Does the vendor share data with law enforcement and governments? Can it decrypt your records at all? If the second answer is yes, the first becomes a policy choice rather than a technical impossibility. That distinction matters more than any badge on the box.

What they don't tell you: resale and model training

Resale rarely appears under that word. Look for "aggregated insights," "research partners," "anonymized datasets," and "service improvement." Each is a door. The FTC's Health Breach Notification Rule covers apps and connected devices that draw health information from multiple sources — a fitness tracker syncing through an API qualifies — so unauthorized disclosure can carry notification duties. That is a floor, not a ceiling. GDPR gives you portability and a lawful basis to challenge, but only if you ask. The privacy policy is the only document that tells you which door your data walks through, and it is written by the party that benefits from you not reading it. Read it anyway. Clause eleven is where the interesting sentences live.

Your move: what to do about it

Open the app's privacy settings before your first sync. Turn off research sharing and third-party partner access if the device still works without them — most do. Check whether end-to-end encryption is offered; if it is, enable it. Export your data once and see what the file actually contains; that is your portability right under GDPR, and it is a useful audit. If the vendor publishes a transparency report, read the law-enforcement section. If it does not, treat that silence as a data point. And when a free band arrives with a subscription attached, remember the economics: free at point of sale rarely is. Take the opt-out on day one.

FAQ

Isn't "anonymized" good enough?

Rarely. Step traces, sleep windows, and heart-rate patterns are unusually good at re-identifying people, and "anonymized" in a policy usually means pseudonymized with a key the vendor keeps. Ask what the dataset is joined against, not just what was stripped out.

Can I just delete my account and be done?

Deletion requests cover what the vendor still holds under your identity, not what already moved to a research partner or an aggregate. Export first, then delete, then re-check in thirty days — some policies give themselves a window to purge backups.

Does GDPR actually help me if I'm in the US?

Only if the vendor sells into the EU, but many do, and the portability right travels with the service. For US readers, the FTC rule is the lever: it obliges notification when health data is disclosed without authorization. Either way, the request you file is the same.

Start in MORLD

Do the one thing this column keeps repeating: open the privacy settings before your first sync and turn off research sharing and partner access. Then export your data once and read the file — that is the audit nobody will run for you. If you find a clause worth flagging, compare notes with other readers in the Morld community.

Related Articles