In some embodiments, the recovery escrow service 230 publishes the recovery private key 205 in a public repository 240 upon detection (e.g., detection by the recovery escrow service 230) of the at least one first computing device 210 being unavailable, instead of the recovery escrow service 230 directly sending the recovery private key 205 to the at least one second computing device 220. For instance, upon detection of the at least one first computing device 210 being unavailable the recovery escrow service 230 may send the recovery private key 205 in a public repository 240 such that in order to carry out recovery of the keys, the at least one second computing device 220 may simply retrieve the recovery private key 205 from the public repository 240 without direct communication between the at least one second computing device 220 and the recovery escrow service 230. The public repository 240 may be a publicly available service (e.g., such as ‘GitHub’) that may be used to publish data to clients of the system, for instance publish data to users of the at least one second computing device 220. The published data may include periodic reports and/or the recovery keys when needed. In some embodiments, the at least one second computing device 220 mathematically verifies that indeed the encrypted key stored therein, may be decrypted to the relevant private key when the decryption key is provided (e.g., from the recovery escrow service 230).