47Vault
How could you keep control of private information and recover access to it?
Earlier software is being restored under the working name 47Vault. No public vault is available. Its security has not been established for real-world use.
47Vault explores storage and recovery of private information under the user’s control. One part of that work studies splitting a secret into shares, so recovery can depend on a defined combination rather than a single copy.
A recovery question · illustrative example
What would happen if you lost your usual access method? The proposed product would make the recovery arrangement understandable: which pieces are needed, who holds them and what happens when a piece is unavailable. This is a design goal, not an available recovery service.
Where the work stands
Retained records document tests of a small secret-sharing component. They do not establish a complete vault, recovery of real secrets or production security. The complete storage and recovery experience has not yet been verified.
Before any real use
Keeping control of keys, protecting stored information and recovering access must be evaluated as a complete system. A passing component test is not a security guarantee.
Discuss 47Vault
Discuss your recovery requirements in general terms. Do not send passwords, recovery phrases, keys or other secrets.