How platforms link accounts you thought were separate
Two accounts, two fingerprints, two proxies, both actioned within a day of each other. The operator did the fingerprint work correctly. That is exactly the case this post is for: the fingerprint was never the thing that connected them.
We covered account linkage as one item in a longer list in why accounts get flagged. This is the depth version. Platforms do not need a single smoking gun; they score a cluster of weak signals across several independent families, and any one family lighting up is often enough on its own.
Device and fingerprint reuse
The most obvious family, and the one tooling in this category actually addresses. Shared canvas hashes, shared WebGL renderer strings, shared font lists, shared audio fingerprints, or simply the same physical device driving multiple browser instances back to back. This is the layer a coherent, isolated, persistent fingerprint per profile is built to solve.
It is also the only family a browser can solve. Keep that in mind as you read the rest.
Network: IP, ASN, and the login nobody thought to hide
Shared IP is the obvious one. Shared ASN, meaning the same hosting provider or the same residential proxy pool, is a weaker but still useful signal when accounts repeatedly show up on address ranges nobody else uses.
The signal operators miss most often is earlier: the first login. Accounts get created, tested, and logged into once from a home connection before the proxy and the profile are ever set up. That single early session, often forgotten within a week, sits in the platform's history forever and links every account that later shares nothing else. Auditing linkage risk means auditing account history from day one, not from the day the tooling was configured.
Payment instruments and billing addresses
Card numbers, tokenized payment identifiers, billing names, and billing addresses are some of the most durable links available to a platform, because payment processors themselves share fraud and duplication signals across merchants. A payment method reused across accounts links them regardless of what the browser or the network looks like, and a billing address is a link even when the card number differs.
Recovery email and phone patterns
Shared recovery email, shared recovery email domain, or emails generated from an obvious pattern (sequential numbers, the same generator, one inbox forwarding to another). Phone numbers from the same short-lived virtual number pool, or the same number reused for verification across accounts, work the same way. Platforms do not need the addresses to match exactly; a recognizable pattern across a batch is enough to cluster them.
Behavioural timing
Accounts created in a batch, minutes apart, in the same order every time, then used in that same order on subsequent days, are a timing fingerprint independent of anything technical. A human managing five accounts does not touch them in identical sequence at the identical hour day after day. Scheduling and automation convenience is exactly what produces this pattern, which is why it shows up disproportionately in accounts that are otherwise well isolated on every other axis.
Content and asset reuse
The same profile photo, the same bio text, the same uploaded image, the same product description, reused or lightly edited across accounts. Perceptual hashing catches near-duplicates, not just exact files, so cropping or recompressing an image does not defeat it.
Social graph overlap
Accounts that follow the same small set of other accounts, in the same order, or that message or connect with each other, hand the platform a graph edge directly. This one requires no inference at all; the accounts are telling the platform they are related.
Fingerprint isolation solves exactly one of these
Of the seven families above, a coherent per-profile fingerprint addresses device and fingerprint reuse. It does nothing for network history, nothing for payment and billing, nothing for recovery identifiers, nothing for timing, nothing for content, nothing for the social graph. Buying a better browser while every account recovers to the same email address changes exactly nothing about six of the seven signal families that link them.
This is also where a free answer beats a purchase. Separating recovery emails and phone numbers, using distinct payment methods, varying creation and usage timing, and avoiding shared assets cost nothing and are entirely process, not tooling. No product in this category sells discipline, and no product should claim to.
Checking your own setup
Go through the account history, not just the current session: where was each account first accessed from, what recovery details does it carry, what payment method is attached, and does its usage pattern look identical to its siblings. If you manage several identities for clients rather than yourself, the operational side of keeping this separate at scale is covered in managing client accounts as an agency.
None of this applies to an account you are not authorized to operate on someone else's behalf; that is a separate problem this post is not addressing.
Try it on the free tier.
Unlimited local profiles, no credit card. Check it against the detectors yourself.