Skip to content
anonymizer

Telemetry

There is no telemetry.

We don’t collect usage data, error reports, performance metrics, IP addresses, install events, country, user agent, or anything else. The redaction engine has no telemetry hooks. The web UI has no telemetry hooks. The installer has no telemetry hooks.

The only outbound request the product can make is the optional, opt-out update check — see What leaves your machine.

Why this page exists

Most software has a “we use only essential telemetry” page. We wanted to be very clear that this product has none. If you came here looking for a privacy policy line item to copy into your firm’s vendor-review checklist:

anonymizer does not collect any user data and does not send any usage information to its developers. The only optional network requests are update checks (the CLI against anonymizer.site/version.json, disable with anonymize --no-update-check or ANONYMIZER_NO_UPDATE_CHECK=1; the macOS app via its built-in updater, manual or opt-in) and language-model downloads you explicitly start. Neither carries any document or usage data — see What leaves your machine.

How we know this stays true

  • Build-time network policy test — a regression test that fails CI if any socket opens during processing
  • Readable source — the full Python source is published as sdist on PyPI alongside the wheel. You can read every line.
  • No tracking dependencies — the dependency tree is published on the licenses page. None of the listed libraries do tracking.

If the situation ever changes, it will be a major version bump (1.x → 2.x) and called out in the changelog under a “BREAKING” header.