We had some fantastic questions and comments in response to our press this week that deserved public answers. As a security company we recognize that people trust us when they use our product. We want to reciprocate this trust by offering transparency in our processes. Please feel free to add any more comments or questions you may have
“Great idea – my wife is a middle school principal. It’s amazing the things teens are sending via SMS and their ignorance about its lasting impact and potential for broad distribution. Snapchat is clearly targeted to this younger group and if it (Gryphn) can save just one person from disastrous embarrassment, I’m all for it.” – Shopilly (TechCrunch)
Protecting teens from sexting mistakes? Sure, we can roll with that. The same security that protects a soldier’s mission critical image from being intercepted in transit, downloaded to a computer, forwarded, saved, screenshot-ed, decrypted or shared will also protect a teen from having their ill-advised image uploaded to Facebook.
“And this is necessary for life because why exactly? So teens can sext each other. Wow, I want to invest in this company. Where do I put my money? Maybe the company founders just want to see a lot of user generated porn.” – Darth (Business Insider)
User generated porn? This is (by far) our favorite comment. Our users include SWAT, local law enforcement and first responders. While we’re sure there’s a fetish for that, we don’t hold the keys to decrypt people’s messages. Or have the ability to see them. Or to give anyone access to them. Even under duress. Our patent-pending public/private encryption key exchange makes it impossible for ANYONE other than the sender and recipient to access or view the contents of even one single message encrypted and sent through our app. Yes, even if it’s porn. Yes, even if it’s really good porn.
“(This works) until people start taking pictures of their phones with other peoples’ cameras…” – Evan (Business Insider)
Yes. Absolutely true. For healthcare, financial and law enforcement (and eventually government), the concern is in knowing who is accessing these images. In whose hands does the phone rest? We achieve this currently through a passcode on the app itself and, eventually, with technology that… has already been used in beta by some of you. This last point in particular is, perhaps, proof that, despite the amusing moniker that some of our press bestowed upon us, our target market is not those looking to macgyver a sexting app, but those who are required to encrypt digital messaging to satisfy the legal requirements of their regulated industry.
“If this is developed in the US, it must be CALEA-compliant, and in that case the company has to store either plaintext conversations, or decryption keys, on its servers, to furnish to law enforcement whenever asked. In that case the first successful break-in into their infrastructure would give the attacker keys to information that is thought to be secure.” – prostoalex (Pandodaily)
Actually – your conversations never flow through Gryphn’s servers, and the encryption is performed by you, the individual, and not by Gryphn. Gryphn maintains Public Keys, but the corresponding Private Keys reside with the user. From: http://paranoia.dubfire.net/
These are good questions, comments and thoughts, but this is only the beginning. Please add any other questions you would like to see answered in the comments below.
Secure messaging with Gryphn’s app:
“Go from unsure to secure in 60 seconds or less — with the ‘year’s most innovative startup for national security‘