How to minimize proprietary data/source leakage when using Air + Junie Lite

Question

If Air is used with the free Junie Lite mode, is there a risk of leaking proprietary data/source to the internet?

If so, which setup to use to prevent leakage?

Answer

Unfortunately, Junie Lite is not local-only. It sends the prompt and relevant project context (potentially source-code fragments) to JetBrains infrastructure for inference.

To minimize potential leakage while using it:

• Use a sanitized test repository with no credentials, .env files, private keys, customer data, or proprietary source.
• Use Plan/Ask/read-only permissions and avoid granting unrestricted terminal or file access. This limits agent actions, but does not prevent context from being sent to JetBrains.
• Do not configure MCP servers or external integrations for the test.
• Avoid web search for confidential queries. Air/Junie web search uses Tavily in the background, so search queries may be sent through that service.

⚠️ If data must never leave the network, then Junie Lite is not sufficient. Use a genuinely local/self-hosted model or an approved on-premises LLM gateway with outbound access disabled.