NeatClipper — Last updated: June 2026
All data created by NeatClipper is stored exclusively in your browser's local IndexedDB and chrome.storage.local. This includes clipped text, links, image bytes, screenshots, folder names, your theme preference, and your last-viewed folder.
This data never leaves your device. It is not uploaded, synced, or shared with anyone — including us.
The only outbound network request NeatClipper makes is when you explicitly clip an image from a webpage. In that case, the extension fetches the image binary directly from its source URL so it can be stored locally on your device. No metadata, identifiers, or usage information are sent alongside this request.
No other network requests are made. The extension does not contact any NeatClipper-owned server at any time.
| Permission | Reason |
|---|---|
| contextMenus | Adds right-click clip options to webpages so you can save content without opening the popup. |
| scripting | Reads the selected text's HTML and a link's visible label at the exact moment you clip — runs only on explicit user action, never passively. |
| storage | Saves your preferences (theme, last-viewed folder, onboarding state) locally in chrome.storage.local. |
| unlimitedStorage | Image and screenshot binary data can exceed the default 5 MB browser quota. This permission prevents data loss when your library grows. |
| downloads | Used solely for the Export feature, which saves your clip library as a local JSON backup file to your device. |
| Host permissions | Required to inject a content script that shows a save-confirmation toast and reads page content on explicit user action. No data is collected passively. |
NeatClipper does not use any analytics, advertising, crash reporting, or third-party SDKs. No data is sold, rented, or shared with third parties under any circumstances.
You can export your entire library — clips and folders — at any time from the dashboard. Uninstalling the extension permanently removes all locally stored data from your browser.
If this policy changes, the updated version will be posted at the same URL with a revised date. Continued use of the extension after a change constitutes acceptance of the updated policy.