What does the anonymization claim checker produce?
Challenge unsupported anonymous-data claims using actual release bytes and explicit risk assumptions.
Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.
What do you need before you start?
- Define your exact task, source population and method.
- Keep the unchanged original files and the selected source versions.
- Review missing, invalid and unresolved facts before preparation.
What information do you enter?
Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.
- Reference. Stable reference for this exact supplied population.
- Working pack version. Customer-controlled version.
- Organization. Actual organization owning this work.
- Approved jurisdiction scope. Select and support the actual jurisdiction and instrument for each exact scope.
- Responsible reviewer. Accountable human reviewer.
- Review timestamp. Exact timestamp with seconds and confirmed offset.
- Approved task scope. Included and excluded scopes, populations, assumptions and intended use.
- Scope approval reference. Actual accountable approval reference.
- Approved method version. Actual your method and calendar assumptions.
- Method source reference. Exact original file supporting the selected method.
- Approved method source locator. Exact JSON pointer or reviewed locator.
- Method approver. Responsible human approver.
- Method approval timestamp. Approved instant no later than review.
- Scope population. Selected or declared complete supplied population.
- Declared scope count. Required for a declared complete population.
- Challenge unsupported anonymous-data claims using actual release bytes and explicit risk assumptions scope inputs. Readable named rows, exact relationships, original sources and responsible decisions.
- Release Claims. Readable named rows, exact relationships, original sources and responsible decisions.
- Evidence. Readable named rows, exact relationships, original sources and responsible decisions.
- Actions. Readable named rows, exact relationships, original sources and responsible decisions.
| Field | What to enter |
|---|---|
| ReferenceRequired | Stable reference for this exact supplied population. |
| Working pack versionRequired | Customer-controlled version. |
| OrganizationRequired | Actual organization owning this work. |
| Approved jurisdiction scopeRequired | Select and support the actual jurisdiction and instrument for each exact scope. |
| Responsible reviewerRequired | Accountable human reviewer. |
| Review timestampRequired | Exact timestamp with seconds and confirmed offset. |
| Approved task scopeRequired | Included and excluded scopes, populations, assumptions and intended use. |
| Scope approval referenceRequired | Actual accountable approval reference. |
| Approved method versionRequired | Actual your method and calendar assumptions. |
| Method source referenceRequired | Exact original file supporting the selected method. |
| Approved method source locatorRequired | Exact JSON pointer or reviewed locator. |
| Method approverRequired | Responsible human approver. |
| Method approval timestampRequired | Approved instant no later than review. |
| Scope populationRequired | Selected or declared complete supplied population.Choose from Selected records only, Declared complete population. |
| Declared scope countOptional | Required for a declared complete population. |
| Challenge unsupported anonymous-data claims using actual release bytes and explicit risk assumptions scope inputsRequired | Readable named rows, exact relationships, original sources and responsible decisions. |
| Release ClaimsRequired | Readable named rows, exact relationships, original sources and responsible decisions. |
| EvidenceRequired | Readable named rows, exact relationships, original sources and responsible decisions. |
| ActionsRequired | Readable named rows, exact relationships, original sources and responsible decisions. |
What you can download
Every result must identify its supplied facts, assumptions and unresolved items.
| Free result | Included downloads |
|---|---|
Enter your information, inspect the on-screen result and keep a browser backup. Editing and direct copies of your entered information stay free. |
These supported outputs are free. No checkout is required. |
Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.
How does the anonymization claim checker work?
- 1Define the approved scope
Reference. Stable reference for this exact supplied population.
- 2Enter task-specific evidence
Measure exact quasi-identifier equivalence-class sizes, singleton count and sensitive-value diversity in supplied local JSON/CSV. Compare only an approved minimum group size, inspect declared direct identifiers and retained linkage keys, and retain auxiliary-data, multiple-release and expert-review assumptions. These descriptive checks never prove anonymity or formal privacy guarantees.
- 3Inspect complete findings
Review all named calculations, original source bindings and unresolved findings.
- 4Keep recoverable work
Exact original bytes and unfinished strings save locally. Restore validates exact tool, revision, row shape, source hashes and history before replacement. Earlier work and purchases remain separate.
- 5Prepare the finalized pack
Prepare 7 plus selected attachments complete files, then download them free. Review the fictional sample below.
Method and sources
Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.
Common questions
What information does the anonymization claim checker need?
Enter reference. Stable reference for this exact supplied population; working pack version. Customer-controlled version; organization. Actual organization owning this work; approved jurisdiction scope. Select and support the actual jurisdiction and instrument for each exact scope; responsible reviewer. Accountable human reviewer. Define your exact task, source population and method.
What does the anonymization claim checker produce?
Challenge unsupported anonymous-data claims using actual release bytes and explicit risk assumptions. Exact named population, deficiencies and task-specific preparation rows. Seven formal/data files plus exact originals. Preference plans also include a dedicated fixture JSON file. Complete Excel/JSON, formal PDF/DOCX, findings, hashes and instructions. Full reviewed draft sections, exact population, chronology, payload and risk outcomes and accountable unresolved findings. Original bytes, unfinished drafts, strict recovery, retained events and preserved earlier work. Review unresolved findings and limitations before use.
Is this tool free?
Yes. The on-screen result and listed downloads are free. No checkout is required. Keep local backups and review the stated method and limits.
Can I use the anonymization claim checker for this task?
Challenge unsupported claims and record residual assumptions. This browser preparation compares actual supplied source bytes and your policy, method and jurisdiction assumptions. It does not determine legal applicability, authenticate reported tests, certify anonymity or secure redaction, or execute preference fixtures. Unsupported surfaces, missing populations and pending human decisions stay visible. No replay, scan, DROP access, remote AI or provider call occurs. Originals remain local. Original files are not saved to the cloud.
What still needs review?
This browser preparation compares actual supplied source bytes and your policy, method and jurisdiction assumptions. It does not determine legal applicability, authenticate reported tests, certify anonymity or secure redaction, or execute preference fixtures. Unsupported surfaces, missing populations and pending human decisions stay visible. No replay, scan, DROP access, remote AI or provider call occurs. Originals remain local. Original files are not saved to the cloud.
At most 500 rows/200000 characters per table, 20 files/10 MB each/25 MB total, 900 KB input and 8 MB output metadata. HAR has at most 500 entries. Parsed text and document surfaces are bounded.
No comparison establishes anonymous release, secure redaction, statutory applicability or actual live test results. Your operative source versions and actual evidence remain required.