Privacy

Privacy Policy

Last updated: April 23, 2026.

This policy explains how Internet Health Check handles information in the Chrome extension and this web portal. It is written to match the current system behavior as implemented today.

1. What the extension stores locally

The extension stores its monitoring data in chrome.storage.local inside your browser profile. That local data can include settings, license state, samples, events, health summaries, and related metadata used to power the popup and dashboard.

• Connection status and latency samples
• Event history such as outages, recovery, unstable periods, and IP change events
• Configuration such as check interval, endpoint choice, notifications, theme, badge mode, and retention settings
• Local Pro activation details such as license key, plan, expiry, and device activation identifier
• Optional JSON backup and restore data if you export or import it yourself

This local monitoring history is not automatically uploaded to this web portal by the current system.

2. Network requests made by the extension

The extension performs network checks against the configured test endpoint. By default, that may include Google connectivity or Cloudflare. If Pro features are enabled, you may also configure custom endpoints or additional targets.

The extension may also request your public IP address from https://api.ipify.org when the network is available. That value is used for display and diagnostics such as IP change detection.

If you run the speed test, the extension sends download and upload test traffic to Cloudflare speed test endpoints.

3. What the web portal stores

The web portal stores information required for pricing, license management, checkout fulfillment, support, and administration. Depending on your use, that may include:

• Name and email address entered during checkout
• Selected plan and license status
• License key, activation timestamps, and device activation identifiers submitted during license verification
• Stripe-related identifiers such as checkout session, customer, subscription, and order references
• Support request details, including email, optional license key, subject, and message
• Administrative changes to license records

4. Payments

Payments are processed by Stripe Checkout when Stripe is configured. The portal receives the checkout result and related identifiers needed to create or update a license after a successful webhook event. The current system does not store full payment card details.

If Stripe is not configured in a development environment, the checkout flow can create a local test license without real payment processing.

5. How information is used

Information is used to operate the service, verify licenses, provide paid features, process checkout events, respond to support requests, and administer the system.

6. Sharing and processors

The current system may involve third-party services that process data as part of normal operation, including:

• Stripe for payment checkout and subscription events
• Hosting and infrastructure providers used to run the web portal
• Google connectivity, Cloudflare connectivity, Cloudflare speed test, ipify, and any custom endpoint you configure in the extension

7. Retention

Local browser monitoring data remains under the user's control and follows the retention settings enforced by the extension. Free mode is limited to shorter retention, while Pro may allow longer retention.

Portal-side license, support, order, and event records are retained until removed or replaced by the operator. If the portal is deployed using ephemeral storage, records may also be lost between deployments or cold starts.

8. Security

The system uses bearer-style admin token protection for admin APIs and stores extension data locally in the browser. No system can guarantee absolute security, and you should avoid submitting secrets in support messages unless necessary.

9. Your choices

• You can uninstall the extension or clear browser extension storage to remove local data from your browser profile.
• You can choose whether to purchase Pro and whether to submit support requests.
• You can request deletion or correction of portal-side support or license records by contacting support through the support page.

10. Contact

For privacy or support questions, use the support page available in this portal.