pseudonymize for reversible workflows and anonymize for irreversible ones.
The Two Modes
| Mode | What happens | Can you restore originals later? | Typical use |
|---|---|---|---|
pseudonymize | Rehydra replaces detected values with placeholders and returns an encrypted piiMap | Yes | Apps, agents, and workflows that need later rehydration |
anonymize | Rehydra replaces detected values with placeholders and discards the original-value mapping | No | One-way redaction and irreversible sharing |
Shared Processing Model
Both modes use the same high-level flow:Placeholder Output
Rehydra uses XML-like placeholders so downstream systems can safely process the text while preserving structure.Choosing the Right Mode
Usepseudonymize when:
- You need to restore the original values later
- You are building an application flow around rehydration
- You want encrypted mappings for sessions or agent workflows
anonymize when:
- You want irreversible protection
- You are preparing text for one-way sharing or analysis
- You do not want to manage keys or stored mappings
Related Concepts
pseudonymize naturally connects to rehydration, encryption, and key management. anonymize is simpler, but it still depends on the same recognizers, type system, and configuration model.
Next Steps
Rehydration
Learn how reversible workflows restore original values.
Configuration
See which settings shape detection and output behavior.