Why encrypt code locally before sending it, if the connection to the server is already secure?
Transport encryption (TLS) protects data in transit between client and server, but the server itself still receives and can act on the plaintext once it arrives. Encrypting locally, before transmission, means the specific application logic on the server is deliberately built to decrypt only what a given operation needs and discard it immediately — a stronger, architecture-level privacy commitment than relying on transport security alone.
Answered in
How Cursor Indexes Your Entire Codebase Without Ever Storing Your CodeCursor's semantic search runs on embeddings, not source. The server never persists a line, and a Merkle tree keeps the index in sync as you type.
Read the full analysisOther questions this article answers
- How can Cursor answer questions about an entire codebase without storing the code?
- If embeddings are stored instead of source code, can the original code be reconstructed from them?
- Why does Cursor use a Merkle tree to keep the index synchronized instead of just re-scanning changed files?
- What happens when the server needs the actual source code, not just its embedding?
More how ai actually works questions
- How many new researchers can receive the next OpenAI grant?
- When do applications open?
- Does the classifier make a final decision about an image?
- Can any developer call the classifier?
- How can Cursor answer questions about an entire codebase without storing the code?
- If embeddings are stored instead of source code, can the original code be reconstructed from them?
- Why does Cursor use a Merkle tree to keep the index synchronized instead of just re-scanning changed files?
- What happens when the server needs the actual source code, not just its embedding?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the How AI Actually Works beat.