Effective date: August 2nd, 2026
These Desktop App Terms ("Desktop App Terms") supplement and form part of the Deep Code Terms of Service (the "Terms") between you and Vibe Star Pte Ltd. ("Deep Code"). Capitalized terms not defined here have the meanings given in the Terms. These Desktop App Terms govern your use of the Deep Code desktop application made available for installation by Deep Code, including any updates or successor versions (the "Desktop App") and each category of local device access that the Desktop App may request or use, as described in Section 2. In the event of any conflict between these Desktop App Terms and the Terms, these Desktop App Terms prevail to the extent of the inconsistency. For clarity, the license granted to you under the Terms to access and use the Services includes a limited, non-exclusive, non-transferable, non-sublicensable, revocable right to download, install, and use the Desktop App in object-code form on devices you own or control, for your personal or internal business purposes, as permitted by your subscription plan. By installing or using the Desktop App, you accept these Desktop App Terms. If you do not accept them, do not install or use the Desktop App.
"AI File Action" means any create, read, modify, rename, move, or delete operation carried out by the Desktop App on your local file system in connection with an AI-assisted task.
"Device Access Feature" means any feature of the Desktop App that accesses hardware, files, or applications on your local device, as further described in Section 2.
"Input" means (i) audio, images, video, screen captures, or other media captured through your device hardware or operating system and submitted to the Desktop App when you activate the relevant feature, and (ii) files that you actively select and submit to the Desktop App for processing.
"Local MCP Connection" means an integration between the Desktop App and a third-party application, service, tool, or local process on your device or local network, established through the Model Context Protocol ("MCP") or a similar protocol that permits the Desktop App to read from and write to that application, service, tool, or local process.
2.1 The Desktop App does not access your device hardware, file system, or local applications by default. All access requires your express action. The Desktop App operates only within the scope of features you enable. Deep Code may restrict or decline certain file types, sensor uses, or Local MCP Connections where reasonably necessary for security, integrity, abuse prevention, or legal compliance.
2.2 Where enabled by you, the Desktop App may: (a) process files you select; (b) capture audio or visual input through your device microphone or camera; (c) connect to third-party local applications via the Model Context Protocol; and (d) perform AI File Actions within folders or paths you designate.
2.3 Material you submit or make available through any Device Access Feature (including files, audio, images, or data accessed via Local MCP Connections) may be transmitted to Deep Code's servers or third-party AI providers for processing to generate AI Output and is treated as Customer Data under the Terms once transmitted.
2.4 You are responsible for your use of Device Access Features, including: (i) ensuring you have all rights and permissions to submit files or grant access to data in connected applications; (ii) obtaining any required consents from third parties under applicable recording, privacy, or biometric laws; (iii) not submitting, accessing, or connecting sources containing sensitive data that the Services are not designed to handle, as described in the Terms; (iv) reviewing AI Output before relying on it; and (v) maintaining and revoking permissions or connections as appropriate.
2.5 AI File Actions are driven by AI Output, which may contain errors, and may occur without a separate confirmation step. By enabling file system access or initiating any workflow involving AI File Actions, you assume all risks arising from such actions. Deep Code does not retain local file copies and cannot restore deleted or overwritten content. You are solely responsible for maintaining independent backups before enabling file system access or initiating such workflows.
2.6 Deep Code has no obligation to monitor, supervise, or control your use of Device Access Features, including any access to your device, local files, or connected applications, and does not review or validate files, data, or actions except as necessary to provide the Services.
2.7 Your use of any third-party application connected via Local MCP Connection remains subject to that application's terms and controls. Such applications may expose the Desktop App to incomplete, inaccurate, or malicious data or instructions. You assume all risks arising from your use of such applications in connection with the Desktop App, and Deep Code is not responsible for third-party applications, their data, or any consequences of the Desktop App accessing or acting on such data at your direction.
3.1 All material submitted through a Device Access Feature constitutes Customer Data under the Terms once transmitted to Deep Code's servers or Third-Party AI Providers. It is subject to the data handling provisions in the Terms, including the "Rights in Customer Data", "Use of Infrastructure and AI Providers", "Use of PII", and "Retention of Your Information" sections and the Privacy Policy. You are responsible for ensuring compliance with any applicable data privacy laws.
3.2 The Desktop App may process material locally on your device without transmitting it to Deep Code's servers, for example, during Local MCP Connection operations performed by integrated desktop applications. Such processing does not constitute a submission of Customer Data to Deep Code. Deep Code has no visibility into, and accepts no responsibility for, data processed solely on your device.
In addition to the License Restrictions in the Terms, you agree not to:
The limitations and exclusions of liability in the Terms apply in full to the Desktop App and all Device Access Features. Without limiting those provisions, and to the fullest extent permitted by law, Deep Code is not liable for:
Nothing in this clause limits liability that cannot be excluded under applicable law.
The indemnification obligations in the Terms extend to cover any claims, damages, losses, or expenses arising out of or related to: (a) material you submit through any Device Access Feature, including Input, and data accessed via Local MCP Connections; (b) your use of local file system access or AI File Actions when that feature is enabled; (c) your failure to obtain required consents from third parties before using sensor features; and (d) any breach of section 4 of these Desktop App Terms.
Deep Code may update the Desktop App and enable new Device Access Features at any time. Where a new or updated Device Access Feature materially changes the scope of access to your device or data, Deep Code will update these Desktop App Terms and provide you with reasonable notice in-app or by email. Your continued use of the relevant feature following such notice constitutes acceptance of the updated terms. Where required by applicable law, Deep Code will obtain fresh consent before enabling new Device Access Features that involve the processing of sensitive or biometric data.
"Bring Your Own Key" (BYOK) means you use your own API Key obtained directly from a third-party model provider. When you enter an API Key into the Desktop App, it is stored only on your local device and is not transmitted to Deep Code's servers. The API Key is saved at the following location in your home directory on each operating system:
| Operating System | File Path |
|---|---|
| Windows | ~/.llm_api_keys.json |
| Mac | ~/.llm_api_keys.json |
| Linux | ~/.llm_api_keys.json |
You are solely responsible for safeguarding and maintaining the confidentiality of the API Keys stored on your device. Deep Code has no access to, and accepts no responsibility for, any API Keys you store locally.
These terms apply when you select the "Bring Your Own API Key" (BYOK) model.
8.1 You independently obtain, manage, and maintain the API Key from the third-party model provider and enter into contract directly with that provider. In this model, Deep Code only provides a local client tool and is not a model-service agent or reseller.
8.2 Your prompts, context, and conversation content are transmitted in encrypted form directly from your device to your specified model provider and do not pass through Deep Code's servers. Post-receipt processing by the provider, including data storage, usage, and security safeguards, is solely the provider's responsibility, and you should read and understand its terms and privacy policy. Notwithstanding the above, Deep Code remains responsible for the security of the Deep Code client itself, including accurate routing of data to your designated provider endpoint and ensuring the Deep Code client does not contain malicious functions or gross negligence.
8.3 Fees from self-provided key usage are charged directly by the model provider. If your API Key is limited or blocked due to insufficient balance, sanctions by the provider's risk controls, or other reasons causing service unavailability, Deep Code bears no responsibility and provides no refund or compensation.
8.4 You warrant that your API Key is obtained and used lawfully and not for generating or disseminating unlawful or infringing content. You shall indemnify Deep Code for all claims, losses, and liabilities caused by your breach of this clause. The Bring Your Own Key Model Risk Notice and Disclaimer in the attachment forms an inseparable part of this Agreement.
The governing law, dispute resolution, limitation of liability, indemnification, and all other general provisions of the Terms apply equally to these Desktop App Terms. If any provision of these Desktop App Terms is found to be invalid or unenforceable, the remaining provisions continue in full force.