Privacy Policy

DevPulse - Privacy Policy

DevPulse does not collect, transmit, or share any personal data. All performance metrics stay on your device.

Document status

Last updated

February 13, 2026

DevPulse computes its metrics inside your browser and keeps them there. The extension does not collect personal data or analytics. Premium payments go through ExtensionPay.

The short version

DevPulse computes its metrics inside your browser and keeps them there. The extension does not collect personal data or analytics. Premium payments go through ExtensionPay.

What DevPulse stores

DevPulse stores a few settings so the HUD behaves consistently across sessions. Those settings stay in browser storage on your device.

  • HUD position and collapsed state so the overlay can reopen where you left it
  • Theme preference for dark, light, or system mode
  • HUD active state for localhost auto-restore during development
  • Premium status cached in chrome.storage.local for faster startup

None of that data is sent to us. It stays inside your browser unless premium verification needs to talk to ExtensionPay.

What DevPulse collects

DevPulse does not collect personal data, analytics, telemetry, or usage tracking. FPS, DOM count, memory, Web Vitals, and network metrics are calculated in the active browser tab and are not uploaded anywhere.

Why DevPulse needs permissions

DevPulse asks for only the permissions required to place the HUD on the page and save its state.

  • activeTab lets the extension inject the HUD into the tab you choose
  • scripting runs the overlay code on that page
  • storage keeps premium status locally

DevPulse does not use <all_urls>. It cannot inspect or modify arbitrary pages unless you actively turn it on. The one exception is localhost and 127.0.0.1, where a small helper script supports HUD persistence during development.

Premium features

Premium is a one-time purchase. The unlocked metrics still run locally in the browser tab where the HUD is active.

  • Memory monitoring reads the browser's own performance APIs
  • Long task detection uses PerformanceObserver
  • Network overview reads local resource timing entries
  • Core Web Vitals are measured with native web APIs
  • JSON export downloads a snapshot directly to your device

DevPulse does not stream those metrics to a remote backend. They stay in the page context where they were measured.

Third-party services

DevPulse uses ExtensionPay for checkout and license verification. ExtensionPay may process payments through Stripe. Their privacy policy is here: extensionpay.com/privacy.

There are no ad networks, analytics SDKs, or extra tracking services in the extension.

What DevPulse does not do

DevPulse does not monitor your browsing history, read your form entries, capture passwords, or run persistent background tracking on ordinary websites. Outside of payment verification for premium users, it does not make hidden network requests on its own.

Changes to this policy

If this policy changes, the updated version will stay at this URL and the date at the top of the page will be updated.

Contact

If you have a privacy question about DevPulse, email 5797565@gmail.com. Adding "DevPulse" to the subject line helps us route it faster.