Thomas and I began with the desk computer.
Robert's password notebook remained in the top drawer, exactly where I remembered.
That fact embarrassed me now.
For years, the little black book had seemed harmless because only family came into the study.
Family.
The word had become its own security flaw.
Thomas did not touch the keyboard.
“We should have someone document this properly.”
“You think evidence might be on here.”
“I think if Brandon accessed protected information without authorization, we do not want to accidentally destroy a record.”
He contacted a digital-forensics specialist named Aaron Patel.
Aaron arrived that afternoon carrying two cases and the patient expression of someone accustomed to frightened people handing him complicated machines.
He asked me what I knew.
I told him Brandon had used the computer after Robert's death.
“How long?”
“Several hours.”
“Did he know passwords?”
“Yes.”
“Did you revoke them?”
“No.”
“Did you change your own passwords afterward?”
“Some. Not all.”
He nodded without judgment.
That was almost worse.
Aaron created copies of the computer's data and began reviewing browser histories, saved credentials, email settings, cloud accounts, and authentication records.
The work was slow.
While he examined the machine, Thomas and I searched paper files.
We found an old insurance portal login.
A hospital billing account.
A pharmacy service.
Then an online patient portal Robert had created for both of us years earlier when we used the same medical network.
“My account was separate,” I said.
Aaron looked over.
“Separate login?”
“I think so.”
“Shared recovery email?”
I didn't know.
He checked.
Yes.
The recovery email had originally been Robert's.
After Robert died, that address remained active.
Forwarding rules had been added.
“Where do messages go?” Thomas asked.
Aaron traced the settings.
“To another address.”
He read it aloud.
I knew it.
Brandon's.
The room went silent.
“When was forwarding added?” I asked.
Aaron inspected the data.
“Looks like about sixteen months ago.”
Two months after Robert died.
Around the time Brandon had helped me with the accounts.
“Does that mean he could read my medical information?”
“Depends on what notifications were sent and whether he could reset credentials.”
Aaron continued.
The answer became worse.
Password-reset messages from my patient portal had gone to Robert's old address.
Because the forwarding rule remained active, copies went to Brandon.
Someone had reset the password three times.
I had assumed I was forgetting it.
I remembered sitting at this desk in April, irritated because my usual password stopped working.
Again in July.
Then in October.
“Can you tell who reset it?”
“Possibly.”
Aaron reviewed login records.
Most connections came from my home.
Others came from an address associated with Brandon's city.
“How certain?”
“IP records don't identify a person by themselves. But the pattern is concerning.”
Thomas asked for a full report.
Aaron nodded.
I stared at the screen.
My medical portal contained appointment summaries.
Test results.
Prescriptions.
After-visit instructions.
And the hospital admission.
“How soon after I collapsed could he have known?”
Aaron examined timestamps.
He looked uncomfortable.
“What?”
“The portal shows an outside login while you were hospitalized.”
My hands went cold.
“When?”
“The first night.”
The first night.
While Margaret sat beside my bed, Brandon—or someone using access linked to his location—had opened my medical account.
“He knew.”
Thomas did not respond.
“He knew that night.”
Another login occurred the following morning.
Then a third after discharge.
Not one call.
Not one message.
Not one question.
I had spent weeks telling myself my children failed to notice because I had stopped initiating contact.
But Brandon had known almost immediately.
Worse, he had not merely known.
He had searched.
Aaron clicked through the access history.
Specific documents had been opened.
My discharge summary.
Cardiology notes.
Medication list.
A nursing note describing temporary confusion after the collapse.
That sentence later appeared, transformed, in paperwork suggesting cognitive decline.
I stood up.
Thomas said my name.
“I need air.”
I walked onto the patio.
Cold struck my face.
For several minutes I stared at the empty garden.
The hospital had frightened me.
I had awakened beneath fluorescent lights with wires attached to my chest, unable at first to remember how long I had been unconscious.
If Brandon had called that night, I would have forgiven almost anything before it happened.
That was the terrible simplicity of it.
He could have called.
He chose information instead.
When I returned inside, Aaron had found another trail.
Someone had downloaded portions of my records.
Files were later attached to an email draft inside Robert's old account.
The draft had been deleted, but remnants remained.
Recipient information pointed toward Brandon.
“Can we recover the attachment?”
“Possibly.”
By evening, Aaron reconstructed part of it.
My discharge summary.
The document Brandon needed to transform one medical incident into a narrative of incapacity.
Thomas removed his glasses.
“This needs to go to counsel experienced in health privacy and computer access.”
“Do it.”
Aaron glanced at me.
“There is something else.”
Of course there was.
“What?”
“The forwarding rule wasn't the only change.”
A secondary recovery number had been added to Robert's email account.
The final four digits matched Brandon's phone.
That meant he could keep control of the account even if a password changed.
“Can he still access it?”
“Not anymore.”
Aaron removed the recovery method and secured every linked account.
For the first time in sixteen months, the digital doors closed.
I changed passwords until my fingers hurt.
Medical portals.
Banking.
Email.
Utilities.
Insurance.
Cloud storage.
Anything connected to anything else.
Then I enabled additional security on all of them.
At nearly nine that night, Aaron packed his equipment.
Before leaving, he handed Thomas an encrypted drive.
“This has the initial preservation copy.”
Thomas signed a receipt.
The formality of it struck me.
My family had become a matter requiring chain of custody.
After everyone left, I received a message from Chloe.
Are you okay?
A normal question.
Two months earlier it would have meant little.
Now it mattered.
I answered.
No. But I will be.
She replied:
Can I help?
I considered telling her no.
Then I remembered what I had told her.
Stop apologizing and do something useful.
Find out who knew about the hospital.
Now I knew.
I typed:
Did Brandon ever tell you how he learned I was hospitalized?
Her response took several minutes.
He said David knew.
That interested me.
Did David say that himself?
No.
So Brandon had provided information while allowing everyone to assume it came from David.
I called Chloe.
She answered quietly.
“Mom?”
“Did Brandon ever mention having access to Dad's email?”
“No.”
“Think.”
She was silent.
Then she said, “Maybe.”
“What does maybe mean?”
“Last summer Jessica lost an old insurance document. Brandon said he'd check Dad's email because Dad kept everything.”
My grip tightened.
“How could he check it?”
“I didn't ask.”
“Did he do it?”
“Yes. He found the policy.”
That placed him inside Robert's account months before my collapse.
“Anything else?”
Chloe thought.
“He once told me you changed doctors.”
I froze.
“When?”
“Spring.”
“How did he know?”
“I assumed you told him.”
“I didn't.”
Each memory now carried a different meaning.
“How often did he talk about me when I wasn't calling?”
Chloe became quiet.
“Sometimes.”
“What did he know?”
“That you had a cardiology appointment. That you changed one medication. That you donated to some foundation.”
The donation.
My banking information?
Or merely a receipt in email?
“How did you not find that strange?”
“I thought you were still talking to him privately.”
There it was again.
All three children had assumed somebody else was communicating with me.
Because I had always done the work of keeping everyone connected, they apparently never noticed when there was no actual conversation underneath the information.
“Did Jessica know he had this access?”
“I don't know.”
“Ask carefully. Do not alert him.”
Chloe hesitated.
“Okay.”
After we hung up, I went into Robert's study.
The room no longer felt like his sanctuary.
It felt compromised.
I took the black password book from the drawer and placed it on the desk.
Robert had trusted paper.
Brandon had used the trust surrounding that paper.
I opened the final pages.
Several notes appeared in Robert's handwriting.
One caught my eye.
B — remove access after audit.
The date was two weeks before Robert died.
B.
Brandon.
I called Thomas immediately.
He answered on the second ring.
“I found another note.”
I read it.
Thomas was silent.
“Robert knew.”
“He knew something.”
“What audit?”
“We need to find out.”
The following morning, David supplied the files Thomas demanded.
Buried among them was an accounting memorandum dated eleven days before Robert's heart attack.
The subject line was simple.
Unauthorized access review.
Robert had discovered repeated logins to investment records.
He suspected Brandon.
But the report showed something stranger.
Two different access patterns existed.
One appeared tied to Brandon.
The second came from an account associated with Jessica.
My children had not started monitoring our finances after Robert died.
They had been doing it while he was alive.
At the bottom of the memorandum, Robert had handwritten:
Do not confront together. They cover for each other.
I read that sentence several times.
Then Thomas turned the page.
Attached was a note from Robert documenting a conversation with Chloe.
My youngest daughter had apparently come to him privately.
She warned him that Brandon and Jessica were discussing my inheritance years before anyone told me I called too much.
And according to Robert's note, Chloe had begged him not to tell them she was the one who warned him.
Click here to continue reading: PART 11: Robert’s Notes Proved Chloe Had Warned Him Years Earlier, but Her Silence After His Death Carried a Cost of Its Own
Three Months After My Children Asked for Space, Their Silence Taught Me Something Their Words Never Could
Part 10 of 35
