MBS Workbench is 100% local-first. No cloud, no telemetry tracking, no accounts. Your code never leaves your machine.
🔒 MBS Workbench runs 100% locally. There is no telemetry, no analytics, no crash reporting, and no account required. Your code never leaves your device.
MBS Workbench is an offline-first, privacy-first development tool. Unlike cloud-based coding assistants, MBS Workbench processes all AI inference, code analysis, image generation, and model training entirely on your local hardware. We have no access to your code, projects, prompts, or generated content.
This Privacy Policy explains what minimal data interactions exist and how they are handled.
MBS Workbench does not collect, transmit, or store any of the following:
All of the following data is stored exclusively on your local machine and is never transmitted to our servers:
| Data Type | Storage Location | Purpose |
|---|---|---|
| Application settings | Local storage / SQLite | Persist user preferences across sessions |
| Chat history | Local storage | Conversation persistence for your reference |
| Model files (GGUF) | Local filesystem | AI inference — runs entirely on your hardware |
| Generated images | Local filesystem | Output from local Stable Diffusion engine |
| Trained adapters (LoRA) | Local filesystem | Fine-tuning results on your own data |
| Embeddings / vector DB | Local SQLite | RAG pipeline for codebase search |
| Extension state | Local storage | Installed extension configuration |
| Daemon logs & metrics (Phase 61) | ~/.mbs/daemon.log | Developer observability and debugging — 500-entry ring buffer |
| Agent loop execution traces | Local storage | Autonomous agent iteration history and safety logs |
| Debug session data | Local storage | Call stacks, variables, breakpoints — used for AI analysis |
| Terminal environment context | Process memory | $MBS_HOST, $MBS_PORT, $MBS_WORKSPACE — never logged |
MBS Workbench v0.2.4+ includes rich local observability (Phase 60 T5.12 + Phase 61 V2.1):
~/.mbs/daemon.log. Useful for debugging but never uploaded.MBS Workbench communicates with external services only when you explicitly initiate it. These connections are opt-in and clearly indicated in the UI:
When you browse or download models from HuggingFace, your device connects to HuggingFace's servers. This is subject to HuggingFace's Privacy Policy. We do not proxy, log, or monitor these downloads.
If you configure API keys for cloud providers (OpenAI, Anthropic, Google, AWS Bedrock, etc.), your prompts are sent directly to the respective provider's API. Each provider has its own privacy policy. We do not intercept, store, or relay this data. Cloud providers are clearly labeled in the UI and are entirely optional.
The Cloud GPU Hub feature allows you to rent GPU compute from third-party providers (e.g., Vast.ai, RunPod, Lambda Labs). When you use this feature, your interactions with those providers are subject to their respective terms and privacy policies.
MBS Workbench includes an optional auto-update mechanism that checks for new versions. This check contacts our update server and transmits only the current software version number to determine if an update is available. No personal data is sent.
If you obtain a license key (e.g., via our Discord bot or website), the following data may be collected:
License key validation may involve a brief check against our server to verify key validity. This check transmits only the license key itself — no code, project data, or usage information.
Export Features (Phase 61 V3.2): Model configurations can be exported as Docker Compose YAML files or Python inference snippets. These exports are generated locally on your device. If you deploy them, you're responsible for securing any sensitive configuration (API keys, model paths, etc.).
If you submit information through our website (e.g., early access request form), we collect the information you voluntarily provide (name, email, company, role). This data is processed through Formspree and is used solely to respond to your inquiry and manage early access. We do not sell, share, or use this data for marketing beyond communications you have opted into.
Our community spaces on Telegram and Discord are operated by their respective platforms. Your participation in these communities is governed by their privacy policies. We recommend reviewing:
Because MBS Workbench operates locally, your data security is inherently tied to your device's security. We recommend:
For paid features and license keys, we employ industry-standard security practices including encrypted transmission (HTTPS/TLS) for any server communication.
MBS Workbench is not directed at children under the age of 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us so we can take appropriate action.
We may update this Privacy Policy from time to time to reflect changes in our practices or for legal, operational, or regulatory reasons. The "Effective Date" at the top of this page indicates when the policy was last revised. We will make reasonable efforts to notify users of material changes.
MBS Workbench includes autonomous agent loops (Phase 61 Agent Loops) that can:
All agent operations occur locally on your device. No code or execution traces are transmitted to us. Agent loops operate under a three-tier safety system that may require human approval for destructive operations.
For privacy-related questions or concerns, contact us at: