When to use Obfuscator
Use Obfuscator when you need to reduce exposure of sensitive values while keeping a dataset useful for review, testing, demos, or limited sharing.
Good use cases
Obfuscator is useful when:
- a File contains names, email addresses, IDs, phone-like values, codes, dates, or other sensitive values
- another person needs the structure of the dataset but does not need the original sensitive values
- you want to keep Field names and Record counts available for review
- you need repeatable settings that can be saved in a Configuration and reused
- you want to preview how selected Fields will change before running the Tool
Examples of practical tasks
| Task | Example | Obfuscator approach |
|---|---|---|
| Prepare training data | An employee roster needs to be used in a training session. | Replace names and emails with placeholder values. |
| Prepare demo data | A customer list is needed for a screen walkthrough. | Mask names, generate fake emails, and randomize IDs. |
| Share a limited vendor File | A vendor needs file shape and sample values, not actual customer values. | Replace sensitive Fields while keeping non-sensitive Fields unchanged. |
| Test a workflow | A team needs realistic dates and numeric ranges. | Randomize dates or numbers within a reviewed range. |
| Hide direct identifiers | A membership list includes member IDs. | Generate random characters or remap whole numbers. |
When another Tool may be better
Use another WebHammers Tool when your main task is different:
| If your goal is to... | Consider this Tool |
|---|---|
| Keep or exclude Records based on Rules | Filterer |
| Standardize inconsistent values | Cleaner |
| Check values against requirements | Validator |
| Remove duplicate Records | Deduplicator |
| Understand data completeness and patterns first | Data Profiler |
Important limitations
Obfuscator output is not designed to be reversed back to the original values. Keep the original input File if you will need the original values later.
Obfuscation uses randomness for many methods. Running the same Configuration again may produce different output values. Preview the output each time you need to rely on the result.
Obfuscator changes selected Fields only. Fields that are not targeted by enabled Rules remain available in the output.