Profiles
A profile is a saved set of identities and values supplied to the processing engine. Enter the real details you need replaced, not the replacement names you would like to see. Do not assume that leaving a detail out means the engine will find it automatically.
- Select Profiles.
- Select + New profile, unless a new profile is already open.
- Replace Profile name with a meaningful, non-sensitive name, such as
Sample household. Avoid confidential details in profile names because names become filenames and appear in the interface. - Add the relevant entries using the sections below. Scroll down to see all sections.
- Select Save near the top of the editor. Wait for Profile saved successfully before leaving the screen.
Enter identities
| Section and control | Details you can enter |
|---|---|
| People / + Add person | ID, FIRST, MIDDLE, LAST, SUFFIX, and SSN. |
| Businesses / + Add business | ID, NAME, and EIN. |
| Cards / + Add card | ID and card NUMBER. |
| Accounts / + Add account | ID, account NUMBER, and optional ROUTING number. |
Every nonempty identity entry needs an ID. Use a short, stable handle such as
person-1, business-1, or checking, not a person's name, email, or account
number. A business also needs NAME; cards and accounts need NUMBER.
For a person, supply the name parts and other details you actually want matched.
Under each person or business, you can also use:
- + Add address: fill LINE 1, LINE 2, LINE 3, CITY, STATE, ZIP, and COUNTRY as needed.
- + Add phone and + Add email: add each number or address separately.
- + Add custom property: enter an ID, optional LABEL, the original
VALUE to match, and a TYPE. The available handling hints are
string,alnum,digits,name,date, andemail;alnumis the default.
Use Remove next to the relevant row to remove an entry, then Save. Number fields accept common formatting such as spaces and hyphens; invalid characters can prevent saving. Check numbers carefully, including leading zeros.
Keep IDs stable if you want consistent generated replacements. Custom property IDs can appear unchanged in engine output, so never put sensitive information in them. The warning for an ID that looks like personal data is advisory, not a block on saving. Custom entries are position-sensitive: removing one can change generated replacements for entries below it.
Save changes deliberately
Unsaved changes means your edits are not yet saved. Selecting another profile or leaving and returning to Profiles can discard unsaved edits; save first.
If Save is disabled, read Cannot save: and the validation message. Common causes are a missing profile name, a name that conflicts with another profile's filename, a partially filled entry missing its ID or required value, or an invalid number. A completely blank row may disappear when you save.
New profiles receive an automatically generated internal value called a salt, used for consistent replacements. There is no salt-editing control in this screen. If an existing profile reports that entities require a salt, create a new profile and enter the needed details, or ask the person who supplied the profile to correct it.
Profiles are stored as readable JSON files containing the original sensitive details. Protect them like your source documents; do not share a profile with someone who should receive only the processed output.