Regulatory governance

Regulations applied to every call, control by control.

Choose the regulations you follow. Vidai sets the retention they need, proposes the policies that serve them, keeps the risk of each AI system dated, and shows what's covered and what's a gap, with the calls that prove it.

Vidai Control room · Regulations
Coverage for each regulation you follow, gaps first.
Coverage for each regulation you follow, gaps first.

Why it matters

Governance that lives in documents.

Regulators ask which AI systems are high risk, who owns them and when they were last assessed. The answer sits in a spreadsheet that drifts from what actually runs, and each regulation says something different about how long records must be kept.

What it does

Regulations as packs

Each regulation is a versioned pack that cites its sources: retention, proposed policies and the controls it asks for.

Rules at the right level

Set a rule once, on the organisation, an environment, a team, an application or an agent, and it reaches everything below it.

Observe, then enforce

A policy starts by recording what it would have done. Enforce it once the findings look right.

Exceptions with an end

Each exception has a name, a reason and an end date. Nobody widens their own access without a second person seeing it.

Risk kept on each AI system

Risk levels in the EU AI Act's terms, assessed, dated and reviewed. A call keeps the risk its system had when it was made.

Retention, legal hold and subject requests

Records kept as long as the law needs and no longer, held during a dispute, and personal data copied or erased on request.

In the Control room

See it working.

Policies · Recipes

Start from a recipe.

A regulation's recipes propose policies in observe mode, ready to review and adapt to your organisation.

Vidai Control room · Policies
Policy recipes, proposed by the regulations you follow.
Policy recipes, proposed by the regulations you follow.

Policies · What applies here

Every exception in force, with its end.

Who asked, who agreed, why, and when it lapses. Nothing lifted quietly, and nothing lifted for ever.

Vidai Control room · What applies here
Exemptions and overrides in force, each with its reason and end.
Exemptions and overrides in force, each with its reason and end.

Proof · Risk register

Which AI systems matter most.

Every agent and application with its risk level, owner, assessment date and review date.

Vidai Control room · Risk register
The risk register: AI systems, their risk, owners and reviews.
The risk register: AI systems, their risk, owners and reviews.

Proof · Retention

Kept as long as each regulation needs.

Each regulation sets a floor; GDPR can set a ceiling. When they clash, the longer period holds until someone decides, with a reason.

Vidai Control room · Retention & legal hold
Retention periods set by the regulations followed, and legal holds.
Retention periods set by the regulations followed, and legal holds.

Who uses it

Compliance officers set and read the rules. Risk owners keep their AI systems' assessments current. Auditors receive the evidence, signed, and check it themselves.

Coverage per control, the compliance officer role, and the signed auditor report and evidence pack come with Enterprise. Following regulations, policies, retention, legal hold and subject requests are in every edition. Vidai gives you the evidence; your auditor makes the call on compliance.

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.