WebSense AI — Privacy Policy

We respect your privacy. Here's exactly what we do and don't do.

Effective Date: July 2025  |  Last Updated: July 2025  |  Version: 1.7.0

Summary: WebSense AI stores all data locally on your device. We do not operate any servers, do not collect personal information, and do not track you. The only external communication happens when you choose to use OpenAI's API or configure a webhook — and those go directly to the services you configure, never through us.

1. What Data the Extension Accesses

WebSense AI accesses the following data solely to provide its core functionality of monitoring web page changes:

  • Web page content (text): When you select an element to monitor, the extension reads the text content of that specific CSS selector from the target web page. This is used to detect changes over time.
  • Page URLs: The URLs of pages you choose to monitor are stored so the extension knows which pages to check.
  • User settings: Your preferences including check intervals, notification settings, webhook URLs, and optionally your OpenAI API key.

2. How Data Is Stored

All data is stored locally on your device using Chrome's chrome.storage.local API. This includes:

  • Monitor configurations (name, URL, CSS selector, check interval)
  • Change history (before/after text content, AI-generated summaries)
  • User settings and preferences
  • AI usage counters

We do not operate any servers. No data is transmitted to or stored on any server owned or operated by WebSense AI.

3. Third-Party Data Sharing

WebSense AI does not sell, share, or transfer your data to any third party. However, the following optional features involve external communication that you initiate and control:

  • OpenAI API (optional): If you provide your own OpenAI API key, the extension sends the before/after text content of detected changes to OpenAI's API (api.openai.com) for AI-powered analysis. This only happens when you have entered an API key. The data is sent directly to OpenAI and is subject to OpenAI's Privacy Policy.
  • Webhook notifications (optional): If you configure a webhook URL (Slack, Discord, DingTalk, Feishu, WeCom, or custom), change notifications are sent directly to the webhook endpoint you specify. We have no access to these transmissions.

4. What We Do NOT Collect

  • Personal identification information (name, email, address, age, ID)
  • Health, financial, or authentication information
  • Personal communications (email, messages, chat)
  • Location or GPS data
  • Browsing history beyond the specific URLs you choose to monitor
  • User activity such as clicks, mouse movements, or scroll behavior
  • Analytics, telemetry, or usage tracking data of any kind

5. Permissions Explained

  • storage: Store monitor configurations, change history, and settings locally.
  • alarms: Schedule periodic checks for monitored pages.
  • notifications: Show desktop alerts when changes are detected.
  • activeTab: Access the current tab for element selection when you click "Monitor This Page".
  • scripting: Inject the element picker and content extraction scripts into web pages.
  • tabs: Find open tabs matching monitored URLs and create background tabs for dynamic page rendering.
  • offscreen: Parse fetched HTML using DOMParser without a visible tab.
  • host_permissions (<all_urls>): Fetch content from any URL the user chooses to monitor.

6. Data Retention and Deletion

All data is stored locally and persists until you take action:

  • Deleting a monitor also deletes its change history.
  • Uninstalling the extension removes all stored data.
  • You can clear all data at any time through Chrome's extension management.

7. Remote Code

WebSense AI does not load or execute any remote code. All JavaScript is bundled locally within the extension package. No external scripts, CDNs, or dynamically loaded code are used.

8. Children's Privacy

WebSense AI is not directed at children under 13. We do not knowingly collect any information from children.

9. Changes to This Policy

If we update this privacy policy, the changes will be reflected on this page with an updated effective date. Significant changes will be communicated through the extension's update notes.

10. Contact

If you have questions about this privacy policy, please open an issue on our GitHub repository or contact us at the email address listed on our Chrome Web Store listing.