Regulations · Regulation (EU) 2016/679, and the UK GDPR
GDPR and UK GDPR, on every AI call.
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.
What Vidai enforces or records
Following GDPR and UK GDPR.
- Personal data masked, pseudonymised or blocked before it reaches a model
- Calls kept in the EU or the UK with region rules
- Data processing agreements on record for each provider
- Copies and erasures for data subject requests, call by call
Retention it sets
No minimum. GDPR sets a ceiling instead: the longest you keep personal data, which you choose. UK GDPR works the same way.
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.
Where it applies
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.