Skip to content

An audit with Vidai

What an audit looks like when the evidence is produced, not gathered. The example follows Grachtwerk Agency Group, a European creative agency whose client teams (Zuiderhoeve Dairy, Kessler Autohaus, Maison Ardelle, Fjordair and others) use AI every day. Katarzyna Nowak is its data protection officer and holds the Compliance officer role; Sanne de Vries, Head of Platform, is an organisation admin. The group follows GDPR and the EU AI Act.

Most of this story uses Enterprise features (tamper evidence, the downloads, the incident register). What Enterprise includes depends on the features your licence includes.

The request

An external auditor writes: "For last month, show us how AI calls involving personal data were controlled, that your logs are complete and unaltered, how long you keep them, and how you handle incidents and access."

1. Is the evidence sound? (two minutes)

Katarzyna opens Proof › Evidence. Tamper evidence is On, the gateway's signing key reads Confirmed, with who confirmed it and when, and the latest daily check is Verified. Before an audit she chooses Check everything again, which checks the whole history rather than only what changed since yesterday.

2. What was in force, and was it applied? (five minutes)

On Policies › Regulations, the GDPR and EU AI Act cards count their controls by state, gaps first. She opens Show its controls on GDPR: data minimisation is Enforced through the policy that masks personal data for every client team, with what it did in the last 30 days and calls to open. Records of processing are listed as Your organisation's process: the product doesn't cover them, and says so.

On the Compliance dashboard, How calls were protected shows every call in the month in one of four states, and Where protection is in place shows each team against each pack.

3. How long are records kept? (one minute)

Proof › Retention & legal hold shows the regulations as chips and a row per kind of record. The EU AI Act asks for 180 days of call records; the group's GDPR ceiling said 90. The clash was decided by Sanne, keeping the EU AI Act's floor, with her reason in the audit log. A legal hold is on for a regulator's inquiry into a Fjordair booking incident, so nothing is being deleted, and the page says since when and why.

4. Incidents and access (two minutes)

Proof › Incidents holds three entries: one open, one closed, and one Reported. That one is a personal data breach (Fjordair's care bot showed a passenger another passenger's booking), reported under GDPR to Datatilsynet, the Norwegian data protection authority, within 72 hours. A serious incident under the EU AI Act would go to a market surveillance authority instead; the register keeps whoever you reported to, and when. Proof › Access reviews shows Q3's review closed, every item decided, Katarzyna's own items decided by Sanne.

5. The files (a few minutes of waiting)

From Proof › Evidence Katarzyna asks for:

  • the auditor report for last month, with A sample (suggested) at 95% confidence and 5% tolerable error. Every call by a high-risk system (Fjordair's customer care bot among them) is included whatever the sample;
  • the evidence pack for the same period, For: EU AI Act: AI systems with their risk and owners, the policies and every change, oversight, the incident register, retention with the clash decision, the last closed access review and the latest verification.

Both are prepared in the background and listed under Asked for in the last 7 days. Each download is recorded in the audit log.

6. The auditor checks it alone

The auditor report carries a README and a signed manifest of every file's SHA-256. The auditor runs the check described there on their own machine, without access to Grachtwerk's systems, and can compare a few seal digests with the copies the group's SIEM received. If they want the same sample drawn again, the Seed in the file's header gives the same calls.

What was produced, and what wasn't

Everything above came from records Vidai kept as the calls happened. Nothing was assembled by hand, and nothing in the files says "compliant": the auditor draws that conclusion from the evidence.