Compliance: rules applied to every call, and proof on demand¶
Most organisations can write down their AI policy. Few can show that it was applied to every call, last Tuesday, by every app. Vidai puts your rules in the path every AI call already takes, records what each rule did, and hands you the evidence when the auditor or the regulator asks. You run it yourself, from the Control room, without a ticket to IT for each change.
This section is for compliance officers, data protection officers, risk and privacy people, and the auditors they answer to. It's told the same way throughout: the problem, what you get, and how you get it.
flowchart LR
R[Regulations you follow] --> P[Policies: guardrails, region rules, approved models]
R --> T[Retention and legal hold]
P --> G((Gateway: every call))
G --> L[Request logs and the audit log]
L --> E[Evidence: auditor report, evidence pack]
T --> L
Compliance has two sides¶
| What it covers | Where it lives | |
|---|---|---|
| Regulatory governance | The regulations you follow, how long records are kept, the evidence | Policies › Regulations, Proof › Retention & legal hold, Proof › Evidence, Proof › Audit |
| Data governance | What data may reach which model, and where it may be processed | Policies › Guardrails, region rules on Policies, Models & routing › Models (Approved for use) |
Vidai acts on both before the risk happens, on every call, and then proves it. It doesn't stop at watching and reporting.
Start here¶
- From policy on paper to policy in the traffic: the story, and what you need from IT once.
- Regulations, mapped: every regulation Vidai helps with, and what it does for each.
- Evidence and the auditor report: what you can hand over, and how it's checked.
- An audit with Vidai: from the auditor's request to the file handed over.
Everything in this section¶
| Page | What it answers |
|---|---|
| From policy on paper to policy in the traffic | Why policies in the request path, and what you run alone |
| Guardrails: what a call may contain | Personal data, secrets and injection found and acted on before a model sees them |
| Where AI may run | Regions, approved models and provider agreements |
| Regulations, mapped | GDPR, the EU AI Act, ISO/IEC 42001, HIPAA, PCI DSS and the rest: what Vidai does for each |
| Named compliance policies | One name for the rules that serve one purpose; observe before you enforce |
| Exceptions and approvals | Who may lift a rule, for how long, and how it's recorded |
| Risk and high-risk agents | Risk levels, review dates and the register |
| Access reviews | Showing regularly that every role and key is still needed |
| Serious incidents | A register a regulator can ask for |
| Evidence and the auditor report | Tamper evidence, the auditor report and the evidence pack |
| Data and people's rights | Retention, legal hold, reading content, data subject requests |
| Watching it live | The Compliance dashboard and events to your SIEM |
| An audit with Vidai | A worked example, start to finish |
| The Compliance officer role | What the role can and can't do |
The step-by-step guides are under How-to › Compliance.
Editions¶
Following regulations, retention and legal hold, the tamper-evident audit log, access reviews, data subject requests and risk levels are in every edition. Some features are marked Enterprise: what Enterprise includes depends on the features your licence includes. Each page says what a Community reader has instead.
What Vidai never says
Vidai never tells you that you're "compliant". It shows what's enforced, what's only observed, what's missing and what stays your organisation's own process, and produces the evidence. Your auditor makes the call.