PagePulse Privacy Policy

Effective date: March 24, 2026 · Last updated: March 24, 2026

All your data stays on your device. Nothing is sent to any server.

1. What We Collect

PagePulse stores the following data locally on your device only using Chrome's built-in storage API (chrome.storage.local):

Monitor configurations: The URLs and element selectors you choose to monitor, along with your preferences (check interval, keywords, ignore patterns).
Text snapshots: The text content of monitored elements, stored locally for change comparison.
Change history: Records of detected changes (old and new text values with timestamps), retained for 30 days and then automatically deleted.
User preferences: Your settings such as theme choice (dark/light), notification sound preference, and diff view mode.

2. What We Do NOT Collect

PagePulse does not collect, transmit, or store:

Personal information (name, email, address, phone number)
Browsing history or browsing activity
Cookies or authentication tokens
Analytics, telemetry, or usage tracking data
Financial or payment information
Location data
Any data to external servers, APIs, or cloud services

There is no server component. PagePulse operates entirely within your browser. No data ever leaves your device.

3. Permissions Explained

PagePulse requests the following Chrome permissions, each for a specific and necessary purpose:

Permission	Why We Need It
alarms	Schedule periodic webpage checks at the intervals you configure (5 minutes to 24 hours).
storage	Store your monitor configurations, change history, and settings locally on your device.
notifications	Send you Chrome desktop notifications when a monitored element changes.
activeTab	Access the current tab to let you select an element to monitor. Only activates when you click the PagePulse icon.
scripting	Inject the element selection interface into the current page when you create a new monitor.
offscreen	Parse fetched webpage HTML to extract monitored element content. Required because Chrome service workers do not have DOM access.
Host access (optional, per-site)	Fetch the specific webpages you choose to monitor. This permission is requested per domain only when you create a monitor, never in bulk. You can revoke access at any time.

PagePulse follows the principle of least privilege. We do not request broad host permissions at install time. Host access is optional and granted per-site at your explicit request.

4. How Your Data Is Stored

Location: All data is stored in chrome.storage.local, which resides on your device only.
Encryption: Data is protected by Chrome's built-in storage security and your operating system's user-level access controls.
Retention: Change history is automatically pruned after 30 days. Monitor configurations persist until you delete them. All data is removed when you uninstall the extension.
No cloud sync: Monitor data is not synced across devices.

5. Third-Party Services

The current version of PagePulse does not use any third-party services, APIs, SDKs, or analytics platforms.

When PagePulse fetches a webpage you've chosen to monitor, it makes a standard HTTP request directly from your browser to that website. This is the same as if you visited the page yourself.

6. Data Sharing

PagePulse does not share, sell, rent, or transfer your data to any third party for any reason. There is no data to share because nothing is collected by us.

7. Children's Privacy

PagePulse is not directed at children under the age of 13. We do not knowingly collect personal information from children. Since no personal information is collected from any user, this policy applies equally to all ages.

8. Your Rights (GDPR / CCPA)

For EU/EEA residents (GDPR):

Since all data is stored locally on your device and we have no access to it, you have full control over your data at all times. You can view, modify, export, or delete all your data directly within the extension's dashboard. Uninstalling the extension removes all data.

For California residents (CCPA):

We do not sell personal information. We do not collect personal information. You have the right to know what data is collected (none by us), request deletion (uninstall the extension), and opt out of sale (nothing is sold).

9. Chrome Web Store Compliance

PagePulse complies with the Chrome Web Store Developer Program Policies, including:

Single purpose: PagePulse has one purpose — monitoring webpage elements for text changes.
Minimal permissions: Only permissions necessary for core functionality are requested.
No remote code: All code is bundled locally within the extension. No code is loaded from external sources.
Accurate description: The Chrome Web Store listing accurately describes what the extension does and its limitations.

10. Changes to This Policy

We may update this privacy policy to reflect changes in the extension's functionality. Changes will be posted on this page with an updated effective date.

11. Contact

If you have questions about this privacy policy or PagePulse:

Developer: Kelvin Nyadzayo
Email: kelvin.nyadzayo16@gmail.com
GitHub: github.com/Nyadzayo/page-pulse