Managing Personal Identifiable Information (PII) in Enterpret

Personally identifiable information (PII) includes information that can identify a person, such as an email address or phone number. Enterpret masks supported patterns in designated feedback fields during ingestion. Coverage depends on the field, input format, and masking policy configured for your workspace.

PII Redaction

Enterpret applies its masking policy to designated feedback content before the processed feedback record is written to the Knowledge Graph. These fields include feedback text, conversation messages, survey answers, transcript text, and certain file-upload fields.

Some ingestion processing happens before masking. Raw webhook payloads can also be archived before this step and can contain the original content. Contact Enterpret to confirm how raw payloads and other copies are handled and retained for your workspace.

Metadata handling depends on the field and workspace configuration. Some fields are included in content masking; additional persisted metadata masking is controlled separately and currently targets email addresses. Display-time masking can also change what is shown without rewriting stored values. Confirm handling of CRM attributes, user and account data, and other metadata separately.

Supported PII Entity Types

The base feedback masking policy includes detectors for these patterns:

• Email addresses, phone numbers, IP addresses, credit card numbers, and US Social Security Numbers.

• Street addresses, ZIP codes, and PO boxes.

• Web links matched by the configured link detector, ISBNs, and inline Base64 images.

Additional handling covers certain structured identifiers and supported spoken-number formats. Coverage such as person-name detection depends on workspace configuration.

Detection depends on supported patterns, formats, and context. Confirm any additional types you need masked with Enterpret, and validate representative examples from your data.

Masked matches appear as placeholders such as <EMAIL_ADDRESS> and <PHONE_NUMBER>.

Admin Configuration

Contact Enterpret to confirm the PII masking policy for your workspace and discuss changes to content or metadata handling.

If you need existing records reprocessed, agree on the scope and verification with Enterpret. A change to ingestion configuration does not by itself guarantee that historical records or every stored copy will be rewritten.

Customizable Controls: Ingestion Blockers and Ingestion Scrubbers

Configured ingestion blockers and scrubbing rules can supplement automated masking. Ask your Enterpret team to confirm the supported rules and fields for your workflow.

Ingestion Blockers

Configured blocker rules can exclude matching feedback from the processed feedback dataset before its Knowledge Graph write. Raw ingestion copies and records already stored require separate handling; blocking new feedback is not an automatic purge of existing data.

Ingestion Scrubbers

Configured scrubbing rules can remove selected metadata keys and apply supported pattern replacements or line-removal rules to feedback text. The available transformations depend on the field and source format. Review the rules and test representative examples with Enterpret.

Benefits of PII Management in Enterpret

Automated masking and configured ingestion rules can reduce sensitive values in the feedback used for analysis. Review coverage against your data fields and sources, and validate the results as part of your privacy process. Masking does not guarantee that every sensitive value will be detected or that a particular compliance requirement is met.

Additional Privacy Controls

For deletion requests, see the User Privacy API and Data Deletion Options in Enterpret. Review the scope and processing requirements of those workflows separately from masking.

Conclusion

Contact your Enterpret team with the feedback source, affected fields, and the masking outcome you need. They can help confirm the applicable policy, supported configuration, and any historical-data handling.