WorkFlowy has end-to-end encryption, but not client side encryption.
What is end-to-end encryption? (Wikipedia article)
End-to-end encryption is like sending a letter to someone with a secret code. If you send me a letter with a secret code, you want me to be able to read it, but no-one else. So you could have your friend deliver it to me, and know that even if they open it, they won't be able to read it. Once I get the letter, on the other hand, I'll be able to read it, because I also have the secret code.
WorkFlowy has end-to-end encryption
When you type something into WorkFlowy, it is encrypted before it is sent to our servers, and then it is encrypted again when it is stored in the database. This means that during transit and storage, everything is secret, but WorkFlowy's servers can still decrypt and read the content, just like I can still read the letter you sent me with a secret code.
What is client-side encryption? (Wikipedia article)
Client-side encryption is like a private diary. You want to be the only person who can read it, and you want to make sure no one else can read it, even if they find your diary. There's still a secret code, but this time you're the only person who knows it.
In the context of a service like WorkFlowy, this is useful so that we can help you manage your data (store it, sync it, share it with people you give permission to, etc) without actually knowing what the data is. It's a very secure way to work with a cloud service like ours.
WorkFlowy does not have client-side encryption (but we hope to)
WorkFlowy's servers can read the content you send to us. We understand that this limits how some organizations can use the product, and we hope to build this feature.
There are also significant downsides to client-side encryption, if you lose your "code" you basically lose the data, and you can't use features that rely on the server knowing anything about the content, but for many organizations this is a very reasonable trade-off, and most current WorkFlowy features would still work.
If your organization wants to use WorkFlowy, and the lack of client-side encryption is the main blocker, please reach out to firstname.lastname@example.org. We'll start keeping track of the demand. If you're a large organization willing to buy a significant number of seats, that might even be enough to motivate us to push this to the top of our priority list.