---
title: "Privacy audit of outbound traffic"
description: "A source audit of what the Pentester workbench sends off the machine: no analytics, update checks or relays, and the traffic a scan needs, documented."
canonical: "https://getpentester.com/changelog/privacy-audit/"
published: "2026-11-18"
updated: "2026-11-18"
---

# Privacy audit of outbound traffic

Pentester's outbound traffic was audited at the source level, dated 2026-11-01. The audited workbench sends no analytics, runs no update checks and has no cloud or feedback relays, and the traffic a scan needs is documented.

## What does it not send?

No product analytics or telemetry, no release update check or self-update, no cloud uploads, no email report relay, no feedback upload and no viewer beacons. Model requests carry no attribution headers.

## What remains?

Model requests to the provider selected for the workspace, and tool traffic to your targets. Package and image registries are contacted only during explicit setup and builds.

## How is it checked?

Regression tests block and record sockets and DNS before the engine imports: zero attempts are allowed. The code paths that once could send analytics, relay reports, upload to a cloud or update the app run with HTTP forbidden. It is a source audit, not a guarantee about every binary. For engagement policies, see [Trust and data handling](https://getpentester.com/security/).
