How Accounts Get Linked and the Habits That Prevent It
Shared cookies, matching device values, one address, and reused recovery details. The practical checklist for keeping separate accounts genuinely separate.
Accounts get associated with each other through evidence, and the evidence is more mundane than most people assume. Almost all of it falls into four buckets.
1. Shared browser state
The largest and easiest to fix. Two accounts used in one browser share a cookie jar, Local Storage and IndexedDB. A site that sets an identifier while you use one account reads that same identifier while you use the other, and no amount of care about anything else undoes it.
The fix is a separate browser directory per account. A separate window will not do it, and neither will a private window. The directory has to persist.
2. Identical device values
Two accounts reporting the same screen size, the same fonts, the same graphics adapter strings and the same canvas hash are two accounts on one machine, because that is exactly what they are.
The fix is a distinct and internally coherent identity per profile. The values are generated as a set so they cannot contradict each other, and stored so the profile reports the same device on every open.
3. One network address
Accounts that always appear from the same address are trivially grouped. The fix is a proxy per profile, with a sticky address rather than a rotating one, and a timezone and locale that agree with where that address is.
4. Reused details
The bucket no browser can help with, and the one that catches experienced teams.
- The same recovery email or phone number across accounts.
- The same payment instrument or payout destination.
- Identical profile text, images or handles, reused verbatim.
- A rhythm of activity that is obviously one person working through a list.
The working checklist
- One profile per account. Never two accounts in one profile.
- Assign the network route before the first sign-in rather than after. The first session is the one that establishes the account's normal.
- Match timezone and locale to the route's country.
- Keep recovery details, payment instruments and identifying text distinct per account.
- Let each profile's identity stay put. Regenerating it is a change of device from the site's point of view.
- Close a profile when you are finished with it, so its state is written out cleanly.
- Warm a new account like a person would. Volume on day one is its own signal.
Where tooling helps
Most of the list above is discipline rather than software. What software removes is the part where discipline fails: the moment somebody opens the wrong account in the wrong window because switching properly was tedious.
PowerOps makes the correct action the convenient one. Profiles are numbered and searchable, so anyone can quote one out loud. Groups and folders keep a client's profiles together. A profile opens from its own row with its identity and its route already attached. No step is left where you have to remember to set something.
One caveat worth stating plainly: none of this grants permission. If a service's terms prohibit holding several accounts, isolating them does not change that. Keep environments separate for the work you are entitled to do.
Try it on your own machine
PowerOps runs the profiles described here. Every one of them keeps its own browser directory, device identity and network route, all from one desktop application.
Download for Windows