Skip to content

Documentation

Signing in on another device

Set up signing only on browsers you trust, and keep a recovery route before removing local data.

Pairing this browser

In a trusted Parable browser that still holds your identity’s recovery material, open Settings → Devices → Start pairing, select Ma’atara Provenance and create a secure invitation. A browser with only a product device key cannot send this recovery handoff.

Scan the invitation QR code on the receiving device, or open the full invitation link in the receiving browser. MP’s /pair page receives invitations; it does not create them. Keep both browsers open, compare the displayed fingerprints and approve on the sending browser only if they agree. Cancel if they differ. Pairing transfers encrypted recovery material so the receiving browser can use the same identity.

The relay carries encrypted material, but both browsers and the pairing invitation must remain trustworthy. Do not share the invitation or pair a public device.

Device authorization availability

The separate “Authorise this browser” flow is release-gated and disabled by default in MP. Its presence in the code does not mean per-device authorization or revocation is available in the public beta. Follow the flow actually offered by your build.

A lost or compromised browser

A paired browser can sign as you when unlocked. Do not assume deleting a device entry revokes a copied identity key. Use the identity portal’s recovery and security guidance to assess rotation and recovery; do not erase your remaining working browser first.

Previously signed records remain evidence of earlier signatures. Revoking future access does not remove public records or recover source files.

← All documentation