PRIVACY / MICROSOFT STORE
DSH Desktop is a community desktop packaging of the official DeepSeek Harness. The app accesses or transmits information when you use a configured model service, the Cordis marketplace or package downloads; this policy explains where that data goes and what the desktop layer does with it.
DSH Desktop is maintained by the web-casa open-source community and published in Microsoft Store under the reserved product name DSH Desktop (Community). It is not affiliated with or endorsed by DeepSeek. Use the Support page for privacy or product questions; do not include personal data in a public issue.
The desktop app injects DSH_TELEMETRY_DISABLED=1 into the Harness child process. It does not enable its own product analytics. Some bundled upstream components or user-installed plugins may have their own behavior; review them before installation.
DSH Desktop is a client for the Harness. Prompts, files and tool output you submit are sent to the model provider or API endpoint that you configure in Harness. The desktop layer does not add another copy or route that traffic through our servers. You are responsible for reviewing the provider's privacy terms.
Settings, sessions, installed plugins and presets are stored under your user profile in a harness/ data directory isolated from the CLI's ~/.dsh. The directory is created with restricted permissions. No local content is uploaded automatically.
Marketplace searches and item details are requested from cordis.run. Approved npm packages are downloaded directly from registry.npmjs.org. Remote presets are downloaded directly from a fixed cordis.run HTTPS endpoint after you confirm the request. These services receive ordinary network metadata such as your IP address. The Microsoft Store build restricts plugin installation and activation to the reviewed allowlist, verifies package integrity, disables package build scripts and does not activate a plugin without a separate explicit action.
The Microsoft Store build disables the app's own updater; Microsoft Store handles package delivery and updates under Microsoft's privacy practices. The separately distributed Windows build may check GitHub Releases for updates and verifies updater artifacts with the project's embedded minisign public key. macOS updates are currently manual.
Diagnostics export is always user-initiated. The generated ZIP or JSON is stored locally unless you choose to share it, for example in a GitHub issue. Redaction is best-effort and is not a guarantee that all sensitive content is removed.
The website does not run product analytics or advertising scripts. It is served by a static hosting provider that may process ordinary request logs. Downloads and non-Store update checks use GitHub Releases; marketplace metadata and presets use cordis.run; plugin packages use the npm registry; model traffic goes to the service you configure; Microsoft Store distribution follows Microsoft's privacy practices.
The Harness webview has an empty desktop IPC capability set and connects only to a random loopback port. Child-process environment variables are sanitized before launch. See the Security page for the threat model and supply-chain controls.
DSH Desktop is a developer tool and is not directed to children. If you are under the minimum age required by your jurisdiction, do not use the application without a parent or guardian.
We will update this page when the application's data practices change. Use the Support page for questions and requests. If a report contains a vulnerability or sensitive security information, use the repository's private Security Advisory flow instead of a public issue.
