I mean, the server would need to have the private keys in order to encrypt the data right

I had no idea mega did that, that's awesome. The whole idea that the server doesn't have the key, like -- it's so simple, but it never occurred to me. Why would the server ever need to decrypt it?

This shit is wrinkling my brain.

And I'm even more mad at every cloud provider. Why you decrypting my shit, Google?

So I guess the question is, for your site idea, where does the encryption start? Like, you want the text on the page and the form data encrypted, but, is the text on the form's submit button encrypted? If it is, your user has to be a developer to some extent, or you needs to build like a WordPress style wysiwyg editor that also encrypts everything -- and, like, that's kinda cool, but actually writing that code sounds like torture. I'd rather spend all that development time giving myself papercuts and squirting lemon juice into them.

So an encryption "barrier" has to exist. The Mega server doesn't decrypt your file, but it knows that it's getting a file of some kind for you, and it knows the shape of the data. It's not completely ignorant -- and, like the WordPress problem above, you could prevent that -- keep the server from even knowing what it's doing -- again, kinda cool, but it sounds like torture to actually write.

So the question is, where are you putting that barrier? It seems like, wherever that barrier is, is also how deep a non-developer user can get into using it. To put that another easy: the more of the site's content that's encrypted, the more development skills the user has to have.

Or I'm just misunderstanding your project entirely, which I will attribute to the fact that it's 1am.