So uhh... in other way, to put it bluntly, your team still have not decide what implementation can be used to safeguard an unexpected event such as the user passed away unexpectedly?
Welcome again Miiike, hope you had a wonderful end of summer.
Yes. You are correct. The dev team is busy finishing the Mainnet and the core features.
The development has not advanced that far to be at the point of adding additional features.
So the safeguard feature has not yet been selected for development and therefore has not been analyzed in depth for its implementation.
But this IS a core feature. Your selling point is a service that allows people feel safe to keep their data without the fear of being lost (hence, cloud) or stolen (hence, a third party security system). How would they feel secure if there were no failsafe for the case of the unexpected? I don't think this is an additional feature.
Of course, we can rule this unfortunate event as a team's poor judgement or something that team failed to see. But, this leads to the second thing that pique my interest the second I study your project: team details.
Certainly you didn't plan to offer a data securing service without telling your clients who are the people behind the screen, right?