Regulations

Choose the regulations you follow. Vidai applies them to every call.

Each regulation is a versioned pack that cites its sources. It sets the retention the regulation asks for, proposes the policies that serve it, shows coverage control by control and produces the evidence. Vidai never claims a control it doesn't cover.

Already in force

What regulators already ask of AI.

None of this is future regulation. Agents make it harder: one task becomes ten calls or more, and every one is an event to record, a transfer to account for and a decision to explain.
RuleWhat it asksHow Vidai helps
EU AI Act, Art. 12High-risk AI systems must automatically record events over their lifetime. A manual export or a person reviewing outputs doesn't satisfy it.Every call recorded automatically and sealed as it happens, kept at least 180 days; every call by a high-risk system always in the auditor's sample.
GDPR, Art. 44Every transfer of personal data outside the EEA needs a lawful basis. One agent task can create dozens of transfers to account for.Personal data masked or blocked before it leaves; region rules keep calls in the EU or UK (Enterprise); each call records where it was processed.
DORAA register of every ICT third-party arrangement, an assessment of concentration risk, and evidence that a critical function could move provider.Evidence to draw on: approved destinations, the provider that served each call, cost by provider, and fallback chains that move calls between providers. DORA is a label in Vidai; it sets nothing by itself.
UK Critical Third Party regimeDesignated critical third parties, AI providers among them, face operational-resilience duties like regulated firms.Keeps you able to move: apps call names you choose, so switching provider is a change in the Control room, and fallback absorbs an outage.
The FCA's approachAI is supervised through existing rules: firms evidence who owns each AI process, what approvals came first, the controls applied and how it's monitored.AI systems with owners and risk levels, approvals and exceptions on record, rules applied to every call, and a tamper-evident audit log of every change.

Summaries, not legal advice: the official text decides, and your auditor makes the call on compliance.

Evidence for your audit

Frameworks you're audited against.

On Enterprise, an evidence pack for a framework carries a file mapping Vidai's records to each of its controls, with the controls that stay your organisation's own. Evidence for your audit, never a statement that a control is met.

SOC 2

Records kept for at least a year.

ISO/IEC 27001

Records kept for at least a year.

ISO/IEC 42001

Mapped control by control as well.

SOX

Records kept for at least seven years.

NIST AI RMF

Evidence mapped to its controls.

DORA can be used as a label on policies so you can find them; it sets nothing by itself. Our DORA guide covers what it asks of AI.

Coverage

Each control, shown as it really is.

Following a regulation sets its retention and proposes its policies, in observe mode first. On Enterprise, each control shows its coverage, gaps first, with the calls that prove it.
EnforcedEvery key in scope has it in force.
Observed onlyIt's watched and logged, but some keys only observe.
PartlySome keys have it and some don't, with how many.
Nothing in placeNothing in scope provides it yet.
Your organisation's processVidai doesn't cover it. Listed so you see what isn't covered: always last, never hidden.

Which controls a setting covers is our reading, not legal advice; the official text decides, and your auditor makes the call on compliance. Coverage counts AI calls sent through Vidai, not your other systems.

Vidai Control room · Regulations
One GDPR control, partly covered: the evidence it looks for, 30 days of findings and the policies behind it.
One GDPR control, partly covered: the evidence it looks for, 30 days of findings and the policies behind it.

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.