Privacy Policy

Last updated: July 11, 2026

The short version

Loophole is a free, open-source AI code editor built on top of Void, which itself is a fork of Visual Studio Code. We built it with one rule in mind: your code and your data stay yours. We don't run servers that store what you write, what you chat about with an AI model, or anything else about how you use the editor.

How AI features work

When you use Loophole's AI chat, autocomplete, or agent features, your request is sent directly from your machine to the AI provider you've chosen — for example Anthropic, OpenAI, Google, DeepSeek, OpenRouter, or a local model running on your own computer via Ollama, vLLM, or LM Studio.

There is no Loophole server sitting in between. We don't proxy, log, or store your prompts, your code, or the model's responses at any point. You connect using your own API key (or your own locally-hosted model), and the conversation happens between your machine and the provider you picked.

Because of this, any data handling that happens after your request leaves your machine is governed by that provider's own privacy policy — not ours. If you use Claude, that's Anthropic's policy; if you use GPT-4o, that's OpenAI's; and so on. If you'd rather nothing leave your machine at all, Loophole supports fully local models through Ollama, vLLM, and LM Studio.

What we don't collect

• We don't collect your source code or files.
• We don't collect your AI chat history or prompts.
• We don't require an account or sign-in to use the editor.
• We don't run analytics or telemetry that tracks how you use the app.
• We don't sell or share data with third parties — because we don't have any to share.

Open source, so you can verify it yourself

Loophole is fully open source. Instead of asking you to trust a privacy policy on faith, you (or anyone) can read the actual source code that ships in the editor and confirm exactly what it does and doesn't send anywhere.

Repository: github.com/loophole-ai/loophole-ide

This website

This marketing website (the one you're on right now) doesn't use tracking cookies or analytics scripts. Downloading the editor from GitHub Releases is subject to GitHub's own privacy policy, since that's where the files are hosted.

Changes to this policy

If anything about how Loophole handles data ever changes, we'll update this page and reflect the new date at the top. Given the project's local-first design, we don't expect that to happen often.

Questions

If you have any questions about this policy or how Loophole works, feel free to open an issue on GitHub.