Cliplane privacy

Clipboard history is sensitive. Cliplane treats it that way.

Cliplane keeps clipboard history local by default, gives you app exclusions and deletion controls, and avoids sending clipboard contents through support or diagnostics by default.

Local by default

Cliplane does not require cloud sync or an account for core clipboard history.

Encrypted local payloads

Clipboard payloads are protected locally with app encryption material stored through macOS Keychain APIs.

No raw clipboard diagnostics

Diagnostics use operation names, statuses, counts, and safe metadata instead of raw clipboard text, image bytes, file names, or copied URLs.

Privacy-safe support

Feedback email drafts include app, version, and macOS context, and explicitly do not attach clipboard history.

Policy notes

How Cliplane handles private clipboard workflows

Clipboard history stays local by default

Cliplane is designed as a local-first Mac clipboard app. Core clipboard history does not require an account, hosted sync, or a web dashboard.

Local payloads use app encryption

The app stores clipboard payloads locally and protects them with encryption material handled through macOS Keychain APIs. Decrypted content is used only for the requested app operation, such as preview, copy, paste, or restore.

App exclusions are checked before saving

You can exclude sensitive apps from future capture. Copies from excluded apps are rejected before clipboard payloads, previews, or searchable rows are saved.

Deletion controls remove stored content

Cliplane includes controls to delete individual clips, clear scoped history, or clear all local content. Deleted clips are not returned in search results.

Diagnostics avoid raw clipboard data

Diagnostics are limited to privacy-safe information such as operation names, statuses, counts, clip kinds, and generic error context. Raw clipboard text, image bytes, copied file names, copied URLs, search queries, tokens, passwords, and full local user paths are not diagnostic payloads.

Feedback email is privacy-safe by default

Feedback drafts go to [email protected] and include app, version, and macOS context when available. They do not attach clipboard history, screenshots, diagnostics, clip IDs, database paths, or backup paths.

Backups are local controls

Backup and recovery features are designed for local archives and privacy-safe manifests. Backup rows and diagnostics should not display clipboard text, image payloads, or private copied content.

Need help with a privacy question?

Tell us what you are trying to understand without pasting sensitive clipboard contents into the message.