Do not take our word

Take the File.

The evidence standard defines what engineering, privacy, security, procurement and legal reviewers should receive—not merely what a vendor should claim.

Evidence-pack contents

What the reviewer should inspect.

  1. Use & boundaryPurpose, recipients, processing location and criteria.
  2. Privacy specificationUnit, mechanism, parameters, bounds and composition.
  3. Utility resultsStructural, statistical and downstream task performance.
  4. Failure analysisFailed thresholds, degraded groups and unsupported uses.
  5. Release recordApprovals, versions and identifiers.
Finding language

Conclusions stay bounded to the task.

Fit for defined purpose

Agreed criteria were met.

Fit with conditions

Criteria were met subject to limitations.

Does not meet criteria

One or more thresholds failed.

Not assessable

The evidence does not support a defensible conclusion.

Publication discipline

No empty proof buttons.

A public reference pack should appear only after a real workload has been frozen, measured against pre-agreed criteria, reproduced, reviewed and published with weak results and limitations included.

Minimum reference set
  • Complete privacy definition
  • Utility–privacy trade-off
  • Structural, statistical and task results
  • Disclosure and attack testing
  • Ledger extract and reproducibility identifiers
  • Known limitations

Ask for the files behind the claim.

Request the current evidence status, pack schema, ledger specification and limitations statement.

Custom assessmentEvidence-backed scopeClear next step
Request assessment