Skip to content

Public Knowledge Reconciliation ​

Public Knowledge Reconciliation reduces over-redaction of well-known entities while preserving strict PII protection.

Why this feature exists ​

Traditional PII pipelines can over-redact broadly recognized entities. For example, mentioning "Utah," "NASA," or "World War II" in a prompt may trigger redaction even though these are common public knowledge. When these entities are masked, assistant quality drops for harmless public-knowledge requests.

What it does ​

When enabled, the pipeline evaluates detected entities against public-knowledge signals. Entities confirmed as widely recognized public knowledge are excluded from redaction and returned to the model in clear text, preserving conversation quality without compromising privacy.

How it works ​

Resolution runs through multiple verification tiers in order, stopping on the first confident match. Administrators can configure which tiers are active; the default configuration uses only the fastest offline tier for minimal latency and zero external calls.

Safety guardrails ​

Public Knowledge Reconciliation is bounded by strict safety logic to prevent private data from being misclassified as public:

  • Proximity filters prevent reconciliation when entities appear near private identifiers
  • Context-aware rules block reconciliation when surrounding context indicates private usage
  • Consensus gating requires agreement across detection layers before overriding protections
  • Entity-type exclusions ensure that inherently sensitive entity types are never eligible for reconciliation and always remain protected

Privacy protections ​

To prevent accidental data leakage:

  • Only the offline tier is enabled by default
  • Candidate entities are pre-filtered before any external resolution calls
  • Audit logging tracks all reconciliation decisions for compliance review

Configuration ​

Administrators control Public Knowledge Reconciliation through admin settings, including which resolution tiers are active and whether the feature is enabled per workspace. Changes are logged for audit purposes.

Compliance benefits ​

  • Reduces false-positive redaction without weakening PII protection
  • Full audit trail of reconciliation decisions supports compliance review
  • Conservative defaults ensure safety out of the box
  • Granular admin controls allow organizations to tune the balance between privacy and usability

SOC 2 Type II Certified | BAA Available | HIPAA-Ready