SafetyClip

Product Introduction

1. Definition: SafetyClip is a native macOS clipboard manager and security utility designed for Apple Silicon and Intel processors running macOS 14 Sonoma or later. Categorized under developer tools and Mac productivity software, it records clipboard history locally while providing specialized security layers for sensitive strings.
2. Core Value Proposition: The software exists to solve the inherent security flaw in standard macOS and third-party clipboard managers: the passive logging of API keys, authentication tokens, and passwords. By combining persistent local clipboard history (accessible via ⌃⌘V) with automated secret detection, Touch ID authentication, and Secure Enclave encryption, SafetyClip ensures developers and power users can maintain a searchable copy history without exposing credentials to malicious applications or accidental AI chat paste events.

Main Features

1. Automated Secret Recognition and Masking: SafetyClip scans clipboard contents at the moment of copying against a built-in library of over 100 signature types, including OpenAI, Anthropic, GitHub, AWS, Stripe, Slack API keys, private keys, database URLs, .env lines, JWTs, and password manager outputs. Detected secrets are marked as concealed, preventing unauthorized background apps and unverified clipboard managers from indexing them.
2. Touch ID-Gated Secure Pasting: When a sensitive string (such as an API key) is copied, SafetyClip immediately flushes it from the standard system pasteboard to prevent unauthorized reads. To paste the secret via ⌘V, the user must authenticate via Touch ID. If Touch ID is disabled, the secret automatically self-destructs from memory after 90 seconds or upon manual clearing.
3. Local History and Shell History Integration: The application retains 30 days of non-sensitive clipboard history searchable via a floating panel (⌃⌘V). Additionally, it provides zsh, bash, and fish shell hooks that prevent command-line variable exports (e.g., export OPENAI_API_KEY=...) from leaking into shell history files, complemented by an audit log tracking secret lifecycle events (copied, concealed, pasted, and cleared) without storing the underlying plaintext payloads.

Problems Solved

1. Pain Point: Accidental credential leaks via copy-paste buffers. Developers frequently copy production API keys or database connection strings to configure local environments, only to inadvertently paste them into public LLM prompt boxes, terminal logs, or unencrypted chat applications. Furthermore, traditional clipboard managers expose these secrets to any background process with pasteboard read permissions.
2. Target Audience: Software engineers, DevOps professionals, system administrators, security-conscious Mac power users, and AI prompt engineers who regularly handle sensitive tokens alongside daily text snippets.
3. Use Cases:
   • Injecting an AWS or OpenAI API key into a local .env file via Touch ID authentication without leaving the key vulnerable in system clipboard history.
   • Retaining and searching through complex, multi-line prompt engineering templates across multiple applications without losing contextual history.
   • Auditing background applications via the "Leaks view" to identify which installed software packages attempt to read concealed clipboard items.

Unique Advantages

1. Strengths & Limitations (Pros & Cons):
   • Pros: Complete local-first architecture with zero telemetry, crash reporting, or user tracking; full Swift source code provided with every license for independent code auditing; lightweight memory footprint utilizing macOS native frameworks; one-time pricing model ($8 lifetime license) free of subscription tiers.
   • Cons: Limited strictly to macOS 14 Sonoma and later; requires macOS Accessibility permissions to function correctly; does not offer cross-platform synchronization (by design, to preserve local privacy guarantees).
2. Key Alternatives & Differentiation:
   • Maccy / Raycast / Alfred: While popular macOS clipboard managers offering fast search and snippet organization, they generally log all copied text uniformly unless explicitly configured otherwise, and they lack native Secure Enclave integration or automated multi-vendor API key pattern recognition.
   • Paste: A visually polished macOS clipboard manager, but operates on a recurring subscription model and stores synced history across iCloud, which introduces a broader attack surface for sensitive credentials compared to SafetyClip's local-only Secure Enclave encryption.

Frequently Asked Questions (FAQ)

1. Does SafetyClip upload my clipboard history to the cloud? No. All clipboard detection, history indexing, and encryption occur entirely locally on your Mac. The application connects to the internet strictly for monthly license validation checks and manual software updates.
2. What happens if SafetyClip fails to recognize a specific API key or password? You can manually designate any item as a secret directly from the history menu using the ⌘L shortcut, locking it behind Touch ID and ensuring identical future copies are automatically masked. You can also designate specific applications (such as banking apps or authenticator tools) to treat all outbound copies as secrets by default.
3. How do I access the full Swift source code included with my purchase? Upon completing your one-time $8 purchase through Dodo Payments, you receive immediate access to a download link, a license key, and instructions to connect your GitHub account. Connecting your account grants you private repository access to read, audit, and build the full Swift source code locally.
4. Can I use SafetyClip alongside other clipboard utilities like Raycast or Maccy? Yes. SafetyClip applies a concealed marker to sensitive items that complies with standard macOS pasteboard privacy protocols, ensuring other cooperative clipboard managers skip logging your masked secrets. If an external application attempts to read a concealed secret anyway, SafetyClip logs the event in its Leaks view.