pseudonymization-field-mapper

When to invoke

• You need to share or analyze datasets while reducing re-identification risk.
• You need a clear, reviewable mapping from original fields to pseudonymized outputs.
• You are preparing a de-identified extract for analytics, QA, or vendor handoff.

Inputs needed

• A JSON dataset schema describing fields (name, type, examples, sensitivity tags).
• Optional policy settings:
  • Whether mapping must be reversible (tokenization) or irreversible (hashing).
  • Join requirements (which identifiers must remain linkable across tables).
  • Environment (dev/test/prod) and key management constraints.