Skip to content
Klyo Changelog

Multi-turn context and broader coverage for dates and addresses

v0.3.0 improvement medium impact
  • firewall
  • compliance
  • performance

Klyo Context Engine v0.3.0 reads multi-turn conversation context when deciding whether a flagged token is sensitive. The same word — a city, a first name, a company — is now resolved correctly based on what was said earlier in the same chat.

Coverage broadens for two common ambiguities: dates of birth are kept as sensitive while ordinary calendar dates are not, and postal addresses are kept as sensitive while IP addresses and similar technical identifiers are not.

Validated across 368 multi-turn conversations in English, German, and French at 99% accuracy. Recall on real personal data stays at 100% on every test category.

Available immediately to all SaaS tenants. Self-hosted operators receive the upgrade as part of the next Gateway release; no configuration changes are required.

No action required.