Data protection

What must not leave, doesn't.

Guardrails check what every call sends, for every app, team and agent at once. They mask, swap for stand-ins, block or redirect what they find before any model sees it, and region rules keep each call where it's allowed to be processed.

Vidai Control room · Request logs
A call whose personal data was masked before it reached the model.
A call whose personal data was masked before it reached the model.

Why it matters

One team forgets, and the data is gone.

Telling every team to strip personal data before calling a model works until one team forgets. "Where do our prompts go?" is answered from a wiki, and checking data for leaks usually means sending it to someone else to check.

What it does

Found before it leaves

Card numbers, personal data, health data, secrets and keys, prompt injection and your own internal terms.

Masked, swapped or blocked

Mask it, swap it for stand-ins and restore the originals in the answer, block the call, or send it to a model you trust with it.

Checked in your network

VidaiGuard's small models run beside Vidai and find what patterns can't. Your data isn't sent elsewhere to be checked.

Calls kept in region

Region rules keep calls from a team, environment, application or agent within an area. A call that would leave is refused, and says why.

One list of approved models

The models any call may reach at all, with provider agreements required where you need them.

Observe first

See what a guardrail would have caught on your real traffic, then enforce it. Every finding is kept for review.

In the Control room

See it working.

Guardrails · Packs

Ready-made packs, and your own.

Packs for personal data, payment cards, health data, secrets and injection, plus patterns for your own terms.

Vidai Control room · Guardrails
Guardrail packs, and the rules that use them.
Guardrail packs, and the rules that use them.

Settings · VidaiGuard

Checks a pattern can't do.

Switch on VidaiGuard's models for personal data, toxicity and injection, running inside your network.

Vidai Control room · Guardrails
Turning on VidaiGuard checks.

Policies · Region rules

Where each call may be processed.

Areas such as the European Union, applied to a team, environment, application or agent.

Vidai Control room · Region rules
Region rules keeping calls within an area.
Region rules keeping calls within an area.

Request logs

Sent to a model you trust.

When a call carries data that must stay put, Vidai can redirect it to your own model or one in your region, and records why.

Vidai Control room · Request logs
A call redirected to another model because of what it contained.
A call redirected to another model because of what it contained.

Who uses it

Security and data protection officers decide what may leave and where. Compliance reviews the findings. Every team's apps are covered without a line of code.

Pattern-based guardrails, masking, pseudonymising, blocking and approved destinations are in every edition. VidaiGuard models and region rules come with Enterprise.

Related

How we start together

Start with one team, on your own AI traffic.

After a 20-minute demo, we agree a two-week pilot with you: one app or team, your traffic, your infrastructure.
  1. 01

    Pick one app or team

    Point it at the Control room. One configuration change; nothing else changes.

  2. 02

    Watch for two weeks

    Every call priced, checked and recorded. Rules start in observe mode.

  3. 03

    See the evidence

    What it cost, what it caught and what it would have stopped, from your own traffic.