The website publishes product information, download entry points, release records, Release JSON, platform status JSON, and legal documents.
It does not receive desktop API keys, providers, prompts, Agent Skills, benchmark history, or local logs.Privacy
Privacy Notice
Data-processing boundaries for the ShnDock website, public downloads, update checks, and local desktop data.
API tests, API cards, providers, prompts, Agent Skills, and reports are processed on the user's device.
ShnDock does not provide API key cloud sync, a web console, or hosted storage for third-party account credentials.When a user runs an API test, the request is sent to the provider, relay, local model service, or custom endpoint selected by the user.
ShnDock does not control third-party logging, billing, availability, service terms, or data-processing practices.Overview
ShnDock is a local-first desktop application for AI API testing and configuration management. The website publishes product information, download entry points, release records, Release JSON, platform status JSON, and legal documents. It does not provide a web console or online API testing.
Desktop API keys, providers, prompts, Agent Skills, benchmark history, and local logs remain on the user device by default. The website does not receive desktop API keys, provide API key cloud sync, or store third-party account credentials for users.
Website and downloads
When users access shndock.com, the download page, public Release JSON, public platform status JSON, or installer files, Vercel and its infrastructure may process necessary request data, including IP address, User-Agent, logs, cache data, and security-protection data.
The website may use Vercel Web Analytics to understand anonymous traffic trends, page sources, and basic device information for improving the website and download experience. This data is not used to create desktop user profiles and does not include local desktop configuration.
Local data
API keys
API keys remain on the user's device by default and are stored through Electron safeStorage using system-level local encryption.
They are not uploaded to the official website and are not written into benchmark history, logs, Skill Packs, or the browser extension.API test records
ShnDock records TTFT, total latency, output speed, failure classification, request diagnostics, and token-usage source.
Plaintext API keys are not written into test records. Test results are for diagnosis and comparison, not billing.Provider / Prompt / Skill
These assets are created, edited, imported, exported, or deleted by the user in the desktop application.
They are not stored by the website and are not automatically published to any public platform.Export files
.sapi re-encrypts API card data with a user-provided password; .shndock-backup is used for encrypted full workspace backups.
Users are responsible for storing export files and passwords. Recovery cannot be guaranteed if the password is lost.API keys
API keys remain on the user device by default. ShnDock uses Electron safeStorage to store keys through system-level local encryption. When a saved card is used for testing, the renderer passes only the cardId; the main process decrypts the key and sends the request to the endpoint configured by the user.
API keys are not uploaded to the ShnDock website, written into benchmark history, logs, reports, Skill Packs, or the browser extension, and are not synchronized through the website to any third-party platform.
Third-party interfaces
API test requests are sent to the official endpoint, relay, local model service, or custom provider selected by the user. Third-party providers may process request content, logs, account information, rate limits, billing data, and compliance obligations according to their own terms.
Users must confirm that they are authorized to use the relevant API keys and endpoints and must comply with provider terms and applicable laws.
Exports and backups
.sapi is used for cross-device API card migration and is re-encrypted with a user-provided password. .shndock-backup is used for encrypted full workspace backups.
Users are responsible for storing export files and passwords. Weak passwords, leaked passwords, compromised devices, or disclosed backup files may increase risk.
Update checks
The ShnDock desktop application checks for updates by reading https://shndock.com/releases/latest.json. The first update-check implementation does not require an account and does not upload API keys, providers, prompts, Agent Skills, benchmark history, logs, local paths, or device identifiers.
Browser extension
The browser extension is a beta companion feature for reading public card metadata through local loopback. It does not read API keys stored by the desktop application and should not receive plaintext keys from the desktop application.
Deletion and uninstall
Users can delete API cards, providers, prompts, Skills, and API test records inside the desktop application. Uninstalling the application does not necessarily delete all local data, export files, downloaded installers, or user-created backups.
Terms and disclaimers
The Terms of Service and Disclaimer further explain third-party services, benchmark results, unsigned builds, and local environment risks.
Users must ensure that they are authorized to use any API key, model endpoint, relay service, local model service, or custom provider configured in ShnDock, and must comply with the applicable provider terms, network service rules, and laws in their jurisdiction.
Users are responsible for API keys, provider configuration, prompts, Agent Skills, exported .sapi files, .shndock-backup files, and the content of test requests stored or processed on their own devices.
The official website provides product information, download entry points, Release JSON, platform status JSON, release records, and legal documents. The first desktop release only directs users to the official download page for updates and does not perform silent installation or forced updates.
ShnDock API test results are affected by network conditions, local devices, providers, models, concurrency, rate limits, and provider policies. They are intended for diagnosis, comparison, and review.
Token, speed, and usage data prefer provider-reported usage when available. If the provider does not return usage data, ShnDock may use local estimates. Local estimates are not bills, settlement records, or proof of provider accuracy.
ShnDock does not control the availability, response quality, pricing, logging, billing, rate limits, account restrictions, or service terms of third-party providers, relays, or model services.
Public contact channels
- Author site · shinning.pro
- GitHub · https://github.com/Shinning1010
- X / Twitter · https://x.com/Shinning1010