For auditors
Evidence you can check on your own machine.
When an organisation runs its AI through Vidai, the evidence is recorded on every call and sealed as it happens. You get one signed report for any period, and you verify it yourself, without access to their systems.
What you receive
One signed file, not weeks of screenshots.
The auditor report
For any period: the calls, as a reproducible sample or every call, with every high-risk call always included; the audit events; and the policies in force at the time.
Both sides of the record
The part of Vidai that carries the calls and the part that manages it each seal and sign their records and check each other, daily and on demand, with Verified or the exact reason why not.
A tamper-evident audit log
Every change, sign-in and read of call content, in a chain you can check at any time. Reading a call's content is its own role, and every read is recorded.
The configuration each call ran under
The key's settings, who set them, and when. No reconstructing what was true in March.
An evidence pack for a regulator
AI systems with their risk and owners, the policies and every change, oversight, incidents, retention and the last access review.
Coverage you can trust
Each control shown as enforced, observed, partly in place or a gap, with the organisation's own processes listed. Never a statement of conformity.
How it works for you
Prepared in minutes. Checked by you, offline.
The organisation picks the period and the framework. Vidai seals the report and signs it. You receive one file, run the check on your own machine, and see what was checked and when.
- EU AI Act, ISO/IEC 42001, GDPR, HIPAA, PCI DSS, SOC 2, ISO/IEC 27001, SOX, NIST AI RMF
- Every high-risk call included in every sample
- Records held as long as each regulation requires, and under legal hold during a dispute
The downloads, in one place.
Auditor report, evidence pack, sample of calls and every call: each named with the pack version in force, and each checkable on its own.
Regulatory governance →
How you check it
One file, checked on your own machine.
README.md
The steps, written down
How to check this file, step by step. You follow it yourself; nobody from the organisation needs to be in the room.
manifest.json
Every file, fingerprinted and signed
The SHA-256 of every file in the zip, signed. The check confirms each file against it, so a changed or missing file shows at once.
The seals
Records sealed as they were written
The check confirms the seals against the keys the organisation confirmed when recording began, without access to their systems.
A second witness
Compare with their SIEM
Seal digests also go to the organisation's SIEM as they happen. Compare a few with the copies there.
The seed
The same sample, drawn again
The seed in the file's header draws the same sample of calls again, so you can confirm it wasn't chosen to flatter.
The result
Confirmed, or a clear failure
Every file confirmed against the signed manifest and every seal against its key. If anything fails, don't rely on the evidence until you know why.
Questions auditors ask
Straight answers.
| Do I need access to their systems? | No. You check the signed file on your own machine. |
|---|---|
| How do I know every call was included? | Every call is recorded and sealed as it happens. Samples are reproducible, and every high-risk call is always in them. |
| Can anyone change the records afterwards? | The audit log is a chain; any change breaks it, and the check says exactly where. |
| Does Vidai say the organisation is compliant? | No. It records and evidences what ran. The opinion is yours. |
| What about calls that don't go through Vidai? | They aren't covered, and the coverage view says so. |
For auditors