Sync and recover browser profile data

When profile uploads are allowed on the current device, MaskPilot prepares and encrypts data locally after shutdown, then uploads an encrypted package. The server keeps existing encrypted content so the same account, or a team member who is still assigned the profile, can restore it on another device. “Do not sync profile data” is enabled by default; while it remains enabled, local changes are not uploaded.

Complete a normal sync

1. Finish the work inside the browser.
2. Close the browser window normally.
3. Confirm that the current device allows uploads and check the sync result. A closed status alone does not prove that the upload succeeded.
4. Then exit the client or turn off the device.

Force-quitting the client or losing power can prevent the latest changes from completing the normal sync flow.

Recover on another device

1. Install MaskPilot and sign in with the same primary account, or with a team account that is still assigned the profile.
2. Find the profile in the list.
3. Prefer closing the original session normally and confirming that needed changes uploaded. This reduces version conflicts; it is not a cross-device launch restriction.
4. Launch it. The client downloads and restores encrypted data when necessary.

A profile can run on multiple devices; the client still prevents duplicate local launches. Uploads check the cloud data version and reject conflicting old copies, but do not automatically merge changes from multiple devices. There is no runtime lease expiry to wait for.

Recover an accidentally deleted profile

After deletion from the MaskPilot profile list, the primary account can open “Account recycle bin” and restore an item that remains listed. The current view does not promise a fixed retention period, so act promptly after an accidental deletion. Deletion preserves the association with existing encrypted cloud data but does not upload local changes that were never synced.

Before recovery, check that:

• You are signed in with the original primary account and the plan has room for the restored profile.
• The original entry proxy and its complete upstream route still exist and are not assigned to another profile.
• The original browser version, proxy, and extensions remain available.
• Data needed on another device previously completed an upload. Otherwise, preserve the local profile directory and recover on the original device first.

After recovery, launch the profile once and verify the session, proxy, and extensions before continuing normal work. If a team member requested a deletion that the primary account approved, review the member assignments again. For conflict handling, see recover a deleted browser profile.

When versions conflict or sync does not finish

Keep the client running and check the connection. When versions conflict, preserve the local data on each device and decide which copy should continue. Do not delete local directories or repeatedly upload in an attempt to overwrite the other copy. Network problems no longer close an already started browser because renewal failed, but launch, sign-in, and sync still need a connection. If you cannot identify the right version or retries keep failing, record the message, time, and profile name before contacting support.