To use these add-ons, you'll need to download Firefox.

Log in
Add-on icon

Privacy policy for ContextAI Saver

ContextAI Saver by ContextAI Saver

0 Stars out of 5
5
0
4
0
3
0
2
0
1
0
Privacy policy for ContextAI Saver

Privacy policy



Privacy Policy for ContextAI Saver Chrome Extension

Last Updated: 07.04.2025

Thank you for using ContextAI Saver (the "Extension"). This Privacy Policy explains how the Extension handles your information.

1. Introduction

ContextAI Saver is a Chrome extension designed to help you save web page content to a server location that you configure. Its single purpose is to extract the main content from a webpage you are currently viewing and send it to your specified server endpoint.

2. Information We Collect and How It's Used

The Extension handles the following types of information:

  • Web Page Content: When you activate the Extension (via button click or keyboard shortcut), it accesses the content of the currently active web page. This includes:
    • The URL of the page.
    • The title of the page.
    • The main textual and structural content of the page, extracted using the Readability library.
    • Associated metadata extracted by Readability (like site name, byline, excerpt, published time if available).
    • A timestamp of when the page was saved.
      This information is collected solely for the purpose of packaging it and sending it to the server URL you provide.
  • Configuration Data:
    • Server URL: The URL of the server where you want to save content is stored locally on your computer using Chrome's storage API. The Extension uses this URL to send the extracted web page content.
    • Last Save Status: The Extension may locally store the success or failure status and message of the most recent save attempt to display in the popup.
  • Usage Data (Indirect): The Extension uses standard Chrome APIs like activeTab, storage, commands, notifications, and scripting to perform its functions. Chrome itself may collect anonymized usage statistics if you have opted into that with Google. The Extension itself does not collect analytics or track your Browse habits beyond the specific pages you choose to save.

3. Data Transmission
  • The only time the Extension transmits data over the network is when it sends the collected Web Page Content (URL, title, content, metadata, timestamp) to the Server URL that you have configured in the Extension's options.
  • The security of this transmission depends entirely on the protocol (HTTP or HTTPS) and security configuration of your specified server. The Extension itself does not add encryption beyond what your browser and server naturally use.

4. Data Storage
  • Locally: Your configured Server URL and the last save status are stored using Chrome's local storage mechanisms on your device.
  • Remotely: The collected Web Page Content is sent to and stored on the server corresponding to the URL you provide. The Extension developers do not have access to this server or the data stored on it. Storage, management, and security of the data on your server are your responsibility.

5. Third-Party Sharing

We do not sell, trade, or otherwise transfer your information to outside parties, except for the explicit action of sending the saved page content to the server URL you configure. The Extension does not utilize third-party analytics or advertising services.

6. Your Choices
  • You can change or clear the configured Server URL at any time via the Extension's options page.
  • You can stop using the Extension at any time by disabling or uninstalling it through Chrome's extension management page (chrome://extensions/).

7. Permissions Justification

The Extension requires the following permissions for its core functionality:
  • activeTab: To access the content of the page you want to save when you invoke the extension.
  • storage: To save your configured server URL locally.
  • commands: To allow setting a keyboard shortcut for saving pages.
  • notifications: To show you success or failure messages after a save attempt.
  • scripting: To inject the necessary scripts (like Readability.js) to extract content from the active page.
  • host permission (<all_urls>): Required by the scripting permission to allow script injection on any page you might want to save, upon your explicit action.

8. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy here and updating the "Last Updated" date.

9. Contact Us

If you have any questions about this Privacy Policy, please contact us at:
Arkady.Dymkov@gmail.com