Keeping your own identity out of the fleet

A customer wrote to me last year because forty of his accounts had gone in one afternoon. We spent a while working through what happened, and the setup itself was genuinely good. Separate profiles, separate lines, separate mailboxes, all of it.

Then he mentioned, almost in passing, that the recovery email on eleven of those accounts was his own Gmail. The one with his name in the address.

Everybody isolates the accounts from each other. Almost nobody isolates themselves.

I run proxy lines and rented phones for people doing exactly this kind of work, so I see the setups, and I see them after they break. The pattern is consistent enough that it deserves its own explanation, because it’s the part that costs the most and gets the least attention.

What this is actually about

Not hiding from anyone. I want to be clear about that up front, because this topic attracts a certain kind of question, and I’m not answering that kind of question.

This is about not letting your personal accounts and your working accounts end up in the same file. Your own bank, your own mail, the account you’ve had for fifteen years with your family photos in it. Those things shouldn’t be reachable from the fleet, and for most people they currently are.

The reason isn’t that anyone is coming for you specifically. The reason is that enforcement is automatic and it follows connections. If the connections lead back to your own account, your own account is in scope.

The mailbox

This is the first one, and it’s the most common by a distance.

You set up an account, it asks for a recovery address, and you’re in the middle of something, so you put in the address you can actually check. Yours.

Now, in that company’s records, there’s a permanent line joining that account to you. Not to a working identity you invented. To the mailbox that also receives your electricity bill.

What makes this worse than it sounds is how much weight a recovery address carries. It’s the route the platform uses to establish that you are who you say you are, which makes it the most trusted field on the account. It’s stored, it’s durable, and it’s exactly what a system looks at when it wants to know whether two accounts belong to the same person.

Do it once on one account and you’ve joined one thing. Do it eleven times, as my customer had, and you’ve joined eleven things to each other through you.

The payment

Second, and it’s the one people defend the hardest.

Funding a fleet is annoying. You need to pay for lines, for tools, sometimes for the accounts themselves, and the easy way to do that is the card in your wallet.

But think about what a platform sees when a card arrives. An identifier with a name attached, verified by a bank, which makes it one of the highest confidence signals available for saying two accounts belong to the same person. Higher than a shared address in most cases, because addresses change and cards mostly don’t.

I want to be fair here. For a lot of small operations there’s no clean alternative, and telling somebody to run a separate legal entity for six accounts isn’t useful advice. So the honest version is this: know that the card is doing it. Don’t pretend it isn’t. And if the operation grows to the point where losing it would actually hurt, that’s the moment to fix the payment path, not later.

What I wouldn’t do is what a lot of people do, which is use their own card and then feel protected because everything else is separated. The separation is only as good as its weakest join, and the card is usually it.

The one session

Third, and this is the one that gets people who are otherwise careful.

Everything is set up properly. Profiles are clean, lines are clean, nothing crosses. Then one evening you need to check your own email quickly, and the working profile is the window already open.

That’s enough. One session, from the same profile or the same address, and the two are now observed together. You can’t take it back, and you’ll usually never know it happened.

What makes this specific failure so common is that it never feels like a decision. Nobody sits down and thinks about whether to log into their personal account from a work profile. They just do it, because the window was there and it was going to take four seconds.

So the rule that works has to be blunt rather than careful. Nothing personal ever opens in the working environment. Not once, not for four seconds, not to check something. Bluntness is the whole feature, because a rule with judgment in it requires you to exercise judgment at eleven at night, and that’s precisely when you won’t.

There’s a version of this that catches people running teams, too. You tell somebody the rule, they understand it, and then they use their own phone to approve something because yours was charging. The rule has to cover everyone who touches the machines, and it has to be stated rather than assumed, because a person who was never told will do the convenient thing every time, and will be right to think it was fine.

The number

Fourth. Shorter, but worth saying.

Verification asks for a phone, you don’t have a spare one to hand, and your own is in your pocket. So it goes in.

Now your number, which is attached to your name at a carrier, which is attached to your bank and probably your government identity, is sitting in the account record. Unlike a mailbox you can abandon, most people keep the same number for years, so it’s one of the most stable identifiers you own.

The same shortcut logic applies. It happens because it’s available at the moment you’re stuck, not because anyone decided it was fine.

There’s a second problem with your own number that people miss. You’ll eventually want it off that account, and removing it doesn’t remove the record that it was there. The platform keeps the history. The number isn’t a decision you can reverse later by tidying up, which is how most people imagine it.

The machine

Fifth, and it’s the quietest one, because it involves nothing you typed.

The working profiles are isolated from each other. Good. But they’re all sitting on one computer, and so is your own browser, your own signed-in accounts, your own everything. If that machine is ever the thing that gets examined, whether by malware or by somebody borrowing it or by a support tool you installed and forgot, the isolation between profiles stops being the relevant question.

I’m not going to overstate this. It’s a lower probability failure than the mailbox or the card, and for most people it never happens. But it’s the one where the blast radius is everything at once, and it’s the cheapest to reduce, because a second user account on the same machine costs nothing and takes ten minutes.

The vendor

Sixth, and I only know this one because I sit on the receiving end of it.

People buy lines and phones from me using their own name and their own mailbox, then run a fleet behind them. I link nothing myself. What I do hold is a record that joins a real person to a block of infrastructure. So does every other supplier you’ve ever paid, and so does the processor that moved the money.

Asking a supplier to delete your details after the fact only reaches the copy they control. The payment trail is somebody else’s record.

If you wouldn’t want the fleet traced back through the people you buy from, buy like it.

Why this is different from ordinary linkage

Here’s the part I actually want people to take away, because everything above is just a list until you see the shape of it.

When two working accounts get linked, you lose two working accounts. That’s a cost, and it’s a cost you planned for. You have others.

When the fleet gets linked to you, the direction reverses. An action against the fleet can now reach the account you were never treating as part of this. Your real mailbox. Your real payment relationship. The account that has your actual correspondence in it, or the photos, or the thing you can’t rebuild because it took nine years to accumulate.

And that account has no backup, because you never thought of it as an asset at risk. You thought of it as your email.

That’s the whole argument. The fleet is replaceable by design, and you’re not.

What actually works

Practical, and short, because the list is short.

Decide the boundary once and write it down. One sentence is enough: nothing personal touches the working environment, ever, for any reason. Writing it down matters more than it sounds, because a rule you’ve articulated survives a moment of convenience, and a rule you’ve only felt does not.

Separate the mailboxes properly. Not a filter, not a folder, a genuinely different account reached a different way, so that using the wrong one requires effort rather than being the default.

Get the payment path off your own card as soon as the operation justifies it. Before that, at least know that it’s the join.

Keep a physical separation if you can. A different machine, or at minimum a different user account on the same machine, so your personal life isn’t one tab away from the working one. Distance defeats convenience, and convenience is what actually breaks this.

The part I got wrong

For about two years I used one password manager for everything. Personal, business, all of it, because it was tidy and I liked having one place.

It was fine. Nothing happened. But when I finally looked at it properly, what I had was a single document listing every account I touched, personal and working, with the relationships between them plainly visible, sitting behind one password.

Nobody broke into it. That’s not the point. The point is that I’d built the exact linking document I was spending real money and effort to prevent anyone else from being able to assemble, and I’d built it for my own convenience, and I hadn’t noticed for two years because it never presented itself as a risk. It presented itself as being organized.

I split it afterward. It’s more annoying now. That’s the correct amount of annoying.

What I cannot tell you

The honest limit: complete separation isn’t achievable for most people, and anyone selling you a version where it is hasn’t run an operation with real overheads.

You will share something. A bank underneath both, a country, a tax number, a machine you use for two purposes at three in the morning because it’s the one in front of you. The goal isn’t zero joins. The goal is knowing which joins exist, so you’re choosing them instead of discovering them.

The exercise I’d actually do, and it takes twenty minutes, is this. Write down your own accounts that you’d genuinely mind losing. Not the working ones. Yours. Then for each one, ask what would have to happen for the fleet to reach it.

Most people find at least one route they’d forgotten. My customer found eleven.

If you want the rest of what keeps a fleet clean, from proxy lines to warm-up to the antidetect setup itself, that’s the work covered on the Multi Account Ops home page.

Get new guides and videos first — join the Telegram channel.