Control data in AI prompts

TETRA inspects AI prompts in real time. Your company decides which data needs control and what action to take when it is detected.

How TETRA checks a prompt

01

An employee writes a prompt in a supported AI service.

02

The TETRA extension or agent checks the content on the employee’s device using configurable rules and local detectors.

03

Policy determines the action: monitor, mask, or block.

04

The original or masked prompt is sent to the AI service, or the prompt is stopped.

Three policy actions

Monitor, mask, and block are alternative actions, not a sequence.

Monitor

The prompt is sent unchanged. The security team sees which AI services employees use and which data categories were detected. Helps assess activity before restrictions, but on its own does not prevent sensitive data from being sent.

Mask

TETRA hides detected sensitive information according to company rules. Masking is irreversible: data is not replaced with tokens for later recovery. The modified prompt is sent, and the response may differ without the hidden details.

Block

TETRA stops prompts that violate company rules. When a prompt is blocked or masked, the employee sees a notification, and the customer controls its text.

Data categories for control

Personal data
Payment and financial information
Credentials and secrets
Source code and intellectual property
Corporate documents
Trade secrets
Local detectors. TETRA includes detectors for PINFL identifiers and Uzcard and Humo card details. PINFL is Uzbekistan’s personal identification number for individuals. Categories and rules are configured to match company policy; before deployment we’ll test detection against your data formats.

See TETRA in action

In the demo, we’ll show how a prompt is inspected and the resulting event in the administrative console.