Privacy Policy

vibeCodeCLI is a bring-your-own-key command-line tool that runs on your machine. By design, almost everything stays local. This page is the plain-English version of what does and doesn't leave your computer.

Last updated: 24 June 2026. This is the policy for the vibeCodeCLI tool and the vibecodecli.com website. The ThinkingMemory cloud service has its own terms · see below.

The short version

• Your code never routes through us. The CLI talks directly to your model provider and to your machine. ThinkingDBx does not receive your source code, your prompts, or your API keys through the CLI.
• Your keys stay local, in an owner-only (0600) file under ~/.config/vibecodecli/, or in your environment.
• What leaves your machine does so to services you choose · your model provider, and (optionally) ThinkingMemory and a web-search provider.

What stays on your machine

• API keys & credentials · written to a 0600 credentials file or read from environment variables. Never transmitted to ThinkingDBx.
• Your code and files · read and edited locally. Git worktrees, sessions, and the repo map all live on disk.
• Session history · saved locally so you can resume; not uploaded.

What (optionally) leaves your machine

The CLI is useless without a model, so it sends data to the services you configure. In each case, that third party's privacy policy governs the data:

• Your model provider (required). To answer a turn, your prompt and the relevant code/context are sent to the provider you picked (Anthropic, OpenAI, Google, a self-hosted server, etc.). We don't see it; their terms apply. For a fully local setup, point the CLI at a self-hosted model and nothing goes to a cloud provider at all.
• ThinkingMemory (optional). If you configure a memory key, short turn summaries are sent to memory.thinkingdbx.com so the agent can recall them later. Before anything is sent, the CLI runs a redaction pass that scrubs known secret shapes (API keys, tokens, private keys) and obvious PII · a defense-in-depth safety net, not a guarantee. You can self-host the memory backend (point base_url at your own instance) or leave it off entirely (the default when no key is set).
• Web tools (optional). fetch_url requests the page you/the agent ask for; web_search sends your query to the search provider you configured (Tavily, Brave, or Exa). Off unless used.
• MCP servers (optional). Any Model Context Protocol servers you configure run as you direct and may reach their own endpoints.

ThinkingMemory

ThinkingMemory is a separate hosted service operated by ThinkingDBx. When you opt in with a key, it stores the (redacted) memory you accumulate so it can be recalled across sessions, scoped per repository. Memory is yours: you can self-host it, or use the cloud service under its own terms and deletion controls. Manage your account and keys at memory.thinkingdbx.com.

This website

vibecodecli.com is a static site served over HTTPS. It uses Google Analytics (gtag) to understand aggregate traffic · standard cookies and usage metrics, no sale of personal data. Your theme preference is stored in your browser's localStorage only. We don't run ad networks or third-party trackers beyond analytics.

Your choices

• Run fully local: a self-hosted model + memory disabled (or self-hosted) = nothing leaves your network.
• Disable analytics with any browser/extension that blocks Google Analytics; the site works the same.
• For ThinkingMemory account data (access, export, deletion), use your account at memory.thinkingdbx.com or email us.

Contact

Questions or data requests: [email protected].