Editorial Note: This story explores the distance between recording and nudging. The same stream of body data can feel like a private record to the person wearing the device and become a retention signal inside the company operating it. We tell the story through a changelog, a push notification, and a customer-support email because these tensions often emerge through ordinary product decisions rather than explicit arguments. The people, companies, products, and events are fictional. The scenarios draw on documented patterns in the wearable technology and consumer health-data industries, combined and adapted for narrative purposes. They do not describe any actual company or individual. The health-related scenes are fictional illustrations, not medical guidance or a substitute for professional advice.
The Wearable That Couldn't Show Ads
Who Owns the Health Data Your Wearable Collects: A Business With No Ad Slots
Phones show you ads. Laptops do, tablets do, even smart TVs do. They have feeds, splash screens, little corners built for a tap. A screenless band has none of that. At best it has a display an inch across; often it has nothing but a status light that changes color. You wear it. It doesn't talk, and it doesn't pitch.
So what keeps it alive?
The answer isn't only in the hardware. For subscription-led screenless bands, the initial device sale is just the beginning of the business relationship. The recurring revenue comes from the billing date: one subscription charge a year, renewed, buying another year of access to the service. The longer-term value lies in continuous tracking, personalized insights, and a relationship designed to keep users engaged. The device is the entry point. The ongoing service is what the company needs to sustain.
From the wearer's side, it feels like something else entirely. Someone who straps on a band believes they're doing a private thing: logging how they slept, how fast they ran, whether their heart skipped. What they don't know is that the same gesture has a different name on the other end. When you tighten the strap at night, the system logs active wear. When you open the app in the morning to check your score, it logs daily active user. When you wear it forty days straight, it logs a retention curve bending upward.
Both sides are recording. They aren't recording the same thing.
David O'Connor knows none of this. He knows he tossed and turned, and his score came out ugly. He's thirty-nine, a project manager in Chicago, the kind of person who puts anything measurable into a spreadsheet. He nudges the strap one notch tighter, lies back, and waits for the band to start working.
Snow is still falling outside. He has no idea that the small motion he just made is being counted, in a conference room two thousand miles away, as a successful retention event.
What a Fitness Tracker Subscription Actually Buys: The Honeymoon Phase and "Active Wear"
For the first two weeks, the first thing David does every morning is check his scores.
Sleep score, recovery score, stress load. Three numbers and a summary line. He screenshots them and sends them to himself like a status report. In week one he hit 91 and carried that around all day; he walked up twenty-three flights of stairs instead of taking the elevator. In week two he got a 64 and canceled dinner plans, citing the data. He thinks the thing is fair. It doesn't flatter him and it doesn't scold him. It just hands over numbers.
Naomi Alvarado uses hers harder. She's twenty-eight, teaches middle school, and has tripled her mileage in a year. She's the one in her running group who argues about pace. She stopped training by feel months ago. In the morning she checks her readiness score: green means hard day, yellow means easy, red means rest. One week she got three reds in a row and pushed her plan back, and felt relieved, which surprised her. She used to be unable to take a rest day without guilt. Now she had external permission. A training partner told her she'd been domesticated. She said fine, as long as domesticated makes me faster.
She signed up for the spring half marathon and talked David into entering too. He needed someone to hold him to it.
Ed Whitlock got his band installed by his daughter. He's sixty-one, a retired teacher, bad knee, slow walker. Karen bought the band, set it up, and enrolled him in a wellness program: wear it, hit the weekly targets, get a break on his insurance. Ed has no interest in numbers. What he likes is the weekly phone call, where Karen asks how he slept. So he checks in every morning, seriously. He thinks he's cooperating with his daughter. He doesn't think of it as cooperating with a machine.
Three weeks in, Hannah Vogel, Meridian's product director, is looking at a curve.
It's a good curve. Thirty-day active-wear rates for new users are up from the last generation, and subscription conversion is moving the right way. Her team has a feature ready for beta: overnight heart-rate anomaly alerts. Somebody raises false positives. Somebody else raises scared users. Hannah takes a moment, then says that if the thing gets one person to a doctor earlier, they've done the right thing. She signs off.
Dana Okoye, a data scientist on the team, says almost nothing in that meeting. She has a deck that hasn't been presented yet, with a comparison in it: users who received an anomaly alert retain noticeably better the following month. She saves it to a personal folder with an unremarkable filename.
That night David gets an update notice. He skims it and notices one new line.
Meridian update v4.1
- Added: overnight heart-rate anomaly alerts (beta)
- Improved alert timing to reduce unnecessary interruptions
- Fixed missing fields in exported data
Out of pure project-manager reflex, David taps "export all data." The file arrives quickly. He scrolls to the middle and finds a gap: four consecutive months where the dates are there and the values are blank. He figures it's a sync glitch, doesn't think about it again, and drops the file in his downloads folder.
Why Sleep Scores Are Making People Anxious
A few weeks later, Dana brings that deck into a review.
The numbers are clean. Users who got an anomaly alert retain better the next month, and the effect is strongest for two categories: sleep below personal baseline, and overnight heart-rate anomalies. Someone offers the obvious reading: the alerts work, so people take their health more seriously. Dana offers a second reading: maybe people who get scared are the ones who don't dare stop. The room goes quiet for a few seconds. Hannah asks her to run the copy as an experiment.
The next release changes the wording. What used to read "your sleep was below your personal baseline" now reads "your body hasn't recovered yet, consider lowering today's intensity." Push timing moves from a fixed 7:00 a.m. to eight minutes after the band detects that you're awake. Thirty days of continuous wear earns a badge, and badges are shareable.
David's change starts in bed. He used to fall asleep when he was tired. Now he catches himself wondering whether tonight will produce an 80. One night he gets a 71 and stays flat on his back for forty extra minutes the next morning, barely moving, to make the curve look better. He pushes his half-marathon training plan back twice, citing recovery. He messages his doctor and asks whether he might have a sleep disorder. The reply is one line: Are you spending too much time on that number? He doesn't answer. He puts the phone face-down, then picks it back up and opens the app to look at last night's respiratory rate.
Naomi's change is quieter. On a red rest day she really wants to run, so she leaves the band on the dresser and goes out for five miles. She feels great afterward. When she puts the band back on, the app tells her the day's data is incomplete and lowers her recovery score. She stares at that line for a long time, and it occurs to her for the first time that she's being docked points rather than looked after. She learns two sets of habits: no band when she wants to run, band strapped tight when she wants credit. Two weeks before the race her readiness goes yellow four days running. She dials down her intensity, curses under her breath, then can't decide who the curse is aimed at. She tells no one she's cheating, including herself.
Ed learns a different performance. He takes longer walks to make the step count respectable. He checks in on time so the phone call with his daughter goes smoothly. On nights when he can't be bothered, he leaves the band on the arm of his recliner so the green light keeps blinking. He thinks that counts. He doesn't know that the arm of that recliner is recording more than he does.
Around the same time, Dana's experiment report grows another page. The anxious-cohort retention result replicates a third time, and it goes into the quarterly deck under a new title: high-value alert strategy. Hannah leaves one line of comment beneath it: keep the thresholds, keep iterating on copy. On the drive home she thinks about what Dana said in that meeting for maybe ten minutes, then goes back to answering email.
What to Do After a Wearable Heart Rhythm Alert: A Gray-Area Warning
At three in the morning, the band on Ed's wrist lights up once.
It has detected an irregular pulse pattern lasting a little over forty seconds. A threshold is crossed. An alert goes out. Karen's phone rings before Ed's, because she has remote viewing access. She calls three times; he picks up on the third. He says he was asleep, she should relax. She says he's going to a doctor tomorrow.
The next morning the doctor reviews the notification and its accompanying pulse data, runs an ECG and a couple of other checks, and delivers the news quickly. It looks like a benign skipped beat; age and caffeine may both play a role. Watch it, cut back on evening coffee, come back for a follow-up. Don't panic. Ed asks whether the band is accurate. The doctor says it can flag an irregular pattern, it can't diagnose a heart condition. Without the band, you might never have noticed that beat. If all you do is watch the band, it could scare you for years.
Ed buys a coffee on the way home and finishes it standing outside the shop. He doesn't tell his daughter.
The same pulse record takes a second path through Meridian's backend. It gets auto-tagged as a potentially useful sample, enters a labeling queue, and a few days later is matched against preliminary eligibility criteria for a research study. No study enrollment has taken place yet. Karen gets an email saying her father's data may qualify for a partnered longitudinal study on sleep and heart rhythm, and asking whether he'd be interested in participating.
Push notification · Meridian An irregular heart rhythm was detected overnight. This is not a diagnosis. Consider talking to a doctor.
Email · Meridian Research Your recent data appears to meet preliminary criteria for a longitudinal study on sleep and heart rhythm. Participation helps improve algorithm accuracy. You can withdraw and delete the associated data at any time.
That same week, a different email arrives from a different company. Ed's wellness program sits inside his Orbit account, and the program administrator wants three months of activity and sleep records for an annual eligibility review. The wording is polite. Somewhere in it, the phrase related services appears. Ed doesn't know what that means, so he forwards both emails to Karen.
Karen says it's a good sign, it means the thing works. Ed says fine, it works, so whose is it now? Karen doesn't have an answer.
That evening he wipes down the arm of the recliner and leaves the band on his wrist. He wants to see how much it actually notices.
How to Export Your Wearable Health Data (and Why Some Months Come Back Blank)
David's formal export request starts with his doctor wanting a longer view.
The doctor asks whether his sleep has changed much over the past few years. David says he has the data. The doctor says send it over. David opens the app and finds only a ninety-day chart, averaged by day. He remembers the file he ignored in his downloads folder, requests an export again, and gets another CSV: dates, sleep duration, scores. No raw waveform, no overnight heart-rate trace. He writes to support and asks for the full raw data.
The reply is courteous. Raw waveform data is available for the period covered by an active subscription. His account had a four-month lapse. That stretch is marked retained but not readable. In the export, those rows are blank, exactly the gap he saw weeks earlier. He asks whether he can pay to reopen those four months. Support says no, subscription periods aren't retroactive. He asks about the data from the brand he used three years ago, before Meridian. Support says that data isn't in Meridian's systems; he'd need to contact the original manufacturer. The original manufacturer writes back: export is possible, there's a one-time data processing fee, the format is proprietary, and a documentation file is included.
Why Some Months Can't Be Exported
He puts his hope in the phone ecosystem instead. His watch data syncs to his Orbit account, so maybe there's a backup there. Orbit sends a template message: health data isn't used for advertising, and is used to improve the product experience and related services within the account. He reads it three times and still can't tell what "related services" covers.
Inside Orbit, none of this has happened yet. Derek Nunez, who runs monetization, is pushing a proposal: route health signals into wellness-program eligibility checks and into personalized recommendations inside the account. Compliance sends one short email asking whether users actually understand the boundary of "improving the experience." Derek replies that it's spelled out in the privacy policy. The thread goes nowhere after that.
Trading Health Data for Insurance Discounts
That week, three requests move through three entry points in the same machinery, and they point at the same question.
David wants to take back: three years of raw records, including the four blank months.
Ed is being asked to hand over: three months of activity and sleep data, to a program administrator he has never met, in exchange for a discount that only exists as long as the data keeps flowing.
Naomi wants to delete: she turns off cloud sync, removes the two runs she did without the band, and then discovers the system still knows she wasn't wearing it that day. The absence is data too.
On race day David finishes the half marathon in 2:14:00. Naomi beats him by nineteen minutes. Afterward he sits on the curb and, for the first time, doesn't immediately check his recovery score. When he gets home the app gives that night's sleep a 68, with a note: elevated training load, consider an early night. He looks at it for a few seconds, then puts the phone face-down on the table.
David eventually gets a file. He opens it, sees the four blank months, and it looks like film cut out with scissors. He screenshots it and sends it to his doctor. The doctor says, then let's start recording from today. It hits David that the way he has been recorded for three years was partly his decision, and partly the billing date's.
What People Keep After Turning Off Every Notification
Naomi moves first.
She turns off every notification and keeps only the weekly summary. She doesn't cancel the subscription; the charge keeps landing. She runs five miles with no band, no log, no score. Afterward she stands in her doorway for a while, legs burning, mind oddly empty, then goes in and showers. She tells herself this isn't giving up. It's negotiating.
Ed withdraws from the wellness program. He takes the band out of the drawer, looks at it for a long time, puts it back, and locks the drawer. Karen calls and is sharp with him: does he know how much that discount was worth? He says he knows. He says he doesn't want a thing living his life for him, and he doesn't want it worrying on his behalf. They sit in silence for about half a minute and hang up separately. After that, Karen still calls once a week. She asks about his sleep. She doesn't ask about the data.
David switches brands. On the day the new band arrives, he puts the old one in a drawer with the CSV beside it. He opens the new app, gets asked for two dozen permissions, reads every one, and taps allow. He knows he'll still check scores, and he knows he'll still lie in bed to protect one. He just probably won't go digging through those four blank months again.
At Meridian, one strategy gets retired. The overnight heart-rate threshold is set more conservatively, and the feature now requires opt-in. In the quarterly deck, the north-star metric changes from active wear time to user-initiated healthy behavior. Hannah writes a retrospective with the same enthusiasm as the old changelog. It opens with: we gave the choice back to our users. At the end of the meeting Dana asks whether the anxious-cohort data is still being kept. Hannah says yes, for research, in de-identified form.
Near the end of that spring, David forgets to charge the band. Its status light fades before dawn, and the room goes fully black with it. He lies there for a while and falls asleep without looking at a single number.
It was the first night in years he slept without checking a score. Before its battery ran out, the band had already logged eleven turns in the dark.
Continue Exploring
References
-
U.S. Food and Drug Administration. (2018). De Novo Classification Request for Apple Inc. Irregular Rhythm Notification Feature.
https://www.accessdata.fda.gov/cdrh_docs/reviews/DEN180042.pdf -
Federal Trade Commission. (2023). Collecting, Using, or Sharing Consumer Health Information? Look to HIPAA, the FTC Act, and the Health Breach Notification Rule.
https://www.ftc.gov/business-guidance/resources/collecting-using-or-sharing-consumer-health-information-look-hipaa-ftc-act-health-breach -
U.S. Department of Health and Human Services. HIPAA Privacy and Security and Workplace Wellness Programs.
https://www.hhs.gov/hipaa/for-professionals/privacy/workplace-wellness/index.html