PagePulse Privacy Policy

Effective date: July 27, 2026

PagePulse is a Chrome extension that monitors webpage content chosen by the user and reports matching changes. It is designed to work without an account, analytics service, advertising service, or PagePulse-operated backend.

Information PagePulse handles

PagePulse stores the following information locally in the user's Chrome profile:

• Webpage URLs and page titles explicitly selected for monitoring
• User-created pulse names and CSS selectors for selected webpage elements
• Current and previous captured webpage text or price values
• Check times, statuses, errors, change history, and unread status
• Notification, badge, interval, and history-retention settings

PagePulse uses this information only to provide its webpage-monitoring, comparison, alert, history, and backup features.

Website access and network requests

PagePulse requests website access only after the user chooses a webpage to monitor. Permission is requested for that website origin rather than being granted for all websites at installation. During scheduled or manual checks, PagePulse requests the monitored webpage and parses the user-selected element so it can compare the latest value.

These requests go directly from the user's browser to the monitored website. PagePulse does not intentionally include website login cookies in background checks and does not send monitored data to a PagePulse-operated server. Content requiring a sign-in, anti-bot verification, or client-side JavaScript may therefore be unavailable.

Data sharing and selling

PagePulse does not:

• Sell user data or monitored content
• Transfer user data for advertising, profiling, lending, or creditworthiness
• Use advertising trackers or analytics
• Send monitoring data to a developer-operated backend
• Use captured content to train AI models
• Allow the developer or other people to read locally stored monitoring data

Local storage, retention, and deletion

Monitoring data remains in Chrome's local extension storage until the user deletes an individual pulse, clears activity, deletes all data in PagePulse Settings, or removes the extension. History is limited according to the retention setting selected by the user.

Backup files

When the user exports a backup, PagePulse creates a local JSON file that can contain monitored URLs, selectors, captured text, history, and settings. The user controls that file and should store or share it carefully. Importing a backup reads the file only to restore PagePulse data in the user's browser.

Security

PagePulse uses Chrome extension storage and the browser's permission system. Supported HTTPS webpages are requested over encrypted HTTPS connections. Users should avoid monitoring sensitive content and should keep exported backup files private.

Limited Use compliance

PagePulse's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is handled only as needed to provide the extension's disclosed, user-facing website-monitoring features.

Policy changes

If PagePulse's data practices materially change, this policy and the Chrome Web Store disclosures will be updated before the new behavior is released.

Contact

For privacy questions, use the developer support contact or support link displayed on PagePulse's Chrome Web Store listing.