It is a little more complicated than that. If you start doing MITM on https connections where pinning is involved, typically those sites &#x2F; apps will just stop working as they don&#x27;t trust the CA for the cert that is injected during the MITM. So yes it &#x27;protects&#x27; you, but it does so by not letting you access that page &#x2F; app. Chrome (and I&#x27;m sure most other browsers &#x2F; apps) can have their pins overriden by user installed root CA&#x27;s (which is what they are pressuring people to do in this scenario).<p>You can read more about how Google does certificate pinning here: <a href="https:&#x2F;&#x2F;www.imperialviolet.org&#x2F;2011&#x2F;05&#x2F;04&#x2F;pinning.html" rel="nofollow">https:&#x2F;&#x2F;www.imperialviolet.org&#x2F;2011&#x2F;05&#x2F;04&#x2F;pinning.html</a>