Security & Trust Center
Your data belongs to you. We built Snipset to keep it that way: local-first storage, no telemetry SDKs, and no cloud server that stores your snippets.
bytes of snippet content stored on our servers
analytics or crash-report SDKs bundled with the app
of snippet content stored in local SQLite on your device
PBKDF2-HMAC-SHA256 iterations guarding the Vault PIN
Private by Construction
Four guarantees enforced by the architecture itself, not by policy documents.
Local-First by Default
Snippets, clipboard history, and configurations live in a local SQLite database on your machine. No account, no sync servers. Inspect, back up, or delete your data at any time.
Local AI with Ollama
Snipset talks to your local Ollama daemon on localhost, never to OpenAI or Anthropic. Text generation and semantic vector embeddings happen on your hardware, so zero bytes of source code, API keys, or customer data cross the network.
No Telemetry SDKs
No analytics scripts, no bundled crash reporters, no usage telemetry. Diagnostic logs stay on your filesystem. Crash reporting is opt-in and off by default. Routine server calls are limited to licensing and signed update checks, and the checks can be disabled.
No Keylogging
Keystroke detection runs in an ephemeral in-memory ring buffer that only checks whether recent key events match your active snippet triggers. Once matched or discarded, the buffer clears instantly. Nothing is persisted or transmitted.
Who Can Reach Your Data
Short answer: only you.
- No cloud servers store your snippet content: every snippet, prompt, and password lives on your device.
- No account, no sync infrastructure: there is no identity database to breach and no session to hijack.
- Nothing sensitive in transit by default: AI runs on localhost, and update checks can be disabled for air-gapped deployments.
Local-First Is a Moat, Not a Feature
Cloud SaaS clipboard managers must copy your keystrokes to their servers to sync them. Legacy local tools keep data on-device but ship no intelligence. Snipset does both, giving attackers nothing to steal.
| Security Property | Cloud SaaS (TextExpander / Blaze) | Legacy Local (Beeftext) | Snipset |
|---|---|---|---|
| 🔒 Breach Surface & Data Ownership | |||
| Snippet & Prompt Storage | ⚠️ Remote cloud servers | ✅ Local only | ✅ 100% Local SQLite WAL |
| Breach Surface | ⚠️ Server breach leaks snippets | ✅ Device-only data | ✅ No server copy, nothing to steal |
| Sync Telemetry | ⚠️ Active cloud sync telemetry | ✅ Zero telemetry | ✅ Zero telemetry, air-gapped |
| 🤖 Intelligence Without Exfiltration | |||
| AI Prompt Privacy | ⚠️ Cloud API calls (paid add-on) | ❌ None | ✅ Local Ollama, zero WAN bytes |
| Clipboard Manager | ❌ None | ❌ None | ✅ Built-in, password-aware |
| Secrets Vault + MFA | ❌ None | ❌ None | ✅ PIN-gated vault + TOTP |
| 🏢 Deployment & Compliance | |||
| Offline & Air-Gap | ⚠️ Degraded without internet | ✅ Full offline | ✅ Full offline, air-gap capable |
| Compliance Posture | ⚠️ BAAs + breach liability | ✅ Device-owned data | ✅ Off-endpoint liability removed |
A Built-In Vault That Never Phones Home
Passwords, 2FA tokens, and secret fields are encrypted with your OS keychain and gated by a PIN only you know.
Vault Master PIN
One PIN locks the whole vault. The PIN itself is never stored. It is verified with PBKDF2-HMAC-SHA256 at 600,000 iterations over a 32-byte random salt.
OS-Protected Storage
Vault payloads live in OS-protected secret storage (the OS keyring on Linux and Windows DPAPI), never as plaintext in the database.
Biometric Unlock
Prefer not to type the PIN? Unlock the vault with Windows Hello biometrics after the Master PIN is configured.
Built-In TOTP Authenticator
Store 2FA secrets next to the passwords they protect. Time-based codes are generated on-device alongside a strong password generator, with no authenticator cloud account needed.
PIN-Gated Everywhere
Require the PIN before the Magic Menu reveals secrets, and before any vault export. Exports stay local. There is no server to upload them to.
Password-Manager Clipboard Shield
Clipboard payloads tagged by password managers (1Password, Bitwarden, KeePass) are automatically excluded from clipboard history retention.
Trust You Can Audit
Signed updates, reviewable source, and a compliance posture that removes cloud liability instead of paperworking around it.
Signed, Checksum-Verified Updates
Release artifacts ship as signed updates with integrity checks enforced in CI. Update checks fetch the signed manifest from our update service, and they can be disabled entirely for air-gapped deployments.
GDPR, HIPAA & NDA Friendly
Regulated data processed through cloud SaaS demands BAAs and breach-liability planning. Snipset keeps that surface small: snippet content never leaves the endpoint, so there is no vendor cloud holding your data to contract with or breach to disclose. The named processors for licensing, support, and site delivery are listed in our Privacy Policy. Snipset holds no security certifications. It simply has no content cloud to certify.
Continuous Dependency Hygiene
Dependencies are scanned for advisories every week, and the full git history is secret-scanned with gitleaks before it can ship. Local secrets stay encrypted at rest with SOPS/age.
Responsible Disclosure
Found a vulnerability? Read our Vulnerability Disclosure Policy and report it through the channels it describes, never in a public issue. Include the affected component, reproduction steps, and impact.
Straight Answers
The questions investors, IT admins, and privacy-conscious teams ask us most.