Codebase Indexing stores embeddings remotely. These embeddings are somewhat reversible.
That feature is not configurable at the organization level. It is also on by default and there are frequent nudges to turn it on within Cursor.
Currently, an organization wanting to use Cursor without sharing embeddings is forced to train all developers to turn the feature off, ignore all the nudges, and trust that none of the developers misunderstand and turn it on at any point. That is kind of unrealistic.
What is the point of having the ability to turn embeddings off at all if companies cannot rely on the feature? It would be super nice to get organization-level control of this!