Multi-account · Safety
Zero IP-linkage risk when you manage multiple Amazon accounts
If you run more than one Amazon seller account — second brand, a family member’s store, a market you tested and kept — the single question that keeps you up at night is: “Can Amazon link them?” This page explains, in the plain language of what actually happens on the wire, why AIAdKing does not create that risk.
Last updated: July 14, 2026
The short answer
AIAdKing never puts your IP in front of Amazon as the seller.
Every request that reaches Amazon is signed with a seller-specific OAuth token you granted, from AIAdKing’s own server IPs, over Amazon’s official Selling Partner API and Advertising API endpoints. Your home or office IP is not part of that request. Neither is your browser, your device, or your session cookies. Two accounts you manage never share any network signal that Amazon can join on.
How it works
Three things that separate us from the risky alternatives
Amazon’s multi-account detection watches for shared browser fingerprints, shared cookies, and shared IP addresses across Seller Central logins. Anything that automates by driving a real browser session is exposed to all three. AIAdKing uses none of them.
OAuth — not passwords
You grant AIAdKing a Login with Amazon (LWA) refresh token. Every API call is signed with that token, scoped to that seller account only. We never receive, store, or type your Seller Central password.
Server-to-server API calls
Every request originates from AIAdKing’s server IPs, using Amazon’s official Selling Partner API and Advertising API endpoints. There is no headless browser, no scraper, no automation on your machine. Nothing runs from your IP address.
One tenant per account, isolated
Each Amazon account you connect is a separate tenancy in our database. Refresh tokens are AES-256 encrypted per-row. We never send data from one of your accounts alongside a request to another; nothing on our side introduces a joinable signal.
Compared to browser-based tools
Where the actual risk comes from
Multi-account “automation” tools that install a Chrome extension, drive a headless browser on your desktop, or scrape Seller Central all share one property: the request Amazon receives comes from your machine, wearing your IP + your device fingerprint. That’s exactly what Amazon looks for.
| Signal Amazon sees | Browser-based tools | AIAdKing (SP-API + Ads API) |
|---|---|---|
| Client IP address | Your IP | Our server IPs |
| Browser cookies & session | Your Seller Central session | None — no browser used |
| Device / canvas fingerprint | Your device | None — no device used |
| Authentication method | Your Amazon password (typed by the tool) | Scoped OAuth token (LWA) |
| API endpoint used | sellercentral.amazon.* HTML pages | Official SP-API & Ads API |
| Compliant with Amazon’s ToS | Grey area (scraping / automation) | Yes — on the approved API |
Common questions
What sellers actually ask us
If I connect two accounts from the same laptop, can Amazon see that both used my IP to grant the OAuth?
The OAuth grant flow runs in your browser on the LWA consent screen — that’s a normal Amazon login you would do anyway. What matters after that is where every subsequent API call originates. All of ours originate from our server IPs, not yours. Amazon does not correlate an OAuth grant with later API traffic to infer account linkage.
Do the two accounts I connect share anything on your side that Amazon could see?
No. Each account gets its own tenancy, its own encrypted refresh token, its own request queue. Nothing is co-mingled at the request layer. Amazon receives entirely independent SP-API and Ads API calls, each signed with the token of that account only.
What about the seller name, email or business address? Wouldn’t Amazon see those match on my side?
Amazon already has that data — you gave it to them at signup. AIAdKing doesn’t create a new signal by connecting; we just make the two accounts easier for you to run. If two accounts share a legal person or address, that’s an Amazon Multiple Account Policy question you should have permission for regardless. AIAdKing helps you operate the accounts you are already allowed to have; it doesn’t change what Amazon knows about you.
Do you keep logs that connect my two accounts to each other?
We log per-account API calls for auditability (rate-limit tracing, incident response, Amazon’s own AI Agent Policy audit requirement). Those logs live in our systems only; Amazon never sees them. Nothing in the log format joins one account to another beyond “these two are owned by the same AIAdKing user”, which is your organisational relationship, not an Amazon signal.
What if AIAdKing’s server IPs get flagged by Amazon someday?
Amazon’s SP-API and Ads API endpoints are designed for high-volume server-to-server traffic. Every third party building on the API sends from their own server pool; that’s the intended pattern. Rate limits are enforced at the token level, not at the IP level.
Is this different from “using a VPN” to hide my IP?
Yes — and better. A VPN just changes which IP shows up; the browser and device fingerprint still leak, cookies still tie sessions together, and Amazon actively pattern-matches VPN exit nodes. AIAdKing does not present a browser session at all: there is nothing for Amazon to fingerprint.
Guarantees
What AIAdKing does not do
These are the things a browser-automation tool would need in order to be useful, and that we have deliberately never built:
- No browser extension. We do not install anything in your browser that can read Seller Central pages or cookies.
- No headless browser on our servers. We do not spin up Chromium or Puppeteer against sellercentral.amazon.* — only the official APIs.
- No scraping of Amazon HTML. Everything we read comes back as JSON from the Selling Partner or Advertising API.
- No storing your Amazon password. We use OAuth; we never see it.
- No cross-account co-mingling. Every request is signed with exactly one seller’s token.
- No selling of your data. Your seller information is never sold, licensed, or shared for advertising.
Manage all your Amazon accounts — safely.
Connect each seller account once via Amazon’s official OAuth. AIAdKing handles the rest over the approved APIs, from our servers, with no linkage back to you.
Have a specific compliance question? Contact us — we’re happy to explain the wire-level details.