Klyo Context Engine ships alongside the Gateway

Klyo Context Engine joins the platform as a new layer that improves how Klyo Gateway decides what counts as sensitive content. Routine business workloads see fewer interruptions where context makes clear that a flagged token is not personal data — a company name read as a person, an order reference read as a tax number, a place name read as a contact.

Coverage of genuine personal data is unchanged. The Context Engine produces signals; the Gateway firewall keeps the final allow-or-block decision. Existing audit trails and approval flows continue to apply to every request.

Available to all SaaS tenants from today. Self-hosted operators receive it as part of the standard Gateway deployment with no additional configuration.

No action required.