Privacy Policy
Last updated: June 2026
What we collect
Nothing. PingPulse does not collect, transmit, or store any personal data on external servers. There are no analytics, no telemetry, and no tracking of any kind.
What stays on your device
- Scan results and history (saved in
chrome.storage.local) - Your preferences: theme, region, refresh interval
- Sparkline trend data per server
- Custom server entries you add manually
All of this data is stored locally and never leaves your browser. You can clear it at any time from the History panel inside the extension.
Network requests
PingPulse makes HTTP HEAD requests directly to the servers you choose to ping (e.g., 1.1.1.1, 8.8.8.8). These are standard network probes — no request body or identifying data is sent. No request data is logged or transmitted to any third party. The sole purpose is to measure round-trip latency.
Permissions explained
| "tabs" | To read the current tab URL for the "ping current tab" feature. No tab data is stored or transmitted. |
| "notifications" | To alert you locally when a server's status changes (goes down or recovers). |
| "alarms" | To power the auto-refresh feature. Alarms fire locally and trigger a new ping scan. |
| "storage" | To save your scan history, sparklines, and settings locally on your device. |
| "host_permissions" | Required to make fetch() requests to IP-based server endpoints for latency measurement. |
Third-party services
PingPulse uses no third-party SDKs, analytics platforms, advertising networks, or external APIs. The extension is entirely self-contained.
Contact
Questions or concerns? Open an issue on GitHub or email: benarushliron@gmail.com