Practical workflows, not invented customer claims

How to evaluate Anonify in practice

We will publish customer names and results only after approval and validation. Until then, we show exactly which workflows to test and how to measure the outcome yourself.

Workflow to test

Municipality: FOI case file

Upload a representative file, flag possible personal data, review disclosure exemptions and export only after human approval.

Measure during the pilot

Missed sensitive passages
Incorrect markings
Total review and correction time

Workflow to test

Privacy team: recurring document flow

Test different document types and scan qualities in separate workspaces with the people who normally perform the work.

Measure during the pilot

Outcome by document type
Difference between good and poor scans
Time to an export ready for approval

Workflow to test

Public body: high-volume request

Run a file selection through detection, review and export while recording legal decisions outside the automation.

Measure during the pilot

Corrections by category
Time from upload to review
Reviewer experience

A reproducible benchmark in four steps

1Select 10-30 representative documents in advance and avoid test bias.
2Have an experienced reviewer create a reference set without Anonify.
3Run the same set through Anonify and record suggestions, corrections and time.
4Compare quality and total handling time by document type; do not hide weak categories in one average.

Why we do not promise a fixed accuracy rate

Detection depends on language, layout, scan quality, context and category. A legally responsible outcome requires human review. Your own representative benchmark is therefore more reliable than one marketing percentage.

Start the first month for €1