IX / TELEMETRY-LEAK-LAB · OPEN SOURCE

Hiding a value can leave its fingerprint.

What can survive log and trace redaction, and how to check without losing useful signals.

Python · MIT22 repository testsWindows / macOS / Linux · CI ↗

01

The business question

An organization can remove a visible identifier and retain its fingerprint in another attribute. A review needs to follow the data beyond its disappearance from a screen.

02

The engineering decision

Compare before/after JSON exports using known synthetic canaries. Require a measurable baseline and surviving preservation controls.

03

What was observed

Incomplete redaction retains a SHA-256-derived identifier: LEAK. The scoped correction passes; destroying useful telemetry produces INCONCLUSIVE.

04

Where the evidence ends

This is not a universal personal-data detector. It covers known canaries and variants in the supplied JSON; it does not run a real Collector or certify anonymization.

60-SECOND WALKTHROUGH / TELEMETRY-LEAK-LAB

Hiding a value can leave its fingerprint.

  1. Choose a scenario
  2. Inspect the recorded evidence
  3. Compare correction and lost controls

Explorer of previously executed reports, using synthetic data. Switching scenarios does not run Python, scan your system or send HTTP requests.

The full report remains available below.
Inspect original JSON evidence

Executed on 19 September 2026. A PASS applies only to that configured experiment.

WHAT THIS MEANS FOR YOUR SYSTEM

From a failure to a review plan.

If your product collects logs, traces or support events, review what leaves the system and who can access it.

A proposed review could include

An inventory of capture points, review of filtering and retention, an agreed synthetic experiment and acceptance criteria for a correction.

This is a synthetic engineering case, not a client outcome. Implementation, intrusive production tests and compliance certification are outside the standard diagnostic scope.

FROM EXPERIMENT TO DECISION

Find out which boundary to review first.

The technical and strategic diagnostic turns a scoped question into a system map, prioritized findings and an actionable roadmap. Scope and access are agreed before any work.

Prepare my diagnostic ↗
Sources and reproduction

Commit a284cf80a5b4445f91beb02d7b3e90592f25faec

Download original JSON · SHA-256

4791dcb6b5b45510f58a2b11b7b10a8ae3ef275699a05f367686b02ef02349f8
git clone https://github.com/ixequiluna-source/telemetry-leak-lab.git
cd telemetry-leak-lab
git checkout a284cf80a5b4445f91beb02d7b3e90592f25faec
python -m telemetry_leak_lab demo --out artifacts

Requires Python 3.11+. Open artifacts/report.html. All data is synthetic.