Chapter 3 - THE MAN WHO MISTOOK INFORMATION FOR SAFETY
Dominic’s security director kept files on everyone.
Not criminal files.
Worse in a quieter way.
“Household risk profiles.”
Dominic had approved them years earlier after a driver was bribed by a rival.
The profiles tracked:
debt.
family illness.
immigration issues.
divorce.
substance-use concerns.
custody disputes.
housing dependence.
romantic relationships.
Dominic believed:
know the pressure points before enemies do.
Then outside HR found Alina’s profile.
Widowed.
one minor child.
live-in housing.
medical issue: anemia.
financial vulnerability: moderate.
bereavement-related emotional stress in child.
There.
Dominic stared.
“How do we know the child is in therapy?”
The security director, Carlo Venn, hesitated.
“Benefits metadata.”
Wrong.
Not clinical notes.
Still.
Usage data had been copied into security scoring.
Dominic’s face changed.
“Delete it.”
Outside counsel stopped him.
“Preserve first. Audit access. Then delete what should not exist.”
Good.
No cover-up.
Then:
“Did I authorize this?”
“You authorized vulnerability mapping.”
There.
He had.
Again.
Not every field.
The system.
Still his.
Then employee review.
Forty-three current staff files.
Some data directly relevant:
a security guard with undisclosed gambling debt and access to weapons.
a driver with suspended license.
an employee under active restraining order involving a person who had threatened the estate.
Relevant.
Other data:
housekeeper’s fertility treatment.
cook’s adult son’s debt.
gardener’s sister’s immigration matter.
Alina’s child therapy.
Not relevant.
Good.
Then reforms:
minimum necessary.
role-based access.
no benefit-usage metadata.
no family vulnerability scoring.
no therapy information.
clear retention.
employee notice.
appeal.
Good.
Carlo objected.
“If we don’t know where pressure can come from, we’re blind.”
Dominic answered:
“We were collecting people.”
There.
Good.
Then:
“Security is not biography.”
That line stayed.
Carlo did not lose his job immediately.
Why?
He had followed broad directive.
Expanded beyond need.
Serious but contextual.
Authority narrowed.
formal discipline.
outside oversight.
Good.
Then one file revealed something worse.
A housekeeper had been denied promotion because her husband owed money.
No relation to her performance.
The manager had written:
“Household exposure too high.”
There.
Review.
Compensation.
promotion reconsideration.
manager discipline.
Good.
Then another employee claimed the same.
Records showed actual reason:
poor attendance before leave protections changed.
No improper risk-score use.
Claim denied.
Good.
Finite.
Then Alina learned her file existed.
Outside HR told her directly.
No Dominic summoning.
She asked for accessible copy.
Received with lawful redactions.
She stared at:
medical issue.
widowed.
child therapy usage.
Her hands shook.
Then anger.
Not fear.
She filed complaint.
Specific:
benefit confidentiality.
medical privacy.
employment decision risk.
Good.
Independent counsel handled.
Dominic could not adjudicate.
Good.
Then he asked if she would meet him.
Through HR.
She said no.
Good.
He accepted.
Three weeks later, after preliminary findings, she said yes.
Conference room.
HR present.
no Lucy.
Then Dominic said:
“I approved the system that created your profile.”
There.
No:
I didn’t know.
Then:
“I did not approve using therapy benefits.”
Specific.
Alina answered:
“But you built a system that rewarded people for finding more.”
There.
Good.
He nodded.
Then:
“I’m sorry.”
She looked at him.
“Are you?”
“Yes.”
Then:
“Does sorry delete who read it?”
“No.”
Good.
Then:
“Does it make me trust the benefits program again?”
“No.”
There.
No forced repair.
Then Alina asked:
“Did you read my whole file?”
“After the review started, yes.”
There.
Worse.
He could have had summaries.
Outside counsel had allowed principal access during investigation? Maybe, but still.
Alina’s face changed.
“You read about Mateo?”
“Yes.”
Then:
“Lucy?”
“Yes.”
He looked ashamed.
Good.
Then Alina said:
“You say you protect people by knowing everything. Do you understand what it feels like to be known by someone you didn’t choose?”
There.
Dominic did.
Not fully.
Enough.
Then he said:
“I’m changing access so I can’t do that again without defined reason.”
Better than promise.
Good.
Then outside review results.
Security files materially narrowed.
Medical and benefits data deleted after preservation and legal review.
Adverse employment decisions reopened.
Two employees received back pay or reconsideration.
One housing decision reversed.
Most files contained no adverse action.
Good.
Then Alina’s complaint outcome.
No evidence her therapy benefit changed employment.
No damages.
But privacy violation acknowledged.
record corrected.
written apology from household administration.
free credit/identity monitoring? Not relevant.
Maybe data misuse compensation modest if policy allowed.
She accepted record correction and independent counseling continuation.
Good.
Then she asked to move out of staff housing.
There.
Not because fired.
Because home and employer were too entangled.
She had savings now.
some.
Emergency fund still small.
She found a modest apartment.
Household policy required thirty-day notice.
Fine.
No retaliation.
Then Dominic heard through facilities.
Old instinct:
offer to pay deposit.
He did not.
Good.
Then Alina needed a reference.
Outside HR gave standard:
dates.
role.
performance.
No Dominic note.
Good.
She kept job for now.
Commuted.
That alone changed the balance.
Then Lucy saw the new apartment.
Small.
No garden.
No marble.
She loved the yellow kitchen.
Good.
Then one night she asked:
“Do we live here because Mr. Moretti was bad?”
Alina thought.
“No.”
Then:
“We live here because I wanted our home to belong to us.”
Good.
Then:
“Is he bad?”
Too big.
Alina answered:
“He has done bad things. He has also done good things. You do not need to decide what kind of whole person he is.”
Good.
Children should not carry moral verdicts.
Then Lucy asked:
“Can I still go to the gym?”
Alina smiled.
“Sometimes.”
Fine.
Then Dominic’s federal investigation intensified.
Subpoenas.
financial records.
witness interviews.
No connection to Alina’s complaint.
Important.
His old lending operation had used freight contracts as leverage.
A borrower named Samuel Price had disputed fees.
Dominic ordered:
No dock access until he settles.
There.
Supported.
Another borrower received relief after cancer.
No condition.
Also supported.
Good.
Then one collector, Rocco Vale, had assaulted a debtor.
Rocco claimed:
“Dominic wanted him scared.”
Maybe true.
Not proof of assault order.
Emails showed Dominic authorized intimidation visits but not violence.
Bad enough.
Then counsel told him:
“You built systems where men guessed how much fear pleased you.”
There.
Same household pattern.
Good.
Dominic sat in his office after everyone left.
He thought of Alina’s question:
Do you understand what it feels like to be known by someone you didn’t choose?
He had spent half his life collecting information because uncertainty felt dangerous.
Now every reform seemed to involve giving up information:
employee benefit use.
medical details.
childcare names.
staff family problems.
He had thought safety came from fewer unknowns.
It was beginning to look like trust required tolerating them.
The privacy review also changed how Alina viewed benefits.
For months she had resisted using anything connected to the estate because she feared every request created a record.
Now outside HR gave employees a simple privacy chart:
What the benefit provider sees.
What HR sees.
What security sees.
What Dominic sees.
Good.
Dominic’s column was mostly:
aggregate cost.
That made people laugh.
Good.
Then Alina used the pharmacy benefit again.
No one called.
No one asked why.
No security note appeared.
Trust did not return because the policy said it should.
It returned through boring repetition.
Then one more file surfaced.
A driver had told security that he was in debt because his mother needed dialysis.
Security had marked:
“financial pressure.”
Relevant at first because he transported cash.
But nobody had offered:
role reassignment.
financial counseling.
support.
They had only labeled risk.
There.
Good.
The new policy required:
if a vulnerability affects a role, first consider risk reduction that does not punish the worker.
Reassign cash duty.
offer support.
document.
review.
No automatic suspicion.
Then Alina asked:
“What happens if someone lies?”
Outside HR said:
“Then investigate the lie.”
Good.
Not everyone presumed truthful.
Not everyone presumed dangerous.
Evidence.
Then Dominic’s own file?
Alina joked once:
“Do you have a risk profile?”
He said:
“Probably.”
Then thought.
The biggest vulnerabilities in the house had never been listed:
his pride.
his need for control.
his fear of uncertainty.
No spreadsheet would have solved those.
One final privacy issue came from the mansion’s old visitor logs.
Security had kept them indefinitely.
Names.
arrival times.
vehicle plates.
who employees met after work if they entered through the gate.
Some retention was reasonable for security.
Forever was not.
New policy set clear periods:
shorter for ordinary visitors.
longer only where an incident justified preservation.
Good.
Employees could request corrections.
Alina did.
One log described Lucy’s therapist as “behavioral consultant.”
Too vague and too suggestive.
Corrected to:
authorized visitor, no operational detail.
Good.
A child’s care did not belong in a security narrative.
That distinction became the core rule of the new system: collect what the role needs, explain why, and stop when the reason ends.
Anything broader required justification.
Not curiosity.
Not fear.
Not “just in case.”
Dominic disliked how often “just in case” had once been enough.
Now it was not.
And the rule stayed after the headlines faded.
May you like
That mattered more than the apology.
That boundary remained boring, visible, and enforceable. Exactly as it should have been.
Related Stories
