ExtHub

DevPulse — Privacy Policy

Last updated: February 13, 2026
The short version
DevPulse does not collect, transmit, or share any personal data. All performance metrics are computed locally and never leave your browser. Premium features use ExtensionPay for payment processing only.

What data does DevPulse store?

DevPulse stores the following data locally on your device using browser storage APIs:

  • HUD position and collapsed state — stored in page localStorage to restore your layout preferences on the current page
  • Theme preference — your chosen theme (dark, light, or system) stored in page localStorage
  • HUD active state — stored in page localStorage for localhost auto-restore functionality
  • Premium status — whether you've purchased premium features, cached in chrome.storage.local for faster loading

This data never leaves your browser. It is not transmitted to any server, third party, or external service (except ExtensionPay for payment verification — see below).

What data does DevPulse collect?

None. DevPulse does not collect any personal data, usage data, analytics, or telemetry of any kind. Performance metrics (FPS, DOM count, memory, Web Vitals, network stats) are computed in real-time inside your browser tab and are never recorded or transmitted.

Permissions

DevPulse requests the following Chrome permissions:

  • activeTab — to inject the performance HUD overlay into the current tab when you click the toolbar icon
  • scripting — to execute the HUD content script on the active page
  • storage — to save your premium subscription status locally on your device

DevPulse does not use the <all_urls> permission and cannot access any page unless you explicitly activate it by clicking the toolbar icon. The only exception is localhost and 127.0.0.1, where a content script runs automatically to support HUD persistence across page reloads during local development.

Premium features (optional)

If you purchase premium features ($2.99 one-time), DevPulse unlocks:

  • Memory monitoring — reads JS heap size from the browser's Performance API, processed locally
  • Long task detection — uses PerformanceObserver locally, no data transmitted
  • Network overview — reads resource timing entries locally, no data transmitted
  • Core Web Vitals (FCP, LCP) — uses PerformanceObserver locally, no data transmitted
  • JSON export — generates a snapshot file that downloads directly to your device

All premium metric collection happens entirely within your browser tab using standard Web APIs. No data is sent to any server.

Third parties

ExtensionPay (for premium features only):

  • Used for payment processing and premium feature verification
  • Processes payment information through Stripe
  • Their privacy policy: extensionpay.com/privacy

DevPulse does not use any analytics tools, advertising networks, or other third-party services.

What DevPulse does NOT do

  • ❌ No tracking or analytics
  • ❌ No data collection or transmission
  • ❌ No ads or advertising networks
  • ❌ No cookies
  • ❌ No access to page content, form data, or passwords
  • ❌ No browsing history access
  • ❌ No background network requests (except ExtensionPay verification)
  • ❌ No persistent content scripts on non-localhost pages

Changes to this policy

If this policy changes, the updated version will be published at this same URL with an updated date.

Contact

Questions? Reach out at 5797565@gmail.com