PRIVACY POLICY FOR EVERCLIP
Last Updated: October 27, 2026
EverClip ("we", "our", or "the extension") is committed to protecting your privacy. This Privacy Policy details our handling of user data, explains the permissions requested by the extension, and confirms our strict adherence to the Google Chrome Web Store Developer Program Policies.
--------------------------------------------------------------------------------
1. CORE PRIVACY PRINCIPLE: 100% CLIENT-SIDE & OFFLINE-FIRST
--------------------------------------------------------------------------------
EverClip operates entirely on your local machine:
- We do NOT own or operate external servers to collect your data.
- We do NOT require user accounts, passwords, or cloud logins.
- All clipped articles, simplified text, bookmarks, tags, personal remarks, and screenshots are stored locally on your device within Google Chrome's native local database (chrome.storage.local).
- None of your saved content, notes, or browsing activity is ever transmitted to us or any third party.
--------------------------------------------------------------------------------
2. DETAILED EXPLANATION OF PERMISSIONS & WHY THEY ARE NEEDED
--------------------------------------------------------------------------------
EverClip requests only four minimal permissions in its manifest.json. Below is a transparent breakdown of what each permission does and why it is required:
a) "storage"
• Why it is needed: Allows the extension to store your clipped articles, bookmarks, notebooks, tags, personal notes, and preferences locally on your computer via chrome.storage.local.
• What it accesses: Only the local storage space allocated by Chrome specifically to EverClip. It cannot access storage or data from any other extension or website.
b) "activeTab"
• Why it is needed: Enables temporary access to the webpage you are currently viewing ONLY when you explicitly invoke the extension (by clicking the EverClip toolbar icon or choosing a right-click context menu option).
• What it accesses: Reads the active page DOM to extract the readable article text, page title, favicon, author metadata, or your highlighted text selection, and captures the visible viewport screenshot when you select Screenshot mode.
• Why this protects your privacy: Unlike broad permissions (e.g. "<all_urls>"), "activeTab" gives the extension ZERO persistent access to your browsing activity. It only activates for a single tab when you consciously ask it to clip.
c) "contextMenus"
• Why it is needed: Adds convenient right-click shortcuts in Chrome (e.g. "Clip Selected Text", "Save Page as Bookmark", "Capture Screenshot", and "Open Library") so you can capture content without opening the popup window.
• What it accesses: Only triggers the specific clipping action on the active tab upon your click.
d) "scripting"
• Why it is needed: Programmatically executes the lightweight content extractor script (content.js) into the active tab when you click "Save Clip" or choose a clipping action.
• What it accesses: Parses the article body, removes ad/sidebar clutter, and renders a floating in-page confirmation badge ("Saved to EverClip").
--------------------------------------------------------------------------------
3. ARE ALL THESE PERMISSIONS TRULY NECESSARY? (AUDIT CONFIRMATION)
--------------------------------------------------------------------------------
YES. Every single permission listed above is strictly required for the core clipping and note-saving functionality to operate. Furthermore:
• WE DO NOT USE Broad Host Permissions (<all_urls>):
We deliberately avoided requesting permission to view or modify all websites. Users are never subjected to intrusive warnings such as "This extension can read and change all your data on the websites you visit".
• WE DO NOT USE Sensitive "tabs" Permission:
We do NOT request access to your general browsing history or all open tabs. Opening the welcome page and library dashboard uses standard chrome.tabs.create without requesting the broad "tabs" permission.
• WE DO NOT USE Web Request or Interception APIs:
We do NOT request "webRequest", "declarativeNetRequest", or "cookies".
• WE DO NOT USE Remote Scripts:
100% of our code is bundled locally within the extension package. No remote scripts or CDN libraries are dynamically fetched at runtime.
--------------------------------------------------------------------------------
4. DATA COLLECTION, SHARING, AND THIRD PARTIES
--------------------------------------------------------------------------------
- Personal Data Collected: ZERO.
- Web Analytics / Telemetry: ZERO. We do not use Google Analytics, Mixpanel, Sentry, or any tracking SDKs.
- Advertising: ZERO. We do not display third-party advertisements or sell user data.
- Sale or Transfer of Data: Never. We have no access to your data, so it cannot be sold, rented, or transferred under any circumstances.
--------------------------------------------------------------------------------
5. USER DATA RETENTION, PORTABILITY, AND DELETION
--------------------------------------------------------------------------------
You maintain complete ownership and control over your knowledge base:
- Full Deletion: You can delete individual clips or all clips at any time directly inside the extension popup or the Clips Library.
- Full Portability: You can export your entire collection into clean Markdown (.md) files or structured JSON backups anytime.
- Complete Removal: Uninstalling EverClip immediately and permanently deletes all stored clips and preferences from your Chrome profile.
--------------------------------------------------------------------------------
6. CONTACT AND POLICY UPDATES
--------------------------------------------------------------------------------
We may update this Privacy Policy if future browser standards or extension features evolve. Any changes will be posted transparently in this file and on our official extension repository.
If you have questions about this Privacy Policy or EverClip's data security practices, please contact the development team through the official Chrome Web Store support tab.