Restore through a linked account
Before recovery
You need an existing Sigma account, a previously linked provider account, a cloud backup uploaded for the intended BAP identity, and its local decryption factor. Provider availability depends on the deployment's configured credentials.
A social callback is sign-in-only unless an explicit signup flow requests account creation. Recovery must not silently create a new account when no existing link is found.
Recovery steps
- Open Restore and select the linked provider offered by the UI.
- Complete the provider's login and return to Sigma. This proves control of that provider account and establishes the appropriate account session.
- Sigma checks the linked provider account and recovery mapping before returning the encrypted backup.
- Enter the backup password locally, or use an available enrolled decryption method. Review the restored identity and sign in with its key.
- Keep an offline encrypted export after confirming the identity is correct.
The provider does not return your Bitcoin key or backup password. Resetting the provider's password or Sigma account password does not reset backup encryption.
Retrieval authorization
GET /api/backup?oauthId=provider|accountId is not a public backup lookup. It requires a Sigma session that owns the linked provider account and mapped identity. Supplying someone else's provider ID is not sufficient. Use the first-party restore flow instead of collecting provider credentials in your app.
Troubleshooting
A missing link, wrong provider account, absent upload, or conflicting recovery mapping can prevent retrieval. Check the selected identity and backup status. A decryption failure can indicate the wrong password or unsupported/corrupt file; do not overwrite the current backup to “repair” it.
Linking a new provider does not prove that a usable backup exists. Confirm both linkage and upload before relying on social recovery. Removing a provider link does not erase offline copies or public profile declarations.