Evidence before claims

FilePreflight release evidence

A public status page for local-processing, format coverage, conversion quality, and post-check claims.

Evidence pending

The Windows release is available; public evidence records are still pending.

This page deliberately separates product availability from a published verification record. A result moves to “Verified” only when the retained synthetic fixture and documented release-build run support it.

0release claims marked verified today
Product availabilityAvailable

Free is downloadable from Microsoft Store.

Network-behavior evidencePending

Method defined; release-build run not published.

Format conversion evidencePending

17 extensions released; public pass records not published.

Educational redaction demoAvailable

Synthetic PDF example; not FilePreflight output.

Method 01

Local-processing network test

The release test will monitor a clean Windows 11 x64 environment while a supported synthetic file moves through inspection, transformation, reopen, and recheck. The record will distinguish file processing from an explicit Pro purchase or license action.

  1. Establish the environment.Record the app build, OS, fixture hash, adapters, DNS state, and monitoring tools.
  2. Run the Free file path.Observe DNS and outbound connections while processing; file bytes and file-derived data must not leave the device.
  3. Separate licensing.Test an explicit Pro license action independently and confirm that no file data enters the request.
  4. Publish the boundary.Report conditions, observations, limitations, and artifacts without calling an unobserved condition “zero network.”

Result pending No pass claim is made on this page.

Method 02

Launch-format coverage

Free and Pro support the same 17 extensions with identical per-file inspection, conversion, speed, and post-verification quality. A separate public evidence record still needs a reproducible release-build result for each extension.

GroupExtensionsPublic status
Documents and Office.pdf, .docx, .xlsx, .pptxRelease test pending
Images.jpg, .jpeg, .pngRelease test pending
Text.txt, .md, .markdown, .logRelease test pending
Data and configuration.csv, .json, .xml, .yaml, .yml, .envRelease test pending

A passing record must show that the selected canary is physically absent from the output, useful content remains usable, the output reopens, the second check passes, and the original hash is unchanged.

Method 03

What a public review record should contain

FixtureSynthetic input description, hash, format, and expected finding.
TransformationSelected policy and the category removed—without exposing a usable secret.
Post-checkReopen result, second scan, output usability, and unresolved items.
BoundaryBuild, environment, known limitation, and a clear human-review reminder.

This is an evidence record for a tested path, not a safety certificate or an advanced reporting feature.

Available now

See why visual covering is not removal.

Use the synthetic two-PDF demo to compare a black overlay with a comparison file authored without the canary values.

Open the PDF demo