Why We Created Digital Divorce: The World’s First Protocol for Ghosting an Ex
- Cyber Houdini
- Apr 8
- 3 min read
Updated: Apr 9
We didn’t set out to build the world’s first protocol for ghosting an ex.
At the time, it didn’t seem necessary. The world already had an answer to digital threats: change your passwords, enable two-factor authentication, be careful what you click. The assumption behind all of it was the same, the danger comes from the outside. From anonymous actors. From distant places. From people you will never meet.
But that wasn’t what we were seeing.
What we saw, over and over again, was much closer to home.
It was the ex who still had access. The jaded former employee who knew how things were set up. The jealous brother-in-law who had been around just long enough to understand where to look.
These weren’t elite hackers. Most weren’t technically advanced. What they had was familiarity.
They knew your habits, your patterns, your blind spots. They didn’t need to force entry; they had already been given it, at some point, under very different circumstances.
And when relationships change, access rarely gets revisited with the seriousness it requires. That’s where the problem begins.
Some situations were obvious, a clear act, a line crossed. In a strange way, those were easier. At least there was no ambiguity.
More often, it was quieter than that.
Small things. Subtle interference. Information appearing where it shouldn’t. Actions that didn’t quite make sense, but weren’t dramatic enough to trigger a response. A kind of low-level sabotage that operates just below the threshold of certainty.
That’s where most traditional approaches fall short, because they treat this as a technical problem. What we were seeing was something else entirely. It was psychological.
The individuals behind these situations weren’t thinking like cybersecurity professionals. They weren’t following playbooks. They were acting out of emotion, resentment, jealousy, a need for control, sometimes simply curiosity taken too far.
And psychology changes how people behave. It makes them persistent, creative, and willing to test boundaries repeatedly, to try the obvious and the non-obvious, to look in places others wouldn’t think to check.
They don’t need to be highly skilled. They just need to be motivated. And in many cases, that is enough.
This was the pattern, and it pointed to something most advice ignores: proximity.
Not just physical proximity, but informational proximity, the accumulation of shared access, known credentials, familiar systems, and implicit trust that lingers long after a relationship has changed.
We began to think of this as residual access. Once you see it, you realize how much risk lives inside it.
The solution wasn’t more tools, alerts, or complexity. It was removal.
If you can systematically identify and eliminate access across accounts, devices, and behaviors, you don’t just reduce risk, you remove the conditions that make it possible in the first place. Even when someone is technically capable, removing that initial foothold changes the situation entirely. It limits what can be done and, in many cases, prevents escalation.
But access alone isn’t the full story.
People don’t just exploit systems. They exploit assumptions, what someone believes is private, what they assume no one would think to check, what they overlook because it feels too small to matter.
That’s why the approach had to be holistic. It had to go beyond devices, passwords, and account settings. It had to account for psychology, how people think when they feel wronged, when they feel entitled, when they are looking for leverage.
Protection, in this context, is not just technical. It is psychological, the ability to understand how someone might act when they turn against you, to see where they would look, and to anticipate what they would try.
That is what led to the creation of the protocol.
Not just a collection of technical fixes, but a structured way of removing access, understanding psychology, and reshaping how people think about privacy and risk. Something practical, repeatable, and grounded not just in systems, but in human behavior.
We chose to build it as a foundation, not a subscription. The goal wasn’t dependency, it was capability, a one-time investment that gives people the principles to act and the awareness to adapt as situations evolve.
Because they do evolve.
The tools will change. The methods will change. But the psychology, the motivations, the patterns, the behavior, remains remarkably consistent.
This wasn’t created to introduce a new idea. It was created to respond to one that was already there, quiet, persistent, and, for most people, completely unseen.
P.S. The protocol is updated over time to reflect changes in tools and methods. Those who have access continue to receive those updates.
.png)