Care to explain to the rest of us who don't see it why your link is an example of "snake oil"? I'm familiar with the metaphor, but I don't see the deception yet.

I believe it is the "data in use" portion, glancing from the page.

Why? Because all forms of powerful server-based crypto rely on software-based crypto. The problem with this is they need the private key of yours on the server side, somewhere, from the whole thing to work. This means the server operator can recover the key from a running operating system, easily (through system utilities) or forcefully (reading it out of memory with specialized programs), or just writing code to fool you into enter the passphrase and storing.

If you have heard of host-proof systems, they indicate (I would say correctly) the only way for crytography on network service like the one offered here is the data is encrypted on the client and sent to the server, never ever will the passphrase see server receiving the data. Therefore, not even the service provider can crack it without the same effort as some adversary from outside the system.

That being said, I could have read too much into.

Homomorphic encryption allows one to carry out operations on encrypted data without having to decrypt it; I could encrypt my data, send it to a big number-crunching server, they do the operations without decrypting anything, and send it back to me to decrypt and see the results at my leisure.

It's got some way to go, but it's certainly possible.

I think as the topography of meshnets takes form, it just makes the ability to securely communicate more inherit in the system than storing our private keys on others computers. That makes me really excited. I'm also pretty excited about what kinds of hacks people will build upon such.