What Does a Browser Profile Copy Keep?

Copying a MaskPilot browser profile creates a new independent environment. The group, browser version, notes, tags, and core fingerprint settings are retained, as are profile-level extension choices. The proxy, cookies, website sign-in state, and other browser data are not copied. The copy receives a new profile ID, identity seed, and encryption key, and it starts in the stopped state.

Copy scope at a glance

Item	Retained?	What happens
Name, group, browser version, and notes	Yes	“(copy)” is appended to the name; you can rename it independently
Core fingerprint settings	Yes	Timezone, language, hardware, and related settings are copied, but a new identity seed is generated
Tags	Yes	The copy keeps the source tags for organization and tag-scoped rules
Profile-level extension choices	Yes	Store-extension overrides are copied; local-extension choices are handled separately on this device
Entry proxy	No	Select and test a proxy for the copy’s intended use
Cookies and website sign-in state	No	The first launch does not inherit authenticated sessions from the source
History, cache, passwords, autofill, and site storage	No	The source browser-data directory and extension site data are not copied
Cloud data package and sync state	No	A copy is not a sync branch and does not inherit the source package or runtime state

Browsers do not all define “copy” in the same way. For example, Firefox documentation says its profile copy includes settings and browsing data. MaskPilot copies only the configuration intended for building a new environment. Do not infer that cookies or sign-in state move just because another browser uses the same button label.

Copy from a signed-out baseline

The safest source is a baseline profile that has never signed in to a business website:

1. Set the browser version, language, resolution, and other fingerprint values that should remain stable.
2. Select only the required extensions, without storing business accounts, wallets, tokens, or other identity data inside them.
3. Validate launch and shutdown on a non-sensitive test website.
4. Copy the baseline, rename the copy, and review its tags.
5. Assign a proxy to the copy, then recheck timezone, geolocation, language, WebRTC, and other related settings.
6. Launch the copy and sign in to the target website independently.

A setting does not have to contain a secret to be wrong for a new profile. When the proxy region changes, timezone, geolocation, and language should still match the new scenario. Treat copied configuration as a starting point, not as a substitute for review.

Why sign-in state is excluded

Cookies, Local Storage, IndexedDB, cache, passwords, autofill, and extension storage can all carry website identity. Duplicating them into a new profile would share access state with the source and undermine the isolation boundary of the new environment.

Chrome’s profile guidance likewise describes history, passwords, and other information as data kept separate between browser profiles. MaskPilot therefore does not use profile copying to migrate that data. To continue with the same profile’s browser data on another device, use profile-data sync and recovery instead of creating a copy.

If local extensions show a copy warning

Profile-level choices for store extensions are retained. Locally imported extension files exist only on the current device. The client attempts to apply their profile-level choices to the copy on this device, but it asks you to select them again if that step fails.

The warning does not mean profile creation failed. Open the new profile, confirm that the extension still exists on this device by following the local-extension import and update guide, and select it for the copy again. On another device, import the local extension there first. Extension sign-in or site data is never transferred by profile copying.

Choose copy, share, or sync

Goal	Use this feature
Reuse a clean configuration under the current account	Copy the profile, then assign a proxy and sign in independently
Give copyable configuration to another MaskPilot account	One-time profile sharing
Continue the same profile’s browser data on another device	Sync and recovery, not a copy

Before first launch, review the new name, proxy, related fingerprint values, and extensions. Do not manually duplicate browser-data directories or treat the source and copy as two versions that will merge later.