Forensic Analyzer — Privacy

Privacy model, limits, and safety notes for Forensic Analyzer.

Forensic Analyzer privacy model

This tool is classified as core workload and runs in On-device mode. Current status: ga (fully-functional).

What this does

  • Applies the selected transformation to the document or exported output.
  • Keeps processing local in browser when marked On-device.
  • Uses monthly local counters for usage quotas.

What this does not protect

  • It does not remove names or sensitive content visible in document text or images.
  • It does not guarantee legal anonymity or endpoint compromise protection.
  • For hybrid tools, privacy depends on explicit cloud opt-in when enabled.
  • Analysis is read-only. It does not modify the PDF in any way — use the scrubber for that.
  • Encrypted or malformed PDFs fall back to byte-level pattern matching. Coverage is reduced but EXIF markers and JavaScript signatures are still detected.
  • Printer tracking dots (Machine Identification Codes) are not detected in the current analyzer. Use the MIC decoder research tool for that — it requires high-resolution page rendering.
  • The analyzer checks PDF metadata and embedded image EXIF. It does not analyze text content for PII (names, addresses in the visible text).

Safe workflow defaults

  • Verify output manually before sharing.
  • Use security guidance at /security for higher-risk scenarios.
  • Keep original and transformed files separated to avoid accidental leaks.