Skip to content
Klyo Changelog

Klyo Context Engine becomes the default PII classifier

v1.13.0 feature medium impact
  • firewall
  • compliance
  • performance
  • ui

The Gateway’s content classification stage now uses the Klyo Context Engine by default — the trained multilingual model published as a separate product, with recall on real personal data benchmarked at 100%. The previous built-in ensemble remains available as a one-click fallback under Settings → PII.

The active classifier is selectable per tenant; the change takes effect on the next request, with selections recorded in the audit log. A PII activity card shows live counts and recent decisions for the chosen classifier.

When the Context Engine handles a message, the chat PII preview shows a Klyo badge so end users see which model judged their content. If the Context Engine is unreachable, classification falls back to a neutral signal so chat is not held up; the Gateway firewall continues to apply its baseline rules.

No action required. The default is on for new and existing tenants.