Explains the limits of erasure against legal retention
GDPR Art. 17(3)(b): erasure does not apply where processing is needed to comply with a legal obligation such as AML record keeping; the precedence is the DPO's call per record type.
Can AI do this?
AI does this partly Some of the tested AI models master this; others do not show it. 2 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 99% | Mastered |
| gemini-3.5-flash-lite | Low cost | 68% | Not shown |
| gpt-6-luna | Low cost | 99% | Mastered |
| claude-haiku-5-5 | Low cost | 76% | Not shown |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: GDPR Art. 17(3)(b): erasure does not apply where processing is needed to comply with a legal obligation such as AML record keeping; the precedence is the DPO's call per record type.
How it is assessed: Answers a written question on the erasure and retention correctly
Related knobits
Needed for
- S-110 Recognises conflicting requirements with no precedence
- S-132 Raises a requirement conflict for the owner of the interpretation
All 17 knobits of Register regulatory security requirements.
Source: Practice the stage 1 reference and review checklist rest on