Input data and information sources
Pleadings, applications and correspondence also come from parties and people outside the organisation. The system specifically searches for names, addresses, dates of birth and other personal information.
Also known as: Automated anonymisation, PII redaction
The system finds names, addresses and other personal information in documents and suggests redactions for a person to approve.
Understand the use case
Courts in Baden-Württemberg and Hesse use this approach to anonymise judgments before publication. Amsterdam uses it to redact documents released in response to access requests.
This page describes a typical system design. Actual data flows and permissions depend on your implementation.
System design and data flows
A judgment, file or other document is to be published or released.
Pleadings, applications and correspondence also come from parties and people outside the organisation. For scanned documents, the system analyses images and text together to place redactions correctly.
A detection model searches for names, addresses and other information that identifies a person.
A detection model marks passages or image regions that can be linked to individuals. An editing component replaces or removes the selected areas. Detection, suggestions and effective technical removal are separate steps; a visible black rectangle alone does not tell you which data remain in the file.
The system suggests redactions or placeholders for a staff member to review and approve.
The result describes the defined model task. A match, category or forecast acquires its professional significance only in conjunction with the underlying data and intended use.
The edited document is published or released to the requesters.
Integration determines whether the result is simply displayed, adopted after approval or written directly into a business application. These variants differ in their data flows and permissions.
Explore the system design: Select a component to see its task, incoming and outgoing data, and role in the use case. The guided walkthrough explains each phase. Then use Yes, Uncertain and No to represent your specific system variant.
5 review first17 clarify8 baseline threats
The diagram shows the typical architecture. Select a component to see what happens there and adapt its features to your system. Enable “Analysis guidance” to see which threats need reviewing for this architecture. The page's checklist continues to describe the typical case.
None yet. Each change will appear here.
In this system design: 5 to review first, 17 to clarify, 8 baseline threats.
External access: Depends on your system
To clarify
Input: Part of every AI system
Review first
To clarify
Baseline for every AI system
Third-party content: Present
AI model: Part of every AI system
To clarify
Baseline for every AI system
Provider service: Depends on your system
To clarify
Training and feedback: Present
Review first
To clarify
Result: Part of every AI system
To clarify
Baseline for every AI system
Business application or equipment: Depends on your system
To clarify
person: Part of every AI system
Review first
Unapproved AI services: Depends on your system
To clarify
Supply chain and technical foundations: 5 baseline threats applying to every AI system
Baseline for every AI system
Intelligent document processing (IDP)
Extracts information from documents and transfers it to a case management system
E-discovery and technology-assisted review (TAR)
Sorts large collections by relevance to an investigation, with redaction only as a secondary function
Pleadings, applications and correspondence also come from parties and people outside the organisation. The system specifically searches for names, addresses, dates of birth and other personal information.
The model processes the inputs. Whether it runs internally or with a service provider must be established for the specific implementation.
Some deployers further train detection using their own judgments or files. Corrections made during approval can feed back as new training examples.
Depending on the workflow, redactions take effect immediately or only after approval; JANO and Amsterdam both require human approval. With a cloud service, documents leave the organisation's environment before they are redacted.
Using a provider does not automatically determine where processing takes place. Storage location, subcontractors, deletion periods and use for training must be checked for the specific deployment.
Assess risks and determine measures
Record data, participants, interfaces and permissions. Resolve uncertain characteristics in the model.
Relate review candidates to actual data flows: what could happen, and who would be affected?
Assess impacts and likelihood in the deployment context. The number of review candidates is not a risk score.
Select appropriate controls, assign responsibilities and define effectiveness checks. Document residual risks and approvals.
A total of 30 threats from the threat catalogue may be relevant to this use case.
Sensitive Information Disclosure
The system misses an unusually spelt name or information in a footnote. The document is published and the person can be identified.
Names are redacted, but occupation, place of residence and the time of the offence remain. Comparing the published judgment with other sources can still identify the person.
Most suggestions are correct, so approval becomes routine. Missed passages are then discovered only after publication.
Targeted Poisoning / Label Poisoning
Falsified training labels can deliberately shift model outputs.
Listed because of this characteristic
Exfiltration from ML Application
Protected data can leak through tools, network connections, storage or insiders.
Listed because of this characteristic
Up to 17 further threats may apply, depending on your system design. Nine threats need to be reviewed for every AI system. One of these is particularly important here and is therefore listed above.
Each Yes adds further threats to your checklist, up to 17 in total. If you cannot yet answer a question, include its threats in your review.
How your system is built
How you operate the system
Traditional methods only mark passages. If a language model inserts substitute terms or rewrites passages, it generates text itself.
If yes, add
If a language model is involved, it may also follow instructions embedded in the document.
If yes, add
Depending on the workflow, redactions take effect immediately or only after approval; JANO and Amsterdam both require human approval.
If yes, add
Some deployers further train detection using their own judgments or files.
If yes, add
If yes, add
Corrections made during approval can feed back as new training examples.
If yes, add
For scanned documents, the system analyses images and text together to place redactions correctly.
If yes, add
These questions arise for almost every AI system.
If yes, add
If yes, add
If yes, add
If yes, add
If yes, add
Measures for the priority review areas are expanded. Each linked measure explains how to implement it.
Controls for the remaining threats are available on their pages in the threat catalogue.
Applies if staff or appointed representatives operate or use AI systems.
Applies since 2 February 2025.
Detailed obligations
The system prepares judgments for publication. It does not help courts establish facts or interpret legal provisions.
Detailed obligations
Classify your system with the quick checker All obligations in the obligations compass
Review these threats for every AI system, whatever its purpose.
If any of these features does apply to your system, add the listed threats.
Does the system generate or edit images, sounds, voices or videos?
If yes, add
Does the system create new content from open-ended requests that people read, see or hear directly? Translation, reading aloud and transcription do not count.
If yes, add
Does the system search its own collection of documents or records for relevant content?
If yes, add
Does the system formulate answers from retrieved documents?
If yes, add
Does the system use a knowledge graph storing concepts and their relationships?
If yes, add
Does the system remember content from earlier conversations or tasks and reuse it later?
If yes, add
Does the system call other programs, interfaces or search services itself, even if only to read?
If yes, add
Does the system determine its next steps itself based on earlier results?
If yes, add
Does the system delegate tasks to other AI agents or incorporate their results?
If yes, add
Is the system connected to tools or data sources through the Model Context Protocol (MCP)?
If yes, add
Do documents from several customers, departments or permission groups share one search store?
If yes, add
Can people outside your organisation use the system, including without login?
If yes, add
Does the system generate code, scripts or database queries for further use?
If yes, add
Does the system execute programs, scripts or commands itself?
If yes, add
Is the system intended to maximise a specified metric, such as revenue, utilisation or clicks?
If yes, add
Baden-Württemberg Ministry of Justice and Migration, New AI tool for the judiciary
Since 12 December 2025, JANO has been available to all civil divisions of the ordinary courts in Baden-Württemberg; staff review and approve its suggestions.
Hessian Ministry of Justice, Hesse and Baden-Württemberg to use JANO AI tool in the judiciary
Hesse initially uses JANO at Darmstadt Regional Court; court staff review and approve the suggestions.
Dutch Algorithm Register, Anonimiseringssoftware, Gemeente Amsterdam
The city automatically redacts personal data in documents.
Updated: 30 September 2026. Review checklist rules version 0.3.2, threat catalogue version 2026.10.24.2. How these pages are structured