6–7 October — first public showcase of TETRA at CSS 2026TETRA at CSS 2026

Book a meeting →

Where TETRA inspects and processes data

Prompts are inspected in the browser extension or agent on the employee’s device. The server component and console run in your infrastructure.

How TETRA handles data

Deployment in your infrastructure

The TETRA server component and administrative console run in your infrastructure. Event logs and analytics stay with you, which matters for data localization requirements.

From the device to the console

The extension or agent detects data using rules and regular expressions. Event information is sent to the TETRA server component and displayed in the console. Detection does not use external cloud models or APIs.

Centralized management

The extension can be managed centrally through Active Directory or MDM.

What external AI services receive

The prompt sent to the chosen AI service is a separate data flow. In monitoring mode, the service receives the original prompt; with masking, a modified prompt; with blocking, nothing is sent.

Storage and telemetry

The installation does not send prompt content, diagnostics, or telemetry to TETRA servers.

Internet access and updates

The TETRA management component requires an internet connection. Updates are installed through the administrative console and also require internet access. This configuration is not designed for a fully isolated network.

What to define before deployment

Decide what will be logged, who can access those records, and how long they will be retained. Review network connections, data protection, and deletion procedures for the selected configuration.

Discuss your security requirements

Send us your technical questions, and we’ll discuss deployment, data flow, and the materials available for evaluation.