What Are “Linked” or “Related” Accounts?

In Amazon’s terminology, “linked” or “related” accounts are two or more accounts that their system believes belong to the same person or are operated by the same entity. Amazon’s Terms of Service are explicit: each person may only maintain one account. When the system determines that multiple accounts are connected, it treats every account in the chain as a policy violation — regardless of which account was created first or which one is “legitimate.”

The consequences are severe and immediate. When Amazon’s linking engine connects two accounts, both accounts are typically suspended simultaneously. It doesn’t matter if one account is ten years old with a perfect history and the other is brand new — once a link is established, both are compromised. Pending orders are cancelled, gift card balances are frozen, and any seller accounts tied to either profile face immediate review.

What makes this system particularly dangerous is that it operates retroactively. Amazon doesn’t just check for links at account creation — it continuously re-evaluates existing accounts against new data. An account that has been running cleanly for months can be suddenly flagged and linked to another account based on a single overlapping data point that the system didn’t previously have.

Understanding exactly how Amazon establishes these links is essential, because the linking criteria are far more extensive than most people realize. It’s not just about using the same email or the same device — it goes much, much deeper than that.

The 8 Ways Amazon Links Accounts

Amazon’s linking engine doesn’t rely on any single signal. It uses a weighted combination of identifiers, and a strong match on even one or two of these dimensions is often enough to establish a link. Here are the eight primary vectors:

• IP address tracking — Every interaction with Amazon is logged with your public IP address. If two accounts consistently originate from the same IP, the system flags them as related. This is especially problematic for users on shared networks — apartments, university dorms, coworking spaces, and even public Wi-Fi. Amazon doesn’t just check the current IP; it maintains a historical log and can link accounts based on IP overlap that occurred weeks or months ago.
• Device fingerprinting — This is Amazon’s most powerful linking tool. Every device that connects to Amazon is assigned a composite fingerprint based on dozens of hardware and software attributes: canvas rendering output, WebGL renderer strings, installed fonts, screen resolution, timezone, language settings, CPU core count, and more. This fingerprint is effectively unique to your device, and it persists even if you clear cookies, use incognito mode, or switch browsers.
• Cookies and local storage — Amazon plants persistent tracking cookies and writes data to your browser’s local storage. These identifiers survive normal browsing sessions and link any account accessed from the same browser profile. Even if you manually delete cookies, some tracking data is stored in less obvious locations — IndexedDB, service workers, and cached resources that function as supercookies.
• Payment methods — Credit cards, debit cards, and bank accounts are globally unique identifiers. If the same card number has ever been used on two different Amazon accounts — even for a single transaction, even years apart — those accounts are permanently linked. This extends to cards that share the same billing address or the same name. Amazon also cross-references payment processor data, which can link accounts through PayPal or Amazon Pay transactions.
• Physical address — Both billing and shipping addresses are tracked and compared across all accounts. If your delivery address has ever been associated with a banned or suspended account, any new account using that address inherits elevated risk. Amazon normalizes addresses to catch variations — “Apt 4B,” “Apartment 4B,” and “#4B” all resolve to the same location. Even slight formatting differences won’t protect you.
• Phone number — Phone numbers used for account registration, two-factor authentication, or customer service calls are all logged and cross-referenced. A single phone number appearing on two accounts is an instant link. This also extends to phone numbers that Amazon’s system associates with your identity through carrier data or third-party verification services like Persona.
• Email patterns — Beyond exact email matching, Amazon’s system analyzes email address patterns. If your first account uses “john.smith.1990@gmail.com” and your second uses “johnsmith1990@gmail.com,” the system recognizes the similarity. Amazon also tracks email aliases and the “+tag” trick (e.g., “john+amazon@gmail.com”) — these all resolve to the same inbox, and Amazon knows it.
• Browser metadata and behavioral signals — This is the least-discussed but increasingly important vector. Amazon tracks typing patterns, mouse movement characteristics, scroll behavior, the speed at which you navigate between pages, and even the order in which you fill out form fields. Combined with browser-level metadata like user agent strings, HTTP header ordering, and TLS fingerprints, this creates a behavioral profile that can identify you even when all other identifiers have changed.

How Device Fingerprinting Actually Works

Device fingerprinting deserves a deeper explanation because it’s the single most effective linking mechanism Amazon uses, and it’s the one that most people fundamentally misunderstand.

Canvas fingerprinting is the foundation. When you visit Amazon, your browser is instructed to render a hidden graphic — a specific combination of text, shapes, and gradients drawn to an invisible HTML5 canvas element. The way your GPU, operating system, and font rendering engine process this drawing produces a pixel-level output that is nearly unique to your hardware/software combination. Amazon hashes this output and stores it as a persistent identifier. Different devices produce different hashes. The same device produces the same hash every time, regardless of which browser you use or whether you’re in incognito mode.

WebGL fingerprinting goes even deeper. Amazon queries your GPU’s WebGL renderer and vendor strings, supported extensions, and maximum rendering capabilities. These values are hardware-specific and extremely difficult to spoof without introducing detectable inconsistencies. Your NVIDIA RTX 4070 reports differently than an AMD RX 7800 XT, and Amazon maintains a database of expected parameter combinations. If you try to spoof your GPU information but the reported values don’t match the rendering behavior, that inconsistency itself becomes a signal.

Research from the Electronic Frontier Foundation’s Panopticlick project demonstrated that a browser fingerprint drawn from publicly accessible attributes is unique among millions of users in 83.6% of cases. Amazon has access to far more data points than Panopticlick tested, including proprietary JavaScript APIs and first-party behavioral data. Their effective uniqueness rate is significantly higher.

TLS fingerprinting is a newer layer that operates below the browser level. Every time your device establishes an HTTPS connection, it sends a Client Hello message with a specific combination of cipher suites, extensions, and protocol versions. This combination — known as a JA3 or JA4 fingerprint — is characteristic of your operating system, browser version, and network stack. It cannot be changed from within the browser, making it resistant to most anti-fingerprinting tools. Amazon logs these TLS fingerprints and uses them as yet another correlation signal.

The Family Member Trap

One of the most common and frustrating linking scenarios doesn’t involve any intentional evasion at all — it’s the family member and roommate problem.

Consider a household where a spouse, partner, or roommate has had their Amazon account suspended. They share the same home Wi-Fi network, which means the same public IP address. They may have shared a Prime membership, which means overlapping payment methods. The other person in the household has their own legitimate, long-standing account that has nothing to do with the suspension.

It doesn’t matter. Amazon’s linking system treats the shared IP and any overlapping identifiers as evidence of related accounts. The innocent account gets flagged, reviewed, and in many cases suspended alongside the problematic one. When the affected person contacts support, they’re told their account has been “related to an account that violated our policies” — but Amazon won’t tell them which account or what the violation was.

This scenario is particularly devastating for families. A parent’s account getting linked to a teenage child’s account that was suspended for excessive returns. A husband’s seller account getting shut down because his wife disputed a charge on her personal account. Two roommates who have never interacted on Amazon but share an ISP-assigned IP address.

Amazon’s official position is that each household member should maintain their own independent account and that shared resources (like Wi-Fi) are not grounds for linking. In practice, the automated system doesn’t make this distinction. Shared network infrastructure is treated as a linking signal, and the human review process that’s supposed to catch false positives is overwhelmed and inconsistent.

What Happens When Accounts Get Linked

Once Amazon’s system establishes a link between two or more accounts, the consequences cascade rapidly. Here’s the typical sequence of events:

• Simultaneous suspension — All accounts identified in the link chain are suspended at the same time. You’ll receive emails on each account stating that your account has been closed for violating the Terms of Service. No specific reason is given beyond a reference to “related accounts.”
• Order cancellation and fund freeze — Every pending order across all linked accounts is immediately cancelled. Gift card balances, promotional credits, and any Amazon Pay funds are frozen. Refunds for recently returned items may be held rather than processed.
• Seller account shutdown — If any account in the link chain has an active seller account, it faces immediate deactivation. Disbursements are held for up to 90 days, inventory in FBA warehouses may be deemed “abandoned” if not claimed, and your selling privileges are revoked across all Amazon marketplaces globally.
• Permanent identity flag — Your name, addresses, payment methods, phone numbers, and device fingerprints are all added to Amazon’s internal blacklist. Any future account that matches any of these identifiers will be automatically linked and terminated — often within hours of creation.
• Appeal near-impossible — The appeal process for linked-account suspensions has an extremely low success rate. Amazon’s position is that maintaining multiple accounts is a clear policy violation, and their system rarely reverses linking determinations. Even if one account was created innocently, the mere existence of a second account is treated as intentional evasion.

Can You Beat Amazon’s Linking System?

The internet is full of advice about how to operate multiple Amazon accounts without getting linked. Most of it is wrong. Let’s address the most common myths:

“Just use a VPN” — A VPN changes your IP address, which addresses one of eight linking vectors. It does nothing about device fingerprinting, cookies, payment methods, or any of the other signals. Worse, Amazon actively detects VPN traffic. Their system maintains a database of known VPN IP ranges (from providers like NordVPN, ExpressVPN, and Surfshark), and connections from these IPs are automatically flagged as suspicious. Using a VPN doesn’t make you anonymous — it makes you more suspicious.

“Use incognito mode” — Incognito mode prevents cookies from persisting between sessions. That’s it. Your device fingerprint (canvas, WebGL, fonts, screen resolution) is identical in incognito and normal mode. Your IP address is identical. Your TLS fingerprint is identical. Incognito mode provides zero protection against fingerprinting-based linking.

“Switch to a different browser” — Different browsers produce slightly different canvas and WebGL outputs, which modifies one component of your device fingerprint. However, many other fingerprint components — screen resolution, timezone, installed fonts, OS version, hardware specs — remain identical. Amazon’s system correlates these shared components and establishes a high-confidence link despite the browser difference. Additionally, if you log into the second account in the new browser while the first account is still signed in on the old browser, the IP correlation alone is sufficient.

“Clear all cookies and start fresh” — Clearing cookies removes one layer of tracking but doesn’t address local storage, IndexedDB, cached service workers, or any of the supercookie techniques Amazon employs. More importantly, it has zero impact on device fingerprinting, which operates independently of stored data. You could factory-reset your browser entirely and your device fingerprint would be reconstructed on the very next page load.

The most reliable approach for users who need a functional Amazon account after a ban isn’t to try to outsmart the system — it’s to use an aged account that was created on entirely separate infrastructure. An aged account with genuine purchase history was generated on a different device, different network, different payment methods, and different physical address. It carries none of the linking signals associated with your banned account, and its established trust history means it won’t trigger the elevated scrutiny that new accounts face.

Frequently Asked Questions