PRIVACY POLICY FOR PAGESAVER WE
Last Updated: October 2026
1. INTRODUCTION & CORE PRIVACY COMMITMENT
PageSaver WE ("the Extension") is dedicated to protecting user privacy. Our software is designed from the ground up on a local-first, zero-telemetry architecture.
• We DO NOT collect, store, transmit, or sell any personal data.
• We DO NOT track your browsing habits, history, or visited URLs.
• We DO NOT communicate with any external servers, third-party analytics platforms, or advertising networks.
• 100% of all page archiving, serialization, and file generation occurs strictly locally inside your web browser on your device.
2. WHAT INFORMATION WE PROCESS AND HOW
When you choose to save a web page, PageSaver WE temporarily processes the Document Object Model (DOM), images, and stylesheets of that specific page to compile them into a standalone archive file (.html or .mhtml). This processed data is converted directly into a download stream and saved to your computer's local Downloads folder. None of this content is ever transmitted across the internet.
3. DETAILED BREAKDOWN OF BROWSER PERMISSIONS
To deliver complete single-file webpage archiving without compromising your security, PageSaver WE requests the following specific permissions:
• activeTab:
Allows the extension to access and read the webpage currently open in your browser ONLY when you explicitly invoke the extension (by clicking the extension icon, pressing the keyboard shortcut, or selecting a context menu option). It gives zero ongoing access when you are merely browsing.
• scripting:
Allows the extension to inject the DOM serializer engine into the active tab. This engine reads inline stylesheets, converts visible images and canvas graphics into Base64 data strings, and synchronizes live form state into the final standalone HTML file.
• downloads:
Allows the extension to save the compiled .html or .mhtml file directly to your device's Downloads directory without requiring you to manually copy and paste code.
• storage:
Used solely to store your personal extension configuration (such as your preferred default format, custom filename pattern, and script removal toggles) and a short list of your recent saves on your local machine using Chrome's local storage API. This data never leaves your browser.
• contextMenus:
Enables convenient right-click options ("Save Page as Single HTML" and "Save Page as MHTML Archive") directly from the browser's context menu on any web page.
• pageCapture:
Utilizes Chrome's built-in native archiving engine to capture bit-perfect MHTML archives including all subresources and embedded frames.
4. ARE ALL THESE PERMISSIONS STRICTLY NECESSARY?
YES. Every single permission has been carefully evaluated to ensure strict adherence to the Google Chrome Web Store Principle of Least Privilege:
• Data Minimization: We deliberately DO NOT request broad host permissions like "<all_urls>" or permanent access to all websites. Instead, we use "activeTab", which only activates when you intentionally trigger a save.
• No Background Surveillance: The extension cannot observe tabs in the background or monitor your network requests.
• Why each is indispensable:
- Without "activeTab", the extension cannot read the contents of the page you asked to save.
- Without "scripting", the extension cannot traverse CSS rules or inline images into a single self-contained HTML file.
- Without "downloads", the extension cannot save the generated archive file to your disk.
- Without "storage", your custom settings and filename templates would reset every time you restart your browser.
- Without "contextMenus", you could not right-click on pages to save them quickly.
- Without "pageCapture", Chrome's native 100% visual fidelity MHTML format would be unavailable.
Removing any of these permissions would directly disable core archiving functionality. The current permission configuration represents the absolute minimum set required to deliver high-fidelity, single-file web archiving.
5. THIRD-PARTY SERVICES & ANALYTICS
PageSaver WE uses zero third-party libraries, analytics engines (such as Google Analytics or Mixpanel), or remote CDN dependencies. The extension code is entirely self-contained.
6. USER RIGHTS & DATA RETENTION
Because PageSaver WE does not collect any data on remote servers, there is no remote data to view, export, or delete. If you wish to clear your local extension preferences and recent saves history, you can click "Clear" in the extension popup or simply uninstall the extension from your browser.
7. CHANGES TO THIS POLICY
If updates or changes are made to this policy, the updated version will be packaged with extension releases and made available through the extension documentation.
8. CONTACT
For questions or feedback regarding this privacy policy or the extension, please consult the built-in documentation page or contact the developer via the Chrome Web Store support tab.