I created https://www.deadmantracker.com https://www.deadmantracker.com and am implementing the reverse of this but your solution is a good alternative that I m

I created https://www.deadmantracker.com https://www.deadmantracker.com and am implementing the reverse of this but your solution is a good alternative that I might support too. The way I saw it working was: * Encrypt docs into a compressed archive * Upload encrypted docs to service * Distribute password for unencryption using something not build into the service (tell them via Signal, or Protonmail, or a piece of paper, or word of mouth) * Link for encrypted archive only becomes available once the dead mans switch is triggered In the same way a password could be uploaded and only released when the switch is triggered. A service just can't hold both parts.