Webpage Change Detector

Overview

Webpage Change Detector is designed to monitor a specific part of a webpage selected by you. The extension records information needed to identify that element, stores its observed content locally, checks it according to your selected schedule, and can notify you when a change is detected.

The extension does not require an account and does not operate a developer backend, cloud database, analytics system, or remote telemetry service. The extension's monitor data remains in your Chrome profile.

Information We Store

Information associated with your monitors is stored locally in your Chrome profile using Chrome's local storage facilities. Depending on how you use the extension, this can include:

• Monitor names and settings.
• The full URL of a webpage you choose to monitor, including its path and query parameters.
• The webpage title.
• Element identification information, such as selectors, tag name, ID, classes, ARIA role or label, name attribute, parent tag, and a short text hint.
• The baseline and latest extracted text from the monitored element.
• Change history containing previous and new extracted text.
• Schedules, monitor status, notification settings, badge settings, and history settings.

A monitor draft may also be held temporarily in Chrome session storage while you are creating or editing a monitor.

Because you choose which webpage element to monitor, the information stored may include text or values that you deliberately select, including potentially sensitive information present in that element. The extension does not ask you to provide sensitive information.

How Webpages Are Accessed

When the webpage you are monitoring is open, the extension can inspect the selected element in that page to obtain its current content.

For closed-page monitoring, the extension may request the URL you selected for monitoring and parse the returned HTML to locate the monitored content. The retrieved HTML is treated as webpage data and parsed locally; the extension does not execute scripts contained in the retrieved HTML.

Closed-page monitoring may not work for webpages whose relevant content is generated dynamically by JavaScript after the initial HTML response.

Network Requests and Cookies

The extension can make a network request to a webpage that you explicitly chose to monitor when checking a closed page. That request is made to the monitored website itself. Existing cookies associated with that website may be included in the request so that the page can be accessed in the same authenticated context available to Chrome.

Those cookies are not read by the extension as cookie data, copied into extension storage, or sent to any separate service. The monitored website receives the request according to its own normal website behavior.

The extension does not follow HTTP redirects for closed-page monitoring. If a monitored request redirects, the check may fail rather than following the redirect.

Because the extension permits monitoring of HTTP as well as HTTPS webpages, a request to an HTTP URL may be unencrypted. You should use HTTPS whenever the monitored website supports it.

Third-Party Services

The extension does not use a third-party service to collect or process monitor data. When checking a webpage you selected for closed-page monitoring, it requests that webpage directly, as described above.

Permissions and Site Access

The extension uses Chrome permissions needed for its functionality, including:

• activeTab: allows interaction with the currently selected webpage when you use the extension.
• scripting: allows the extension to inspect and interact with the selected webpage element.
• storage: stores monitor configuration and history locally in Chrome.
• alarms: schedules periodic monitor checks.
• notifications: displays desktop notifications when configured.
• offscreen: supports background webpage checking where required.

The extension's optional host permissions cover HTTP and HTTPS webpage URLs (http://*/* and https://*/*) so it can check webpages that you choose to monitor. Site access is used for the origin of a webpage when you create a monitor for that site and is released when the last monitor for that site is deleted.

Data Sharing and Disclosure

We do not sell or share the extension's stored monitor data. This includes the monitor list, monitored webpage URLs, monitored webpage content, extracted text, snapshots, change history, and monitor settings or configuration.

Your monitor information is intended to remain in your Chrome profile. A monitored website may receive a normal page request when the extension checks that website, as described above. This is necessary for the monitoring functionality and is not a transfer of your stored monitor database to us.

Data Retention and Deletion

Monitor information remains in local Chrome storage until you delete the monitor, clear the extension's stored data, uninstall the extension, or otherwise remove the relevant Chrome profile data.

Deleting a monitor also releases the site's optional access when no other monitor for that site remains.

Because monitor data is stored locally, we do not maintain a separate developer-side copy that must be deleted from a server.

Security

The extension is designed to minimize data exposure by keeping monitor records locally and not operating a remote data collection backend for monitor data.

Stored extension data is not separately encrypted by the extension. It relies on the security protections provided by Chrome and the operating system for the user's Chrome profile.

The extension also applies safeguards such as bounded stored values, a minimum monitoring interval, HTML escaping in its user interface, a Content Security Policy, redirect blocking for closed-page requests, and local parsing of retrieved HTML without executing its scripts.

Children's Privacy

The extension is not directed specifically at children and does not knowingly request personal information from children.

Changes to This Policy

We may update this Privacy Policy when the extension's functionality, data practices, or applicable requirements change. The effective date at the top of this page will be updated when material changes are made.

Contact

If you have questions about this Privacy Policy or the privacy practices of Webpage Change Detector, contact:

Developer: Usman Ali
Email: mirzausmanali321@gmail.com

Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.