Privacy Policy
Updated for the new release: October 28, 2026
The Short Version
Secret matching and dependency inventory run locally. Sieve does not operate a developer-hosted findings service or include third-party usage analytics. The new release can contact Google OSV for advisory checks with your consent, share saved evidence with an MCP client you enable, and use Apple's purchase and entitlement services. Those optional connections mean it would be inaccurate to promise that no data ever leaves your Mac.
What Sieve Stores Locally
- Findings database — A local SQLite file at
~/Library/Application Support/Sieve/sieve.dbcontaining finding metadata: rule ID, source path, redacted preview, and an HMAC fingerprint of the detected value. The raw secret value is never written to this database. - Vault entries — Secrets you explicitly store are saved in macOS Keychain under the service namespace
com.sieve.vault.macapp. Only you can read them; they require Touch ID or your Mac login password to copy. - Sandbox bookmarks — Security-scoped bookmarks are stored in UserDefaults so Sieve can access your AI tool directories across launches without asking again.
- MCP settings — Whether the MCP server is enabled, stored in
~/Library/Application Support/Sieve/mcp-settings.json. - Project security evidence — Project names, selected-folder bookmarks, relative manifest paths, package names and versions, advisory matches, coverage warnings, check history, comparison summaries, and monitoring preferences are saved locally. Storage paths may be inside the app's macOS sandbox container.
What Sieve Never Does
- Does not upload source files, environment-file contents, or vault values for OSV dependency checks
- Does not send findings to a developer-operated cloud dashboard
- Does not collect usage statistics
- Does not use third-party analytics SDKs
- Does not store raw secret values anywhere except macOS Keychain
- Does not sync data to iCloud
Optional OSV Advisory Checks and Monitoring
With per-check consent or per-project monitoring consent, Sieve sends supported public package names, versions, and ecosystem identifiers to Google's OSV advisory service. It does not send source code, project-folder paths, environment files, or secret values in those requests. OSV also receives ordinary network-request information such as your IP address. Its handling is governed by the service provider's policies. Private or unsupported coordinates are skipped and reported as coverage limitations rather than uploaded.
Monitoring repeats these requests at the selected interval while Sieve is running and the Mac is awake. Turn monitoring off in the project's controls to stop scheduled requests. Existing saved results remain on your Mac.
The MCP Server and Your AI Provider
The local sieve-mcp server communicates over standard input/output; it does not open a public network port. Project sharing requires a separate global sharing switch. When enabled, a connected client can read saved project names, relative manifest paths, package names and versions, advisory findings, coverage, and check summaries. The connected assistant may send these responses to its model provider under that provider's policies. Local transport does not mean the assistant keeps the responses on-device.
Read-only project tools do not run scans or fixes, grant folder access, or return raw secrets. Other secret-related MCP tools have separate controls; vault-injected command execution is a distinct, sensitive permission. Disable project sharing to revoke project-tool access.
Purchases
Apple processes App Store downloads, in-app purchases, and restore requests. Sieve uses StoreKit to verify entitlement and product information; the developer does not receive your payment-card details. Apple may process purchase and account information under its own privacy policy.
This Website's Limited Analytics
The Sieve landing page records page visits and App Store-link clicks in the developer's existing PostHog project, relayed through VibeScan. It sends only an event name, fixed referral labels, and a random identifier that lasts for the current page document. No cookies, persistent visitor IDs, cross-site identity linking, session replay, form contents, full URLs, app findings, or vault data are collected by this script. These counts measure landing instances and outbound intent, not unique people, installs, or purchases.
The relay and its hosting provider receive ordinary request information such as IP address for delivery and abuse prevention. The relay does not forward the visitor's IP, browser user-agent, or referrer to PostHog and disables person profiles and GeoIP enrichment for these events. The script honors Global Privacy Control and Do Not Track. Privacy and support pages do not run it. The app's no-usage-analytics statement above applies to the Mac app, not these limited website events.
File Access
Sieve uses Apple's security-scoped bookmarks to read AI tool directories you grant access to via the standard macOS Open dialog. Access is limited to the specific folders you select. Sieve requests read-only access to these paths and does not write to them (except when you explicitly use the SQLite redaction feature, which creates a backup first).
Deletion
To remove all Sieve data:
- Turn off project monitoring and MCP sharing before removing local records.
- Removing the app alone may leave its sandbox container, Application Support files, and Keychain entries. Use the app's reset controls where available, or contact support for help locating your installation's local records.
- Open Keychain Access → search for
com.sieve.vault.macapp→ delete entries — removes vault secrets
Contact
Questions about this policy: gautamumapathy@gmail.com