How Hidemyacc Isolates Profiles
Each profile is a full browser environment with its own fingerprint, cookies, cache, and local storage. A website reads it as a separate device rather than a second tab on the same computer. You set screen resolution, device memory, fonts, audio stack, WebGL, and language per profile, and templates let new profiles inherit those settings.
Version 3.0 ships two browser cores, Marco and Ghosty, and both are built on Chromium. Marco can present itself as Chrome, Opera, Brave, Edge, or Yandex, but the engine underneath does not change, so treat those as user agent variants rather than five separate browsers. Foxy, the older Firefox core, was pulled from 3.0 because its base had aged badly and detection scripts caught it more often. Reviews that still list a Firefox option are describing 2.0.
WebRTC deserves separate attention. The RTCPeerConnection API can leak your real address through ICE candidate gathering even when every HTTP request goes through a proxy. Hidemyacc lets you disable WebRTC or bind it to the proxy IP, and binding is usually safer, since a browser with no WebRTC stack at all is itself an unusual signal.
Mobile Emulation
Several published reviews state that Hidemyacc has no mobile OS emulation, then contradict themselves a few paragraphs earlier by listing mobile fingerprinting as a plan feature. The profile creation endpoints accept ios and android alongside win, mac, and lin, and Marco profiles take a device model field for tablet hardware. That matters because a desktop fingerprint sitting on a mobile carrier IP is exactly the contradiction detection systems look for.
Also Read: Plug Proxyon Into Multilogin
Proxies and Automation in Hidemyacc
Assigning a Proxy to Each Profile
Every profile takes its own proxy, entered manually or pulled from the built in proxy manager, which supports HTTP, SOCKS4, and SOCKS5 and shows status per entry. One proxy per profile is the rule. Sharing an IP across profiles undoes the fingerprint work entirely.
Pick the type by how much trust the target demands. Residential proxies route through real home connections and carry the ISP metadata consumer platforms expect. ISP proxies give you a static address on datacenter infrastructure registered to a consumer ISP, which suits long lived logins where the IP should not change between sessions.
Then align the profile with the exit node. Timezone, geolocation, and browser language have to match the country the IP resolves to. A Warsaw IP with an America/New_York timezone is a clean signal that something is being spoofed. Check the result against a fingerprint tool like BrowserLeaks before you log anything in, which surfaces WebRTC leaks and timezone mismatches in one pass.
Driving Profiles From the Local API
The desktop app exposes a local HTTP API on 127.0.0.1 port 2268 while it is running. That is the piece most reviews skip, and the part that matters if you are scripting. You create, update, and start profiles programmatically, and the start call returns a debugging port for Puppeteer or Selenium.
import requests
resp = requests.post(
"http://127.0.0.1:2268/profiles",
json={
"os": "win",
"name": "store-01",
"browserSource": "marco",
"proxy": '{"mode":"http","host":"proxy.example.net","port":8080,"username":"user","password":"pass"}',
},
)
print(resp.json())The proxy field is passed as a JSON encoded string rather than a nested object, which trips people up on the first call. API access is gated to the higher plans, so confirm that before building a pipeline around it. There is also a visual macro recorder and a synchronizer that mirrors actions from one profile across the rest.
Also Read: Sticky Sessions vs Rotating Proxies
FAQ Section
Is Hidemyacc a VPN?
No. A VPN changes your IP and leaves your fingerprint untouched, so every account still reports the same canvas hash and font list. Hidemyacc changes the fingerprint and expects you to supply the IP separately.
Does it include proxies?
Free proxies are bundled on the mid tier plans and above, but they are shared and not suitable for anything sensitive. Most users bring their own.
Which core should I pick, Marco or Ghosty?
Marco is the newer of the two and gets the more frequent fingerprint algorithm updates. Ghosty is still maintained and supports the same operating system list. Start with Marco unless a specific target behaves better under Ghosty.
Do profiles run in the cloud?
No. Profiles execute locally, so your hardware sets the ceiling on how many run at once. Profile data syncs to the account, but the browser itself is local.
Can I move profiles from another antidetect browser?
Cookies import from txt or json files, so sessions transfer. Fingerprints do not transfer cleanly between vendors, and a warmed account landing on a brand new fingerprint often triggers a verification loop.
Final Thoughts
Hidemyacc is a reasonable pick when you need isolated profiles on your own hardware and you already have a proxy source you trust. The fingerprint controls are deep and the local API is genuinely usable, but the tool only handles half the problem. Whatever the browser does with canvas and WebGL, the IP behind it still decides whether the session survives. Pair it with clean proxies and take the plan tier that unlocks API access if you intend to script anything.
