- Stories
- Sci-Fi
- What the Algorithm Knows
- Opt Out
Opt Out
Maya stared at the single sentence on the screen, the cursor blinking like a metronome that kept time for a piece she hadn’t yet composed. The document’s title, “Personal Ethics,” felt too formal for the rawness of the thought it contained. She saved it, closed the window, and opened the next tab—a portal the insurer called “Data Subject Rights.” The interface was a sleek cascade of teal buttons, each promising a different shade of control: “Access,” “Rectify,” “Erase,” and finally, “Opt-Out.”
She clicked the last one and a form expanded, asking for a reason, a signature, a timestamp. The reason field offered a dropdown of boilerplate options: “Privacy concerns,” “Incorrect data,” “No longer a customer.” None of those captured the nuance of a system that had already seen her heart before she could. She typed instead: “I no longer consent to my data being used for predictive modeling.” The words felt too blunt, but the system didn’t care about literary flourish.
Behind the form, a diagram showed the data pipeline in simplified form: ingestion from claims, preprocessing, feature extraction, model training, inference, feedback loop. Each stage was a black box, but Maya could see the labels: “Feature Store,” “Model Registry,” “Risk Engine.” She hovered over the feature store node and a tooltip appeared, listing the attributes the model used for her cohort: “Age, BMI, nocturnal HR variance, claim frequency, social media sentiment score, geolocation clustering.” The sentiment score was a recent addition, a sentiment analysis on public posts that the insurer had begun to incorporate after a pilot in Bangalore. Maya’s mind flinched at the idea that a stray comment about a late night pizza could have nudged a risk curve upward.
She pulled up the cohort report that had been the focus of the previous week’s meeting. It was a PDF titled “High-Risk Cohort – 2024 Q3,” a PDF that listed a dozen anonymized IDs, a handful of risk factors, and a line chart that spiked each time the model adjusted its weights. The cohort was the very group that had justified the new underwriting rules she had been tasked to draft. She scrolled down to the bottom, where a footnote read, “Cohort size may be adjusted as new data points are excluded per opt-out requests.”
Maya’s fingers hovered over the mouse. Opt-out would reduce the cohort size, possibly lowering the model’s confidence and forcing a re-training. The insurer’s internal dashboards were built on gradient descent loops that ran nightly; a smaller cohort meant more variance in the loss function, which could manifest as higher false-positive rates for the remaining members. In other words, by withdrawing herself she might increase the risk for the people who stayed.
She remembered the dry joke Rahul had made when they first met in the analytics lounge: “If you opt out, you become a statistical black hole—nothing gets in, nothing gets out, and the model just pretends you never existed.” He’d said it with a grin, tapping his coffee mug against a stack of compliance manuals. The humor was a thin veneer over a deeper anxiety. Maya hadn’t laughed then; she’d only thought about the hole in the data set, the invisible void that could distort the very thing she was trying to fix.
Now she opened a new email to the compliance team, addressed to “Data Governance – Opt-Out Request.” She wrote, in a tone that was as measured as the policy documents she’d drafted all year, “Please remove all personally identifiable information and derived features related to my member ID (MKR-007) from any future model training cycles, and delete any existing feature vectors from the feature store.” She attached the signed consent form that the portal had auto-generated, and added a short note: “I am aware this may affect cohort statistics. I accept any downstream impact on model performance.”
She hesitated before hitting send. The legal team would likely respond with a standard acknowledgment: “Your request has been received. We will process it within 30 days in accordance with the Data Protection Act.” She imagined the reply, the polite language, the assurance that the system would respect her agency. But the system wasn’t just a collection of policies; it was a live process that churned on servers humming in a climate-controlled data center on the outskirts of Delhi.
The next morning, after the email bounced through the automated queues, Maya stood in the server room. The room smelled faintly of ozone and cooling fluid. Rows of racks stretched like the aisles of a warehouse, each unit blinking with green LEDs that pulsed in unison—a visual representation of the algorithm’s heartbeat. She wore her access badge, a thin polymer strip that granted her physical entry but did nothing to mitigate the ethical weight she carried.
She walked to the terminal that controlled the feature store. The interface was a command line, stark and unforgiving. She typed in her credentials, then a series of commands that she’d rehearsed in her head: “SELECT * FROM features WHERE member_id = ‘MKR-007’;” The query returned a list of rows, each a vector of numbers representing her nocturnal HR variance, her claim history, the sentiment score derived from a public tweet about a missed train. She scrolled through, the numbers stark and indifferent.
She typed, “DELETE FROM features WHERE member_id = ‘MKR-007’; COMMIT;” The system prompted for confirmation. She hesitated, then typed “Y.” The command executed, and the rows vanished from the table. She watched the log file scroll past, confirming the deletion. A small, almost imperceptible ripple ran through the monitoring dashboard—a brief dip in the cohort size indicator from twelve to eleven.
On a separate screen, the live model performance chart displayed a modest uptick in loss. The algorithm, oblivious to the human drama behind its parameters, adjusted its weights in response to the missing data point. Maya felt a faint prickle at the back of her neck, not from the humidity of the server room but from the realization that the model was still alive, still learning, still indifferent to the moral calculus it had just been forced to accommodate.
She stepped back from the terminal and glanced at the monitoring wall. One of the graphs showed a real-time risk distribution for the “High-Risk Cohort.” The line for her member ID, which had previously hovered at a sharp 0.84 probability of a cardiovascular event, was now a flat zero. The cohort’s average risk dipped marginally, the confidence interval widened. She made a mental note to inform Rahul that his black-hole joke had turned out to be technically accurate.
Maya left the server room with the door closing behind her, the soft hiss of the air-lock sealing her out. Back at her desk, she opened a fresh document titled “Cohort Reflections.” She wrote a single line, mirroring the tone of her earlier ethics note: “Excluding yourself reshapes the collective risk, but it also reshapes the collective narrative.” The line sat there, stark and unadorned, a quiet anchor in a sea of policy drafts and legal clauses.
She glanced at the clock. It was past midnight, the rain outside still drumming against the glass. The city’s neon lattice glimmered through the window, each light a node in a network of data points she could no longer claim to be part of. The algorithm continued to run in the background, its loss function still converging, its parameters still shifting. Maya leaned back, feeling the weight of the decision settle like a low-frequency hum—present, but not oppressive. She thought of Anjali, of the nocturnal tachycardia that had sparked this whole chain of events, and of the countless other unseen signals humming through the city.
A notification pinged on her screen: “Model training cycle complete. Updated cohort size: 11.” She stared at the number, at the fact that a single omission could be quantified, could be recorded, could be acted upon. The model would keep learning, and the system would keep watching. Yet for the first time in weeks, she felt a quiet optimism that a single act of agency could ripple outward, however faintly, into the algorithmic fabric of the world.
The app remembers where you stopped, reads chapters aloud, and works offline. Writing lives there too.