[mbork_pl]

Thanks, that's an interesting option! It requires trust in the bank (of course), but I'm not that paranoid. However, I have a feeling that it's a bit expensive - it can be cheap (say, ~$10 per month, which is not as cheap in my country as it is in the US, but still), but frankly, I'd prefer a homebrew solution.

[Bender]

In that case, multiple thumb drives because they do go bad with instructions where to download 7-zip so they do not rely on Google and to use "the family password" to open a password protected 7-zip file. Plain text file inside that. Ensure everyone in the family know what they "family password" is by making use of it for something.

Keep the thumb drive tech up to date annually just in case the tech changes and they can't figure out how to use current thumb drive tech.

Have thumb drives and instructions replicated in multiple places in the event the home burns down or is otherwise destroyed. stored with other trusted family members that live near by or even at remote locations.

Avoid clouds, cloud accounts, any system you do not control as they can be hacked, go out of business, lose your data, accounts disabled upon death, accounts closed because who knows why, etc...

[mbork_pl]

If I'd go that route, why not include that (encrypted) file on the drives themselves?

> Avoid clouds, cloud accounts, any system you do not control as they can be hacked, go out of business, lose your data, etc...

Yes, that is obvious, but still a great point. I'd probably use my VPS for that (maybe even two of them for redundancy).

[Bender]

why not include that (encrypted) file on the drives themselves?

That is what I was trying to convey. Both unencrypted instructions for where to get 7-zip, the encrypted file, and hints to what "family password" means, replicated to multiple thumb drives in the event one fails or gets corrupted. If they are using windows they may not even need to download 7-zip but one never knows.

    D:\ dir
    encryptd.7z
    README.txt