This is tempting, particularly when learning new libraries, but it seems like it could be resolved with an offline database at some point instead of a hosted cl

This is tempting, particularly when learning new libraries, but it seems like it could be resolved with an offline database at some point instead of a hosted cloud service. This would probably improve performance a bit (in terms of responsiveness, rather than accuracy). I can see where you might want to index all of my code to add to your store of information about how frequently various functions are used, because "more is better" in terms of training data, but there are plenty of open-source projects that could be polled instead. For my own code, why not simply analyze my existing projects on my own machine without sending it elsewhere? It's pretty laughable that when one clicks through to the security page, the very first thing beyond the heading of "Security. Built in." is "Kite is Cloud Powered." as though that were a feature instead of a liability. While directory whitelisting and a .kiteignore seem like decent ways to prevent code from leaking, it's only one small bug away from disclosing a company's proprietary secret sauce to unknowns entities.