Recover a deleted browser profile

If you used “Move to recycle bin” from the MaskPilot profile list, the profile is usually recoverable. Sign in with the original primary account and open the account recycle bin. You can attempt recovery while the item remains listed. MaskPilot does not currently promise a fixed retention period in this view, so act promptly after an accidental deletion.

This is different from deleting a browser-native profile. The official Chrome guidance warns that removing a native profile erases its bookmarks, history, passwords, and other settings from that computer. Do not use native browser deletion or manual user-data directory changes as a substitute for the MaskPilot recycle bin.

What deletion preserves

A profile must be stopped before it can move to the recycle bin. MaskPilot saves a recovery snapshot of its name, group, browser version, fingerprint, tags, entry proxy, and extension selections, and preserves the association with any encrypted cloud data that already exists.

Deletion does not trigger an extra sync upload. If “Do not sync profile data” is enabled, or an unexpected exit left recent changes unuploaded, another device cannot reconstruct those changes from the cloud. However, deletion itself does not remove the local profile directory on the original device, and recovery reuses the original profile identity, so the latest local data may still be present there. Do not uninstall the client, clear its data directory, or remove files from the original device before recovery.

Recovery steps

1. Sign in to MaskPilot with the original primary account.
2. Open “Recycle bin” from the profiles page. Team members cannot view or restore the primary account’s recycle-bin contents.
3. Use the profile name, deletion time, and notes to identify the item, then select “Restore.”
4. Return to the profile list and review its group, browser version, fingerprint, tags, proxy, and extensions.
5. With no process or operation active for this profile on the current device, launch it once and check the required sign-in state and browsing data. Coordinate data versions if others are still editing it.
6. If a team member requested the deletion and the primary account approved it, review member assignments after recovery. That deletion path may have removed the earlier assignments.

If recovery fails

• The plan is at its profile limit: Resolve the current profile count before retrying recovery.
• The original proxy route is now in use: Recovery checks the entry proxy and its complete current upstream route. If any node is assigned to another profile, change that assignment instead of repeatedly clicking restore.
• The original proxy route no longer exists: If the entry proxy or an upstream node was deleted, the current client cannot complete recovery. Creating a new proxy with the same name does not recreate the original record identity. Keep the error and contact support.
• The original profile identity conflicts: In rare cases, the original profile identifier already exists, so recovery is rejected rather than overwriting current data.
• A restored resource is unavailable: After successful recovery, replace a browser version or store extension that was retired or removed. Local extension files are device-specific and are not copied when the profile is recovered on another device.
• The profile still appears in use: Recovery no longer waits for earlier runtime permission to expire. Distinguish a local process, an old-client message, and the latest run record with the profile in use checklist. Do not delete local directories or lock files.

Do not rush to create a replacement and reuse the original proxy, because that can create a recovery conflict. Matching names do not mean two profiles contain the same data.

If the profile is not in the recycle bin

Confirm that you are signed in with the original primary account and that the item was not already restored. The account recycle bin covers deletions initiated from the MaskPilot profile list. It cannot recover a deleted website account or browser-native profile. If data was never uploaded, preserve and use the original device first; another device cannot obtain changes that exist only there.

If the cause remains unclear, record the profile name, deletion time, deleting operator, and original page message before contacting support. Keep website passwords, proxy credentials, and other secrets out of screenshots and logs. For the device upload boundary, continue with disable profile data sync on one device.