The PII types tab controls exactly which entities the agent looks for. Tune it to your regulatory scope — a Europe-focused deployment might enable the GDPR pack (EU VAT, IBAN, FR INSEE, ES DNI, DE Tax ID, UK NINO/NHS) while disabling US-specific identifiers; an India-focused deployment might lead with Aadhaar and PAN.
View mode
By default the tab is read-only and shows every available entity grouped by category, with a clear enabled/disabled state for each. This gives auditors and admins an at-a-glance view of the active detection policy.
Editing PII types
Click Edit PII types
The list switches to edit mode with a checkbox per entity.
Check or uncheck entities
Enable or disable individual entities, or toggle whole categories.
Save
Click Save. The configuration is stored locally on the device.
Changes apply from the next scan onward. A scan already in progress continues with the entity set it started with; existing findings are not retroactively removed.
Entity categories
| Category | Example entities |
|---|
| Identity / National ID | FR INSEE, ES DNI, DE Tax ID, UK NINO, Aadhaar (India), PAN (India), US SSN, US ITIN, US Passport |
| Financial | IBAN, EU VAT numbers, credit card numbers, US bank routing (ABA) numbers |
| Medical | UK NHS numbers and related health identifiers |
| Contact | Email addresses, US phone numbers |
Disabling entities you don’t need reduces false positives and speeds up scans. Start with the packs matching the jurisdictions where you operate, then broaden if needed.
Disabling an entity means new occurrences of that PII type will go undetected. Align the enabled set with your data-protection policy before rolling the configuration out to a fleet.
