https://developers.facebook.com/docs/internet-org/platform-t...
> Your service will be proxied by Internet.org. Since we cannot support SSL, TLS, or HTTPS as part of proxying, your content or service should not rely on passing or collecting encrypted information — resources that do so will not be accessible within Internet.org or will be dropped altogether. While we would prefer to support fully encrypted connections between user and website in all cases, proxying for third-party sites does not allow for this in its current implementation without introducing man-in-the-middle capabilities.
Catch that? They can proxy HTTPS for themselves, but they won't proxy HTTPS for "third-party sites."
Thus, Internet.org isn't even neutral between Facebook and other developers; Facebook gets special HTTPS treatment that nobody else can get!
Related, in an interview on Scroll.in: http://scroll.in/article/724975/facebook-opens-up-internet-o...
> Q: Isn’t it strange that Internet.org wants to offer free basic services but has no email?
> A: If an email provider wants to comply with the platform guidelines that we are announcing, Internet.org would be glad to have it.
Well, yeah, but if that means someone would have to offer email service without HTTPS, so anybody can read my email unencrypted or even send email as me, is that even useful?