Please see my answer to @kruczek in the same thread. This might be quite broad (maybe unconventional) definition of "secure" I'm talking about here, but the poi

Please see my answer to @kruczek in the same thread. This might be quite broad (maybe unconventional) definition of "secure" I'm talking about here, but the point is: everything that leaks important personal data to the 3rd party (I mean "not me and not the person I'm talking to", so FB is a 3rd party) leaking which is not absolutely mathematically necessary to perform its most basic functions — is not "secure" in my book. It doesn't matter if data end ups leaked because of using ROT13 for message encryption, or because it shares it with FB by design. Sharing my whole contactbook with FB, using proprietary closed-source app and protocol, requiring to have a real phone number (and sharing my access code via SMS with my mobile network operator on the first login — this is truly brilliant for a "secure" app, although I don't quite remember if it was WhatsApp or something similar) is not absolutely necessary for its most basic features and thus is not secure. I want to be clear that `conflating privacy and "secure"` is intentional — violating my privacy automatically harms my security in most direct way. If something quite literally puts me in danger it shouldn't be considered "secure" by definition, no matter how good its crypto is on paper.