What Clipplane handles
Only an explicit click, context-menu command, or confirmed Element selection starts a capture. The extension may process the chosen page title, selected or extracted body, useful links, capture method, and a sanitized source URL.
Clipplane records local history only for pages you explicitly clip. It does not read your general browser history, watch the clipboard, track engagement, or collect analytics.
What stays on your computer
The Native Host writes the confirmed capture into the notes folder you choose. Local capture bodies and the capture trail remain on your computer. Settings and consent metadata stay in extension or Host storage as required to operate the feature.
When content leaves the computer
External sync is disabled by default. A capture is sent to Notion or flomo only after you configure that destination, explicitly accept the per-destination disclosure, and choose Save + sync. Clipplane does not run background or scheduled sync.
- Notion receives the captured title, body, source link, and Clipplane metadata required to create the page.
- flomo receives the captured content through the official incoming webhook configured by you.
Those providers process data under their own terms. Clipplane does not proxy this traffic through a Clipplane server.
How credentials are handled
A Notion token or flomo webhook is passed to the local Native Host and stored in the operating system credential store. It is not stored in extension storage, logged, included in Native Messaging responses, or sent to Clipplane.
Uninstalling the Host removes the two Clipplane external-service credentials by default. Local notes are preserved. The uninstall helper also offers an explicit option to preserve credentials.
Retention, deletion, and human access
You control the notes directory and can edit or delete its files with ordinary local tools. In Capture History, Mark processed removes the matching bounded entry from inbox.md while retaining the local history record and Markdown source snapshot. Delete local copy removes the Inbox entry, history record, source snapshot, and Clipplane-managed local-export copy together. If an Inbox entry was removed manually, History reports it as missing and lets you finish cleanup instead of treating the edit as a permanent deletion. A 0.7.x migration retains the previous Org Inbox at its original location as read-only migration evidence and at .clipplane/backups/inbox-v2.org. Copies already sent to Notion or flomo must be deleted through that service.
Copy for Agent copies a title, sanitized source, and local Markdown path. Copy diagnostics copies compatibility facts only; neither action silently sends data over the network.
Clipplane has no remote copy to retain or inspect. It does not sell captured data, use it for advertising or credit decisions, or make it available for human review.
Browser permissions
activeTab and scripting allow capture only after an explicit action on the current tab. contextMenus provides the save commands. nativeMessaging communicates with the installed local Host. storage keeps extension settings and recent result state. Clipplane does not request broad site access.
Use on normal web pages only. Browser internal pages, the Chrome Web Store, and isolated cross-origin frames cannot be captured.