Before he could close the distance between us, the phone he had abandoned on the hallway table flashed awake, and the banner across its screen was tied to an account that belonged to me.
I saw it.
He saw me see it.
The difference was that his free hand moved toward the phone while mine was already closer.
I hooked my good hand around the edge of the table, dragged the phone toward me, and nearly dropped my laptop when another bolt of pain ripped through my swollen wrist.
“Give me that.”
His voice had changed again.
No yelling now.
No pretending either.
He still had the black server tucked against his side, one arm wrapped around it like it mattered more than the fact that he had just shoved me hard enough to put me on the floor.
I looked down at his phone.
The notification preview was brief, but I recognized the account name immediately because it was mine.
“Why is my account sending alerts to your phone?”
He reached for it.
I stepped backward.
“Give me the phone.”
“Answer me.”
“You don’t understand how any of this works.”
There it was again: the same explanation he had been feeding me for weeks, only now it sounded different because he was standing in front of a hidden machine he had ripped out of a closet while carrying a notification from my account on his own phone.
He wanted me confused.
He wanted me dependent.
He wanted every technical problem to end with me handing him my laptop.
He wanted the laptop now because I had finally stopped doing that.
The router finished rebooting behind us, and the lights stabilized one by one.
My cousin looked toward the living room as if he could hear the connection coming back.
I opened my laptop with my good hand and waited for the Wi-Fi icon to return.
“Don’t.”
That single word told me more than another explanation would have.
I clicked into the security page for the account named in the notification.
My fingers were clumsy because I was balancing the laptop against my body and trying not to move my injured wrist, but I did not need to dig through anything complicated to find the first problem.
A recovery phone number was attached to my account.
It was not mine.
I recognized the last digits.
They belonged to him.
For a few seconds, I just stared at the screen while my brain tried to catch up with what my eyes were showing me.
Then I turned the laptop toward him.
“Is this your number?”
He looked at the screen and immediately looked away.
“Is it?”
He tightened his arm around the server.
“I put that there because you kept locking yourself out.”
I almost laughed, but the pain in my wrist stopped me.
“I never asked you to.”
“You would have lost access to everything.”
“Then why didn’t you tell me?”
He had no answer ready for that.
I changed the recovery number.
His phone vibrated in my hand.
He took a step forward.
I changed the password.
His phone vibrated again.
I signed the unfamiliar sessions out.
His expression finally changed.
Not because I had accused him.
Because his access was disappearing.
“Stop doing that,” he said.
I looked at him over the top of the laptop.
“Why?”
“You’re going to mess up your accounts.”
“They’re my accounts.”
“You don’t know what’s connected.”
That sentence landed differently from everything else.
“What’s connected?”
He glanced at the black machine in his arms.
Then he made the mistake of trying to bargain with me.
“Give me the laptop for ten minutes and I’ll put everything back the way it was.”
I stared at him.
He seemed to realize too late what he had admitted.
“Put what back?”
“That’s not what I meant.”
“What were you going to put back?”
He shifted the server against his chest and looked toward the front of the house.
I suddenly understood that I did not need to win an argument with him.
I needed to keep control of my laptop, keep control of my accounts, and get away from someone who had already used physical force when I refused him access.
So I stopped trying to make him confess.
Instead, I kept changing what belonged to me.
The next account had unfamiliar recovery information too.
Another had security notices I did not remember receiving.
Another showed sessions I could not explain.
I did not start opening private messages or trying to reconstruct every strange event from the previous month while he was standing three feet away from me.
Control first.
Questions later.
He watched me work through the accounts he had always insisted were simply suffering from my “bad password habits,” and the more access I removed, the less interested he became in pretending this was about helping me.
“You’re making a huge deal out of nothing.”
I looked up.
“You shoved me onto the floor.”
“That was because you wouldn’t listen.”
I felt something inside me become very still.
Not calm.
Clear.
“You broke my wrist because I wouldn’t give you my computer.”
“I didn’t break anything.”
I raised my swollen arm slightly.
He looked at it for less than a second.
Then he looked back at the laptop.
Even then, the laptop mattered more to him.
I had spent weeks wondering whether I was becoming forgetful, careless, or paranoid because every strange digital problem seemed small enough to explain away by itself.
A reset notice could be spam.
An opened message could be an app syncing badly.
A changed setting could be an update.
One unexpected sign-out could happen to anyone.
But dozens of small incidents stop looking random when the person who has been dismissing them is standing beside a hidden server with your account connected to his phone.
He moved toward the front door.
I did not block him.
I could not have stopped him physically even if I had wanted to, and the way my wrist was swelling made that decision easy.
He reached for his phone.
I held it out but did not release it immediately.
“Why was my account on this?”
He looked at me.
“For recovery.”
“Did you add your number?”
He hesitated.
“Yes, but—”
That was enough.
I handed him the phone.
I did not need a speech.
I needed distance.
He took the phone, adjusted the server under his arm, and started toward the door.
Then he stopped.
“Give me the laptop.”
“No.”
“If you mess something up, don’t blame me.”
“No.”
“You’ll come begging me to fix it.”
“No.”
The third answer was the one that finally ended the conversation.
He left carrying the black server.
I stayed where I was until I heard the door close.
Only then did I sit down against the wall because my knees had started shaking.
The pain was no longer sharp in one place.
My whole forearm throbbed, and my fingers had swollen enough that using the keyboard was becoming difficult.
I finished only the most important account changes before I stopped.
I changed access.
I changed recovery information.
I changed the places where alerts were supposed to go.
I changed something more important too: I stopped treating his explanation as more trustworthy than what I could see with my own eyes.
I did not go back to the closet and start pulling apart cables.
I did not try to chase him for the server.
I did not convince myself that the injury could wait because the digital mess felt more urgent.
My wrist needed medical care, and for once I put the obvious thing first.
At the emergency room, the questions were simple.
How did it happen?
Where did it hurt?
Could I move my fingers?
I told the truth: my cousin had tried to take my laptop, I refused, and he shoved me with both hands.
Imaging confirmed the fracture.
Seeing it documented in plain medical language affected me more than I expected, because I had spent the ride there hearing his voice in my head saying he had not broken anything.
The record did not care what he called it.
My wrist was broken.
I left with it immobilized and with strict instructions to protect it while follow-up care was arranged.
I also made a report about what had happened in the house.
I was careful about what I claimed.
I knew he had pushed me because I had been there.
I knew the server had been hidden in the closet because I had seen it.
I knew his phone received a notification from my account because I had held it in my hand.
I knew his number had been attached to at least one recovery setting because I had seen the digits myself.
What I did not know was exactly what the server had been doing, how long it had been operating, or whether every strange account event had come from him.
That distinction mattered to me.
I was done being manipulated, but I was not going to make the truth weaker by decorating it.
The next morning, with my wrist aching inside the splint, I started reviewing my accounts slowly from a safe place he could not access.
This time there was no cousin leaning over my shoulder offering to “clean things up.”
There was only me, my laptop, and the history I had been too intimidated to trust before.
The pattern was clearer than I wanted it to be.
Security settings had been changed.
Warnings had not always reached the contact information I expected.
Sessions appeared that I did not recognize.
Some of the timing lined up disturbingly well with the days when my cousin had casually asked whether an account was “acting weird again.”
That detail bothered me most.
He had often seemed to know I was having trouble before I told him.
I used to interpret that as proof that he understood technology better than I did.
Now I wondered whether the simpler explanation was that he knew because he had access.
I preserved what I could without digging through anything unrelated.
Screens showing recovery changes.
Security notices.
Dates.
Session information.
The messages he had already sent me about handing over the laptop.
Then, late that afternoon, he gave me something more useful than any argument we had exchanged in the hallway.
He texted me.
At first, he acted offended.
He said I had embarrassed him.
He said the server was his personal equipment and I had no right to interfere with it.
He said I had misunderstood a setup that had been “helping” me.
Then he complained that changing the recovery information had locked him out of things he needed to “maintain.”
I read that sentence twice.
I answered with one question.
“Why did you need access to my accounts at all?”
His reply took longer.
When it came, it was a paragraph about how careless I was, how often people get hacked, how he had been protecting me from myself, and how I would understand eventually.
He never answered the actual question.
So I asked it again.
“Why did you need access to my accounts?”
This time he wrote that somebody had to monitor things because I refused to let him help.
Monitor things.
That was the phrase.
He had spent weeks telling me nothing unusual was happening while privately claiming he needed to monitor the very accounts he said were fine.
I saved the exchange.
He continued messaging for two days.
His story changed depending on what he thought would work.
First he had only added a recovery number.
Then he had only checked security.
Then he had only used the setup after I supposedly created problems myself.
Then the whole thing was my fault because I had reset the router without warning.
Each new explanation made the earlier one harder to believe.
What never changed was his assumption that he had been entitled to access because he thought he knew better than I did.
That was the part I had failed to recognize before the shove.
The technical details mattered, but the relationship had been giving me the same warning for weeks.
Every time something went wrong, he positioned himself as the only person allowed to solve it.
Every time I asked a question, he made me feel foolish for asking.
Every time I hesitated to hand him a device, he treated my privacy like an inconvenience.
And when I finally said no, he did not respect the boundary.
He used force.
The broken wrist made it impossible to keep describing the situation as an awkward family disagreement.
Whatever he believed about his intentions, he had decided that my refusal did not count.
That changed how I handled everything afterward.
I stopped debating whether I was being “too harsh.”
I stopped passing messages through relatives trying to make the conflict sound smaller.
I stopped offering him opportunities to explain the same behavior in softer words.
There was nothing complicated about the boundary anymore.
No access to my devices.
No access to my accounts.
No private troubleshooting sessions.
No physical proximity while he was angry.
For the accounts that offered formal recovery or support processes, I used them.
For the rest, I worked through the security settings myself, slowly, with one functioning hand and more patience than confidence.
It was frustrating.
It was boring.
It was mine.
That last part mattered.
Over the next several days, the strange behavior began to stop.
I was no longer being thrown out of accounts while using them.
Password resets stopped appearing without explanation.
Messages no longer showed as opened before I reached them.
Settings stayed where I put them.
I cannot prove that every single earlier glitch came from my cousin, and I do not need to.
The facts I could establish were already serious enough.
He had unauthorized recovery access.
He had hidden networking equipment attached to the household connection.
He had panicked when that connection failed.
He had tried repeatedly to obtain my laptop.
He had admitted in writing that he had been monitoring accounts he did not own.
And when I refused to surrender the device, he had shoved me hard enough to fracture my wrist.
The black server never became the magical answer to every question.
He had taken it with him, and I refused to build my entire understanding of the situation around a machine I no longer possessed.
The stronger evidence was less dramatic.
It was the recovery number.
It was the alerts.
It was the account history.
It was his own changing explanations.
It was the medical record.
Most of all, it was the fact that once his access was removed, the problems that had made me doubt myself began disappearing.
My wrist took longer.
For weeks, ordinary things became annoying negotiations with my own body.
Opening jars hurt.
Typing was slow.
Getting dressed required more planning than it should have.
Even carrying a paper coffee cup while holding my laptop case became something I had to think about.
That physical inconvenience kept dragging the night back into the present long after the accounts were secure.
Sometimes I resented that.
Other times it reminded me why I had stopped accepting explanations that required me to ignore what actually happened.
My cousin continued insisting that he had been trying to help.
I eventually stopped answering.
The report existed.
The records existed.
His messages existed.
I did not need another private confrontation to make any of them more real.
What happened after that moved slower than the night itself.
Account reviews take time.
Medical follow-up takes time.
Family consequences take even longer because people often want a version of events that allows everyone to sit at the same table again without choosing sides.
I could not give them that version.
I also did not ask anyone to hate him for me.
I asked for one thing instead: do not give him access to my belongings, my devices, my passwords, or information about where I am staying.
That boundary was practical enough that people either respected it or revealed that they would not.
There was relief in that simplicity.
Months later, after my wrist had healed enough that typing no longer reminded me of every keystroke, I noticed something almost embarrassingly ordinary.
My laptop had become boring again.
No mystery sign-outs.
No unexplained reset notices.
No settings quietly changing back.
No cousin appearing at my shoulder with his hand out, telling me to give him the computer for ten minutes.
The router was just a router.
A notification was just a notification.
A password change happened when I initiated it.
For a long time, every blinking light had felt like a warning that someone else might already be inside a part of my life I thought was private.
Eventually that feeling faded.
I still remember the exact sound of my laptop shifting against my chest when I hit the floor that night.
I still remember the router going dark.
I still remember my cousin asking, “What did you do?” before he asked whether I was hurt.
At the time, I thought accidentally resetting that router had created the disaster.
It had only interrupted it long enough for me to see what had already been happening.
One evening, I sat down with the same laptop, rested both hands comfortably on the keyboard, and watched an ordinary blue notification light blink beside the screen.
Then I opened my work and kept typing.
