Idea: 1. A phone app which routinely checks for phone movement periodically when the phone is unlocked and sends an "All Good" confirmation back to the app's cloud account where you have set up a number of event triggers. 2. After X amount of time of it failing to send the "All Good" confirmation (due to lightning strike/fire/space lasers destroying the phone or the phone being lost/stolen but remaining locked) the cloud account sends an email to preset addresses stating that if no response is received by clicking on a link within, important information from you will be sent in X amount of time 3. a) Fortunately you have a new phone being set up and you managed to remember your login for your favourite password storage app so don't need this package to be sent. You click the link on the email to delay the delivery long enough for your new phone to be set up so the app can be reinstalled and continue to send "All Good" confirmations to your app cloud account OR b) You don't have any other means to access your digital life than through the information contained in the digital delivery package, so nobody clicks on the link in the email and the digital package is then sent at the required time, thereby restoring your access to your digital life Note: Said app would only allow the creation of the digital 'package' and trigger settings/email recipients once and the entire setup would remain locked and encrypted within your app account cloud storage unless it is deleted/replaced with a new one. This means even if your app account access was compromised the most damage which could be done by the intruder would be the deletion of your encrypted event package and the app could be set to automatically notify you whenever a deletion is done on your cloud account and block any cloud deletion during an active countdown period. This is the closest I can get to a mechanism by which an account compromise reveals nothing useful to an intruder while ensuring that delivery of the data package is only made in the absence of any responses from you or your recipient group. (You could even make it a 'n of n' response requirement just to prevent a 'bad' recipient from maliciously responding to the alert email and reseting the countdown timer even though they know the data release is needed) Thoughts?