1 min lesson
Privacy as a product tier
Recall the main items in "Privacy as a product tier", then connect each one to the work.
Step 1 of 2
Privacy as a product tier
Frame this as a differentiator, not just a constraint. A privacy mode - no retention, no training, optionally local indexing - is exactly the thing that lets a security-conscious enterprise say yes when a competitor can't give the same guarantee.
- A "privacy mode" that hardens defaults (zero retention, no training, restricted egress) and is contractually verifiable, not just toggled.
- Clear data-flow documentation, since enterprise buyers need to show their own security team exactly where code goes.
- Be ready to position this against Copilot, Windsurf and Claude Code - "who do you trust with the repo" is a real buying axis and an opinion here signals you understand the market.
Watch out
Don't promise "fully local, fully private, fully powerful" - that combination doesn't exist with today's latest-generation models. State the tradeoff plainly: local maximizes privacy at the cost of capability, server-side maximizes capability with strong but non-zero exposure. Naming the tension is more credible than pretending it away.