Every profile already keeps its own cookies, storage, cache, extensions and logins. Fingerprint protection goes one step further for privacy: it limits what websites and tracking networks can measure about your device to follow you across your profiles.
Websites can recognise a device from the details a browser reveals: how it draws an image, which graphics card it reports, how it processes audio, which fonts it has, its screen size, its browser identity, its time zone and language. Fingerprint protection gives a profile its own consistent set of those details.
The device profile is derived from the profile itself, so it stays the same across restarts and every page in that profile sees the same machine. A different profile gets a different one.
Open the profile manager, then either right-click a profile and choose Fingerprint, or use the fingerprint button on the profile's row. In the Fingerprint Protection window, tick Enable fingerprint protection and pick a level.
Whenever you turn it on in the app, MetaDock shows a short notice about what it does and its limits. Basic per-profile device emulation stays available either way.
The window is split into Overview, Hardware, Canvas & Audio, Identity and Location.
Yes, from the Location section. Choose a source:
Yes, on MetaDock Pro. The same settings are reachable over REST, WebSocket, WebDriver and MCP: get, set and clear a browser's fingerprint configuration, set canvas, WebGL and audio separately, list the named graphics cards, and set or clear location. Claude, Cursor or the built-in AI assistant can use them like any other MCP tool.