eterna

You keep control.

Check the changes

Your key signs each plan change and recovery package. The independent reader checks those signatures and compares a saved checkpoint to detect older or conflicting copies. Offline checks cannot find later changes. Blockchain anchoring and independent witnessing are not connected yet.

What this release stores

Generated references, category and dependency codes, roles, scoped permissions, reports, signed revisions and salted file fingerprints. Public signing keys identify accounts without names or email addresses. These limited records can still reveal context; keep exports safely.

What stays outside

Assets, private documents, account and policy details, passwords, recovery codes, seed phrases, keys, shares and the mapping to actual people. File checks run locally; contents and filenames never reach Eterna. Eterna hosts no private payload, including an encrypted one.

Access to the platform

Unlock with your locally encrypted account key and passphrase. Save and verify its backup before creating your account. Eterna does not receive the private key or passphrase and cannot reset them. Shared planning access is limited to the paths selected by the owner.

Evidence, accurately described

Recipient signatures identify who reported each result. A dummy-file check compares bytes locally; Eterna receives only the fingerprint. Neither proves live access or legal authority. Changed paths, expired access and older evidence require review. Independent security review remains outstanding.