Anonymization removes or transforms personally identifiable information (PII) in training data. It reduces privacy and compliance risks, as well as the chance that a model will memorize and reveal sensitive details. section 5.1.7 section 5.11
Before using sensitive data for fine-tuning:
- Remove or anonymize PII unless its use is necessary, justified, and legally permitted. section 5.1.7 section 5.11
- Check applicable rules, including GDPR, HIPAA, and data-residency requirements, which can constrain data use and where fine-tuning occurs. section 5.11
Table 5.9 Responsible AI risks and controls in fine-tuning
|
Area
|
Key Risk
|
What to Watch For
|
Typical Mitigation
|
|
Privacy and Compliance
|
Data leakage, regulatory
violations
|
PII in training data,
unclear data ownership
|
Anonymization, consent
checks, and data residency controls
|
|
Fairness and Bias
|
Discriminatory or uneven
outputs
|
Skewed examples,
demographic imbalance
|
Dataset rebalancing, bias
tests, targeted evaluations
|
|
Safety
|
Over-compliance, harmful
responses
|
Loss of refusal behavior
after fine-tuning
|
Safety prompt sets,
refusal examples, and comparative testing
|
|
Evaluation
|
False confidence in model
quality
|
Overreliance on a single
metric
|
Mixed metrics, human
review, segmented analysis
|
|
Transparency
|
Misuse or
misinterpretation
|
Unclear limitations or
intended use
|
Model cards,
documentation, usage boundaries
|
|
Monitoring
|
Degradation over time
|
New failure modes, user
complaints
|
Logging, feedback loops,
iterative LoRA updates
|
The risk-and-control table places anonymization alongside consent checks and data-residency controls for privacy and compliance. section 5.11








