Frequently Asked Questions

We don’t promise they won’t. Nobody can; read the reviews of anyone who says otherwise. What we promise is that every profile reports one coherent device, that every build is published with its hash, and that when something leaks we say so in the changelog before you find out. What you do with the accounts is your responsibility, and our acceptable-use policy says what we won’t support.

Running multiple accounts is legal in general. Some platforms’ terms restrict it, and some uses — fraud, evading sanctions, anything the acceptable-use policy names — are illegal everywhere and we don’t support them. Read the policy before you buy.

Yes. Ten profiles, the full fingerprint engine, unmetered proxies, the local API and MCP. No card, no trial timer.

Profiles run on your computer instead of a rented cloud VM, and we don’t resell proxy traffic. Remove those two costs and this is what’s left.

Yes, on every plan. A local REST API and a CDP endpoint per profile, from Node, Python or bash, or from an AI agent over MCP.

An antidetect browser is specialized software that creates separate, isolated browser profiles. Each profile presents a unique, internally coherent hardware signature (Canvas hash, WebGL shader responses, AudioContext curves, font lists, and screen metrics) and a dedicated proxy IP. This prevents anti-fraud algorithms on platforms like Amazon, Meta, Google, and TikTok from correlating multiple accounts back to the same physical computer.

Chrome profiles and Incognito mode only separate cookies and browsing history. They do not change your hardware fingerprint — every tab still exposes the identical GPU renderer, audio curve, installed fonts, and public IP address. To fraud systems, that represents one device attempting to run multiple accounts, which is a common trigger for account linking and review. XDLogin spoofs the underlying hardware fingerprint for every profile individually.

Windows and Linux builds are stable. macOS is a beta: the build is unsigned, so you clear the quarantine flag once, and it needs Chrome, Edge or Brave installed. Android is a separate native beta app with its own per-profile WebView engine, sideloaded as an APK. Details and checksums are on the download page.

On Windows, Linux and macOS, profiles launch as real Google Chrome, Edge, Brave or Chromium processes, so one of those needs to be installed; XDLogin picks it up automatically. If none is found, the built-in engine takes over. The Android app brings its own engine.

Yes. Your plan follows your account, so sign in on any machine. Profiles themselves are files on each machine’s disk: carry them across with JSON backups, or turn on end-to-end-encrypted cloud sync on Pro and above.

Yes. Paid plans are billed per period and can be cancelled anytime from your account dashboard — you keep access until the end of the paid period. The Free tier (10 profiles) needs no card and never expires.

Paid plans are billed immediately and renew until cancelled. If you are not happy within 7 days of your first payment, email support@xdlogin.com for a full refund. You can cancel any time from your account page and keep access until the end of the paid period.

Yes. Checkout offers card payment through Dodo Payments, our merchant of record, or cryptocurrency through NOWPayments. Both activate the plan on your account automatically.

Seat counts are part of every paid plan and the account server already enforces them. Server-side invitations and profile sharing between teammates are rolling out in a coming release; the Team panel in the current desktop build is local to your machine. Everywhere on this site we label the feature as rolling out rather than selling it as finished.

No. You can use any third-party HTTP, HTTPS, or SOCKS5 proxy provider (Bright Data, Oxylabs, Smartproxy, Webshare, IPRoyal, etc.). XDLogin never meters your proxy bandwidth or charges traffic fees.

XDLogin includes built-in WebRTC leak protection that automatically matches WebRTC candidate IPs to your proxy exit IP, or disables STUN requests altogether so your true residential IP is never exposed behind the proxy.

All profile cookies, localStorage, and cache files are stored locally on your disk in an isolated per-profile store. Nothing is uploaded unless you explicitly enable Pro's end-to-end-encrypted cloud sync — and then servers only ever hold ciphertext your devices encrypted.

Yes. The desktop app includes an MCP server, off by default, listening on 127.0.0.1:8931 with an optional API key. Any MCP-capable agent can list, create, launch and stop profiles, navigate and screenshot pages, test proxies and move cookies. It is available on every plan; see the docs.

Cloud sync is end-to-end encrypted with a passphrase that never leaves your devices, so we cannot reset it or read your data. Your local profiles are unaffected; only the encrypted cloud copy becomes unreadable. Keep the passphrase somewhere safe and take JSON backups.