If you have the encrypted key 'somewhere safe', it is not account recovery because your key was never lost. It is just a more elaborate password change.
As I've said, you can't have both meaningful encryption (as in service operators can't decrypt data by themselves) and account recovery (as in you've lost credentials necessary to access account).
> If you have the encrypted key 'somewhere safe', it is not account recovery because your key was never lost. It is just a more elaborate password change.
Uh...what? I think you misunderstood. You use the "password" to access your account, encryption key to decrypt the data. You lose the password, you lose access to your account and your data. However, server has the ability to grant you access to your account without the password. BUT Access is not equal to decryption of data.
The key that you have is used to decrypt your data on your device. The "service operator" is never involved in the decryption step; only the access step.
This is the only way to recover account access + data for zero knowledge apps. It is similar to the [backup data -> delete account -> create new account -> restore backup] process but it's automated and much more secure.
> The key that you have is used to decrypt your data on your device.
Oh so you need a safely stored key and your own device to decrypt data. Lol. Why do you say we need to use that service, if all is done on user's device?
but being serious, everything you say just proves my point, yet, somehow, you refuse to see it.
As I've said, you can't have both meaningful encryption (as in service operators can't decrypt data by themselves) and account recovery (as in you've lost credentials necessary to access account).