Here's an example... when you validate the client and run a native app. What we did was that we built out a generic datastore system which supports any storag

Here's an example... when you validate the client and run a native app. What we did was that we built out a generic datastore system which supports any storage provider backend. https://getpolarized.io/2019/03/22/portable-datastores-and-platform-independence.html https://getpolarized.io/2019/03/22/portable-datastores-and-p... But the app is downloaded. It's not just a web app that could be changed on you. If it's something that's open source and you download it you have less of an issue with people swapping out the JS on you. The idea in this situation is when you store your docs it's encrypted before we even see the data. This way you don't have to trust us. No trust required. We could even be a hostile actor and as long as your code is legit you're good to go. I like this honestly as I don't have to rely on our customers trusting us. We literally CAN NOT see your data. The main issue is getting keys between machines though. Firefox has an interesting strategy for that but I haven't had time to dive into it yet.