Privacy by Design

The Lansweeper Traffic sensor is an extension to Network Discovery, currently available in open beta. If you do not install it, no network traffic data is captured, transmitted, or stored by Lansweeper.

The sensor is a passive, receive-only software component that runs on your own infrastructure. It listens to the network traffic (via SPAN, RSPAN/ERSPAN, network TAPs, or a packet broker), and never injects, alters, or forwards production traffic. The only outbound activity from the sensor is throttled lookups against your own DNS servers, used to identify devices.

What the Sensor Sees

Only the connection metadata needed to identify and place devices in your inventory: IP and MAC addresses observed on the network, source and destination IPs and ports of observed connections, the date and time of each connection, and a device identifier so observations can be linked to the right asset.

What the Sensor Does Not See

In encrypted traffic — the vast majority of modern network communication — Lansweeper does not capture, transmit, or store TLS payloads, HTTPS request bodies, URL paths behind a domain, query strings, prompts, file contents, passwords, chat messages, or anything inside encrypted tunnels. Anything on segments you do not mirror is also invisible to us.

Where the Data Lives

Connection metadata is forwarded over TLS 1.2+ from your on-prem Network Discovery Hub to your Lansweeper Cloud site, hosted on AWS in the region you select (EU or US). Traffic data follows your asset-data retention policy and is fully deleted within 60 days of contract termination.

You Stay in Control

You are the Data Controller; Lansweeper is the Data Processor. You decide which segments are mirrored, traffic is shown at the device level (no user names), and your administrators can disable the sensor at any time — which immediately stops the flow of new data to Lansweeper.