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.
| Rule | What it asks | How Vidai helps |
|---|---|---|
| EU AI Act, Art. 12 | High-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. 44 | Every 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. |
| DORA | A 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 regime | Designated 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 approach | AI 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.
Mapped control by control
Regulations with every control mapped.
GDPR and UK GDPR
Personal data found and kept out of models before any call leaves, calls kept where they may be processed, and a person's data copied or erased when they ask.
GDPR and UK GDPR →EU AI Act
Every AI system with its risk, owner and review date, every call by a high-risk system on the record, and human oversight you can show.
EU AI Act →ISO/IEC 42001
Roles, AI systems and their owners, suppliers, model access and every change, recorded in one place and mapped to the standard's controls.
ISO/IEC 42001 →HIPAA
Health identifiers kept out of models, business associate agreements on record, and a record of who could call what, and of every call.
HIPAA →PCI DSS v4.0
Card numbers found with check digits and kept out of every model, unused keys suspended, and access reviewed.
PCI DSS v4.0 →Retention and evidence
Record-keeping and data laws.
FCA, MiFID II and SEC 17a-4
Records kept as long as financial regulators ask, including the content of calls made by applications that talk with your clients, and held during a dispute.
FCA, MiFID II and SEC 17a-4 →Gulf data laws
A built-in pack for each country's law, with personal-data guardrails that read Arabic-Indic digits as well as Latin ones, and calls kept in the region.
Gulf data laws →India DPDP and CCPA
A ceiling on how long personal data is kept, and the people it's about answered call by call.
India DPDP and CCPA →Evidence for your audit
Frameworks you're audited against.
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.
| Enforced | Every key in scope has it in force. |
|---|---|
| Observed only | It's watched and logged, but some keys only observe. |
| Partly | Some keys have it and some don't, with how many. |
| Nothing in place | Nothing in scope provides it yet. |
| Your organisation's process | Vidai 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.
How we start together
Start with one team, on your own AI traffic.
- 01
Pick one app or team
Point it at the Control room. One configuration change; nothing else changes.
- 02
Watch for two weeks
Every call priced, checked and recorded. Rules start in observe mode.
- 03
See the evidence
What it cost, what it caught and what it would have stopped, from your own traffic.