Chapter 4
SomnaSafe sent us a forty-three-page incident report.
I expected legal language.
There was plenty.
But the useful parts were tables.
Account created:
January 8.
Sponsor code:
ELAINEPORTER_FF12.
Guardian name:
Daniel Reeves.
Account owner email:
marianne.reeves@—
Guardian verification:
manual sponsor override.
That phrase became important.
Manual sponsor override.
It sounded technical.
It meant:
Elaine vouched.
No email to me.
No ID check.
No co-parent confirmation.
The beta system had a shortcut for trusted referrals.
My mother entered through it.
Then signature.
The PDF stored:
typed name.
drawn signature.
IP address.
device identifier.
IP:
my mother’s home.
Device:
her tablet.
No plausible claim that I had signed from my office.
Good.
Then data collection.
The report separated:
raw source.
processed events.
beta research clips.
Raw source:
stored in encrypted cloud bucket under Theo’s participant ID.
Processed events:
sleep/wake classifications.
cry durations.
room temperature.
adult-presence estimate.
caregiver response interval.
That last phrase made Megan furious.
“Adult-presence estimate?”
Priya explained by video call:
“The beta tried to estimate whether a caregiver responded within certain windows.”
“To grade us?”
“Not intended as a clinical grade.”
“That wasn’t my question.”
Priya paused.
“The roadmap included caregiver adherence scoring.”
There.
The same phrase from USB.
Then Megan asked:
“Adherence to what?”
“App recommendations.”
“So if I picked up my own baby before your model wanted me to, I could be marked nonadherent?”
“In the pilot version, yes.”
I watched Megan’s face.
The company had designed a metric.
My mother had turned it into authority.
That distinction mattered.
SomnaSafe did not tell Marianne:
fire the nanny.
It gave her a dashboard where ordinary disagreement could look like noncompliance.
Then model notes.
Internal bug ticket:
participant TREV-042 has frequent manual caregiver overrides; model confidence reduced.
That was Theo.
No names in ticket.
But enough.
Another:
visual obstruction events common; caregiver may be blocking sensor.
Again:
Lena hanging a cloth.
Then support notes from my mother.
“Camera view blocked again after nanny enters.”
“Can system alert if caregiver lifts baby too early?”
“Can I lock recommendation schedule so household members cannot modify?”
That last one.
Priya said:
“The answer from support was no.”
Good.
Then:
“Did anyone tell her the parents needed to control settings?”
“Yes.”
Show me.
Support response:
Because you are registered as account owner and Daniel Reeves is listed as guardian, please confirm all household caregivers have been informed of device operation and data collection.
Marianne replied:
They know we use monitoring equipment.
Technically true.
We used a baby monitor.
Not this.
Then another support agent wrote:
For recording features, explicit household disclosure is recommended.
Recommended.
Not required in the beta workflow.
The company had left ethics as a suggestion in a place where the product collected video inside nurseries.
Priya did not defend.
“Our controls were inadequate.”
Good.
Then:
how many homes?
We did not need customer numbers.
But we needed to know whether this was a one-off loophole or broad risk.
SomnaSafe said:
seventeen founding-family beta accounts used sponsor override.
All under review.
Were any other guardians unverified?
They would investigate.
No public drama yet.
Good.
Then deletion.
Megan wanted every file gone.
I did too.
Nina Patel, our attorney, advised:
“First preserve what proves unauthorized collection. Then request deletion of everything not legally required to retain.”
That felt awful.
To get rid of private recordings, we first had to preserve evidence that they existed.
Again:
records can protect and violate at the same time.
We agreed:
SomnaSafe would preserve a limited legal copy under access restriction.
all product-development duplicates quarantined.
training extraction stopped.
raw consumer copies scheduled for deletion after forensic verification and counsel signoff.
Could they delete every trace?
No.
System backups rotate.
audit logs remain.
certain incident records retained.
I hated the word backups.
Megan said:
“I want written retention dates.”
She got them.
Specific.
Then we reviewed access logs.
My mother opened forty-six video clips.
Which ones?
SomnaSafe provided thumbnails first.
We could choose whether to inspect.
We did not want to watch everything.
We needed categories.
Priya’s team created:
baby only.
caregiver present.
parent present.
sensitive care.
Sensitive care:
feeding.
changing.
partial undress.
My mother had opened six sensitive-care clips.
Megan’s face went white.
“Which?”
I almost told Priya not to say.
Then stopped.
Megan decides.
She said:
“Tell me.”
Four nursing clips.
one diaper change with me.
one clip where Megan changed her shirt after spit-up while camera still active.
My hands shook.
“Did Marianne know what was in them before opening?”
No way to know.
Thumbnails likely visible.
She opened.
That was enough.
Why?
We later asked.
Not yet.
Then audio.
My mother opened thirty-eight audio samples.
Some:
crying.
white noise.
voices.
Transcript snippets were machine-generated.
One clip:
Megan saying to me at 2 a.m.:
“I cannot do another night like this.”
My mother opened it twice.
That line later appeared in one of her CARE NOTES.
Megan stood.
Walked out.
I followed.
In hallway she said:
“She used something I said to you in the middle of the night.”
“Yes.”
“It wasn’t even to her.”
“I know.”
“That feels worse than the camera.”
I understood.
A camera catches bodies.
Audio catches unguarded meaning.
Then she said:
“I want your mother to know exactly what she watched.”
Not to shame her publicly.
To remove ambiguity.
Later.
Then we looked at the USB provenance.
My mother downloaded everything the same day SomnaSafe froze account.
Why USB?
She feared the company would delete the archive.
Ironically, she wanted to preserve what she had no right to collect.
Then she intended to remove devices.
Destroy one?
Why not just unscrew?
The shelf sensor mount used industrial adhesive.
She had tried a putty knife.
Lena heard scraping.
The iron came because the flat metal soleplate could break plastic cleanly.
My mother had not heated it.
Important.
Cordless iron was cold.
Still heavy.
Still above crib.
Still reckless.
The police report reflected that:
no evidence of intent to injure child.
reckless handling of heavy object near infant.
physical confrontation with caregiver.
potential evidence tampering issue referred for review.
No sensational attempted assault charge.
Good.
Then forgery.
Digital signature.
Would prosecutors charge?
Unknown.
The officer said family misuse of an e-sign consent could fall under several statutes depending purpose and loss.
No promise.
We did not demand arrest.
We asked for accurate report.
Then BrightNest’s final finding.
Lena had not violated care standards.
All complaints by Marianne removed.
Agency apologized in writing.
Then a harder part.
BrightNest admitted:
their intake form allowed emergency contacts to submit “care concerns.”
staff did not distinguish:
safety report
from
performance management.
New process:
safety concerns from anyone can be reported.
performance complaints require client confirmation before personnel file entry unless direct evidence of immediate danger.
That was sensible.
Then Lena decided to return.
Not immediately.
After twelve days.
Her conditions:
Marianne not enter during shifts.
no hidden recording devices.
written notice of any monitoring equipment.
agency is employer contact.
I do not ask Lena to manage family conflict.
All reasonable.
We agreed.
Then Lena said:
“I don’t want an apology from your mother.”
“Okay.”
“If she sends one through you, don’t give it to me.”
“Okay.”
Good.
Boundaries need not end in reconciliation.
Then my mother.
She emailed once daily for the first week.
Too much.
Even without demands.
I replied:
One email per week. Emergencies only otherwise.
She answered:
Understood.
Then stopped.
Good.
Her next email contained no defense.
Only:
I opened private recordings of Megan and Daniel that I had no right to see. I am not going to explain that as concern.
I stared.
Megan read.
Then:
“That’s accurate.”
No forgiveness.
Then my mother wrote:
I contacted Lena’s employer because she would not follow a system I had installed without your permission. I treated her resistance to my secrecy as evidence that she was a poor caregiver.
Also accurate.
Then:
I used Emily’s death as permission to override you.
That sentence hurt.
My sister’s name.
Then:
I do not yet understand why being afraid made me feel entitled rather than simply afraid.
Better than:
I couldn’t help it.
Then no request to see Theo.
Good.
We did not answer.
Then Elaine Porter resigned from SomnaSafe’s advisory board.
Not because we demanded.
Company investigation found she knowingly allowed a beta enrollment without verified guardian consent after learning disclosure had not occurred.
No evidence she watched our private footage.
No evidence she directed complaints against Lena.
Her responsibility was narrower.
She acknowledged.
SomnaSafe offered:
refund? We never paid.
identity protection? Irrelevant.
legal fee contribution.
privacy settlement discussion.
Nina handled.
We did not post online.
Not yet.
Then the company announced beta suspension.
Public reason:
consent-verification review.
No names.
That was appropriate.
Then one night, two weeks after Lena returned, Theo cried at 1:06 a.m.
The normal baby monitor lit up.
I reached for phone.
Then froze.
For months, my mother had built an entire worldview around response time.
Two minutes.
three minutes.
too fast.
too slow.
I put the phone down.
Walked into nursery.
Picked up my son.
He stopped crying.
No dashboard scored me.
No model decided whether I had reinforced waking.
May you like
He needed his father.
That was enough data.
