// LEGAL

Privacy Policy

NetRecon · Last updated March 2026

Short version: NetRecon collects nothing about you. All processing happens on your machine via a local companion server. The extension only connects to localhost:31337.

What NetRecon collects

Nothing. NetRecon does not collect, store, or transmit any information about you, your browser, your identity, or your browsing activity. There are no analytics, no error reporting, no crash logs, and no telemetry of any kind.

How data flows

NetRecon is split into two parts: the Chrome extension (the UI) and the companion server (a Node.js process running on your machine). All communication between them happens over localhost:31337 — it never leaves your device.

When you run a scan, the target you enter is sent to the companion server, which performs the operation and returns results. Nothing leaves your machine except the specific external API calls described below.

External API calls

Some tools make outbound requests to third-party services. These calls are made by the companion server (not the extension), include only the target you entered, and contain no identifying information about you:

Tools that operate entirely locally (Nmap Scanner, Port Scanner, DNS Recon, WHOIS, SSL/TLS Inspector, HTTP Headers) make no external connections beyond the target you're scanning.

Scan history

Scan results and history are stored in chrome.storage.local — local browser storage on your device. This data never leaves your machine and is not accessible to any server or third party. You can view, export, or clear your history at any time from the History tab.

Permissions explained

NetRecon requests no permissions to read your tabs, access your cookies, see your browsing history, or inject scripts into web pages.

Third-party services

The services contacted during scans have their own privacy policies. NetRecon does not control those services and is not responsible for their data practices.

Contact

Questions about this policy? Get in touch.