SecretHub Privacy Policy
Effective date: 2026-11-22
SecretHub ("the App") is a desktop vault for developer secrets, developed and operated by Yinghao Shi ("we", "us"). This policy explains what data the App handles, when it uses the network, and the choices you have.
1. In short
SecretHub has no account system, no cloud sync, no advertising and no analytics or telemetry. We do not collect your secrets, and we cannot see them. Everything you save stays on your computer.
2. Data stored on your device
- Vault. The API keys, tokens, logins, bank cards, notes and other values you save are encrypted with a key derived from your master password (Argon2id, AES-256-GCM) before being written to a local database in the App's data folder (Windows:
%APPDATA%\com.secrethub.desktop\; macOS:~/Library/Application Support/com.secrethub.desktop/). Names, providers, tags, variable names and similar metadata are stored alongside so that the App can list them. - Master password. We never receive it and cannot recover it. If you forget it, your vault and backups cannot be opened.
- Other local files. Request queues for AI tools (contain no secret values), the media library files you import (not encrypted), a cached model catalog, audit records without plaintext values, and encrypted backups you choose to export.
- Project files. When you export to a project, the App writes
.envand.env.examplein the folder you choose. A.envfile holds plaintext values; protect it as you would any secret file.
3. When the App connects to the network
| Situation | What is sent, and to whom |
|---|---|
| Update check (about 3 seconds after start, then hourly) and update download | An HTTPS request to updates.9aizhuan.com, a server operated by us, for the update manifest and installer. Like any web server it receives your IP address and standard request headers. No vault data is sent. |
| Saving, checking or syncing an API key (when you use these functions) | The key is sent over HTTPS directly from your computer to the provider's official API address (for example its model-list endpoint) to check it and list the models it can use. The provider processes it under its own privacy policy. Requests go only to HTTPS addresses, private-network addresses are refused and redirects are not followed. We do not see the request. |
| AI secure input form with verification | If an AI tool asks you for a login or key, the form states which website the values will be sent to. When you click "Verify and save", the values you typed are sent to that website (for a login, its login endpoint; for an LLM key, its model list). They are stored only if verification succeeds. |
| Capturing a key from the clipboard | The App opens the provider's official key page in your default browser. After you click Start it reads the clipboard for at most 3 minutes, stores a recognized key, and clears the clipboard. The browser's visit to that page is between you and the provider. |
| Signed model-catalog updates (only in builds where an address is configured) | A request to the configured HTTPS address for a signed list of provider models. No vault data is sent. If your build has no address configured, this does not happen. |
The App does not upload your vault, your secrets, your project files or usage statistics to us or to anyone else. It does not use cookies or advertising identifiers.
4. AI tools and the MCP service
You can connect SecretHub to AI coding tools (Claude Code, Claude Desktop, Cursor) through a local MCP service. The service runs on your computer, opens the vault read-only, and does not decrypt secret values. The AI tool can see names, providers, variable names, validation status and models; for a configuration group it can also see the values of variables that are not marked secret, unless you turn this off for that group. Writes requested by AI (for example writing a project .env) appear in the App for your confirmation, except the AI-assisted import, which runs under built-in guard rails and can be undone. What the AI tool does with the information it receives is governed by that tool's own privacy policy.
5. Website analytics
This website (bigstoneopc.com and its subdomains) uses Cloudflare Web Analytics, which measures page views without cookies and without tracking you across sites. The App itself contains no analytics.
6. Retention and deletion
Your data stays on your computer until you delete it. You can delete items in the App, or delete the App's data folder listed above. Uninstalling the App may leave that folder in place; delete it yourself if you want everything removed. Because we hold no copy of your data, we cannot delete or restore it for you.
7. Your rights
Because we do not collect your personal data through the App, there is normally nothing for us to access, correct or delete. For the web server logs of the update service or this website, you may ask us to access or delete data relating to you by emailing privacy@bigstoneopc.com; we will respond within 30 days. If you are in the EU/UK, you may also complain to your local data protection authority.
8. Children
The App is a developer tool and is not directed to children under 13 (or the minimum age in your country).
9. Changes
We will post any changes on this page and update the effective date.
10. Contact
Yinghao Shi (石英豪) · privacy@bigstoneopc.com · support@bigstoneopc.com