Clear cache after the vault has been locked

[tobihagemann]

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

Add an option so that a vault can clear its cache after it has been locked

Motivation

Even though the local device is not Cryptomator's security target, some users would feel more comfortable if there is as little decrypted content as possible on the device (even though it's in a sandbox).

Adding a "Clear Cache After Lock" option (per vault) would make sure that decrypted content is automatically removed without having to think about it. However, it shouldn't be enabled by default because it would cause usability drawbacks (often used files have to be re-downloaded, thumbnails get lost).

Considered Alternatives

A user can already manually clear the cache to achieve the same goal.

Anything else?

No response

[ratranqu]

Would "Encrypting the cache after lock" make sense (for the scenario where bandwidth is more expensive than encrypting)?

[Blabss0]

Hi, Is there a chance a "clear cache after lock" option would ever come to the iOS app ? Because I use Cryptomator as a way to encrypt cloud content, I don't want everything I open with cryptomator to be stored on my device and take storage on such until I manually delete it all. I would like for Cryptomator to just delete everything everytime the app auto or manually locks.

[phil1995]

One problem that came up to my mind is that this wouldn't really work with auto-lock because technically we do not lock after n minutes but if you interact again after n minutes without any interaction in between as the Cryptomator FileProviderExtension (like all other iOS apps) does not run all the time in the background. So we would actually clear the cache on the next interaction and I'm not sure if there would be any benefit here?

On the other hand one could easily implement a clear cache on manual lock.
However, as we obviously don't have any analytics we don't know how many users really lock their vaults manually in the app… so it would be nice to get some feedback and then I guess nothing really hold us back to implement this :)

[olfway]

Btw, is this cache encrypted? If it is, then it's less a problem I guess