Profile Sync, Backup, and Recovery

When uploads are allowed on the current device, MaskPilot prepares and encrypts local profile data after shutdown, then uploads an encrypted package that the same account can restore on another device. Normal shutdown, completed sync, and avoiding concurrent sessions keep versions easier to understand.

Understand sync direction

“Do not sync profile data” is enabled by default to prevent an unexpected upload after an upgrade or a damaged local setting. While it remains enabled, the current device does not upload local changes but can still retrieve existing remote data; edits that have not uploaded remain on the device. Confirm which copy should continue before allowing uploads.

Restore on another device

Sign in with the same primary account or a member account that is still assigned the profile. Data is restored as needed during launch. Multiple devices can run the profile, but uploads check their cloud baseline and reject conflicting old copies; cookies, cache, and other browser data are not automatically merged. Prefer closing the original session and confirming that needed data uploaded before switching devices, rather than waiting for a runtime lock to clear.

Preserve local data after a failed sync

When usable profile data already exists on the device, a failed remote read, download, validation, or restore does not replace it with incomplete content. The local copy remains available, but its latest changes may still be waiting to upload. Use the failed sync and local data checklist before retrying on another device or removing the local copy.

Handle deletion and client maintenance

After an accidental deletion from the MaskPilot profile list, the original primary account can restore an item that remains in “Account recycle bin”; the current view does not promise a fixed retention period. Deletion preserves the association with existing encrypted cloud data but does not upload local changes that were never synced; data that exists only on the original device should be recovered there first. Check plan capacity, the proxy route, extensions, and team assignments after recovery. Before a client update, review the version details; if download or verification fails, keep the working client and do not run an unverified installer.