Classify sensitive fields
Identify personal, financial, contractual, and operational data that requires specific handling.
Masking and controlled-reveal patterns are running for selected customers. Pattern-based PII detection is in active development with design partners; we do not claim it is comprehensive across every file type or language. Where the signals are partial, the page makes that explicit.
Classification, permitted use, access, redaction, export, and retention controls travel with sensitive evidence throughout the investigation.
Identify personal, financial, contractual, and operational data that requires specific handling.
Present only the fields and records required for the user’s authorized investigation task.
Apply policy-aware handling to downloads, packages, deletion, and retained decision evidence.
PII handling is treated as a property of the workflow, not a one-shot scrub. Masking and controlled-reveal patterns are running for selected customers. Pattern-based PII detection is in active development with design partners; we do not claim it is comprehensive across every file type or language. Where the signals are partial, this page says so.
When a source is brought in, fields that look like personal data can be flagged for review. The flagging is conservative: where the system is uncertain, it errs toward marking the field rather than missing it. Reviewers do not need raw values to understand structure, so previews can render the shape of a record, which columns, what types, how populated, while masking the contents of sensitive fields.
Masking is applied as a presentation layer, not a destructive scrub. The original source stays linked, so authorized reviewers can confirm context when the workflow requires it. Lineage and citations continue to function on redacted content, because the source link is preserved. What changes is who can resolve the link, and every reveal of masked content is recorded in the audit trail.
Purpose and authorization shape each view so teams can examine financial leakage without casually expanding sensitive-data access.
Privacy is strongest when purpose, access, and retention remain visible together.
Illustrative view. Values shown are examples, not customer data.