Restore a Previous Local Profile Backup

If a recent local data change caused a problem and Data backup status shows “Previous backup: Available,” you can queue that backup for restoration before the next launch. Queueing does not change current data immediately. On the next launch, MaskPilot validates the previous encrypted backup before replacing local browser data.

This operation rolls back the complete browser-profile data set. It does not restore only one tab or cookie. Confirm the target profile, backup scope, and sync direction before continuing.

Understand “previous backup” first

Before MaskPilot writes a newer local encrypted backup, it retains the earlier package as a rollback point. “Previous backup” therefore means:

• An earlier encrypted data package for this browser profile on this device.
• One rollback point, not a list of selectable historical dates.
• Not a cloud-version history, recycle-bin entry, or manually exported file.
• It may be unavailable for a new profile or one without enough local backup history.

“Local backup” and “Previous backup” are separate status fields. The restore action appears only when the page reports that a previous backup is available. Each device has its own local backup state; another device does not automatically receive this rollback point.

Queue the restoration

1. Close the target browser profile normally and wait until it is stopped.
2. Open its action menu and select “View backup status.”
3. Expand “Technical details” and confirm that “Previous backup” is “Available.”
4. Record the current local-change and cloud-backup status. If a team uses this profile, coordinate a pause on other devices first.
5. Select “Restore previous backup before next launch.”
6. Read the confirmation and, only if a full profile-data rollback is intended, select “Queue restore.”
7. Wait for “Queued: the previous backup will be restored before the next launch,” then launch the profile.

A running or starting profile cannot queue a restoration. The queued state is not a preview, and the current page does not provide a cancel action. If you selected the wrong profile or changed your decision, do not launch it again; contact support first.

Mozilla’s profile-backup guidance likewise requires the browser to be closed before replacing a complete browser profile. MaskPilot performs the replacement before the next launch, so do not manually copy, delete, or overwrite the profile-data directory at the same time.

What happens on the next launch

The launch flow reads and decrypts the previous backup, then fully prepares it in a temporary location. It replaces current local browser data only after the backup is valid and ready. After a successful restoration:

• The queued state clears and the profile launches with the earlier data.
• Cookies, history, site storage, extension data, and other browser content return to their state when that backup was created.
• The restored data becomes a new local change.
• If uploads are allowed and the cloud version has not changed independently, the restored result is used to update the cloud backup.

When “Do not sync profile data” is enabled on this device, the restored result remains local and is not uploaded. Before allowing uploads again, confirm that this is the version you intend to continue with. See profile-data sync and recovery for the full boundary.

Will a failed restoration remove current data?

If the backup cannot be read, decrypted, extracted, or safely installed, MaskPilot retains current local data and keeps the restoration pending instead of treating incomplete content as successful. That launch stops so you do not continue in an invalid data set.

Do not delete local data, repeatedly switch devices, or manually overwrite directories after a failure. Record the profile name, restoration time, and complete message, then use remote recovery failure and local-data protection or contact support. If another device has independently updated the cloud version, resolve that conflict before attempting to continue from older data.

What to verify after restoration

Perform a small validation before resuming important work:

1. Check whether required bookmarks, tabs, extension settings, and site data match the expected earlier state.
2. Visit a non-sensitive test website and confirm that browser data can be read and written normally.
3. Check sign-in state on important websites. Sessions in an older backup may have expired or been revoked by the website.
4. Review the proxy, fingerprint, and extension assignments. These profile settings are outside the local browser-data rollback, but they should still match the intended use.
5. After confirming this is the version to keep, close the profile normally and review backup status again.

Restoring older browser data cannot guarantee that a website will accept an older authenticated session. MDN’s session-management guidance explains that websites can set session lifetimes and revoke sessions on the server. If some or all websites request a new sign-in, follow the website sign-in-state checklist instead of repeatedly restoring the same backup.

If the entire MaskPilot browser profile was deleted, use the profile recycle-bin recovery flow instead of the previous local backup.