Your keys stay with you.
Know what you share.

This browser opens your LifeHash.

Saved private custody is encrypted in this browser. The browser holds the key and opens it automatically: there is no LifeHash password lock.

Use a browser profile you trust. Someone who can use that profile may be able to open your LifeHash. Clearing its site data can erase your saved identity and evidence.

Account verification uses account information.

Google, GitHub, and email verification involve the provider and a verification service. They see the information needed to confirm your account; the service retains private operational records.

That account check is separate from your approval to add it to LifeHash. It gives the service no access to your LifeHash signing key.

Your proof file is readable.

A proof export contains your whole retained document. Its review lists account identifiers, supporting evidence, private commitment openings and salts, any Google ID tokens, and retained removals.

It contains no signing key. The recipient can read, keep, and forward it. Removing an account later does not erase a file you already shared.

Your recovery file is encrypted.

This separate file includes your LifeHash keys, private evidence, and saved operations. Keep both the file and its password. Restore works only in a browser with no saved LifeHash; it does not merge or overwrite identities.

Google, GitHub, and email access cannot decrypt it or restore your LifeHash. LifeHash cannot reset the password for an existing file. If your current browser still opens your LifeHash, you can save a new file with a new password.

A backup is a snapshot. Save an updated copy after account or saved-operation changes, and use one active wallet copy. Restored browsers do not synchronize automatically.

Check what the file actually supports.

The verifier separates signatures, account acceptance, and provider checks. The recipient chooses a trust policy independently of the file.

A file alone does not establish current account control or that all history is included. Chain publication is optional and separate; this browser-local flow does not establish current public state.