For teams running credit, hiring, claims or other automated decisions, and AI agents
When someone asks why the system decided, show what it did, unchanged.
An applicant refused, a candidate screened out, a claim declined, an agent that took an action nobody expected. The question that follows is always the same: what exactly happened, which version of the system did it, and can you show the log was not edited once the question was asked?
- When it is tested
- A person contests an automated decision about them; a supervisor or market-surveillance authority asks for your logs; an internal review after an incident; a court.
- What you will be asked for
- For high-risk AI systems, the events logged automatically (AI Act, Article 12), kept by the provider (Article 19) and by the deployer for at least six months (Article 26(6)). For a decision based solely on automated processing, the person’s right to human intervention and to contest it (GDPR, Article 22(3)), which you can only honour if you can say what was decided and why.
- What goes wrong today
- Logs rotate, are overwritten, or sit in the same infrastructure the team can edit. Model versions move on. Months later nobody can say which version decided, and an honest log is no easier to believe than an edited one.
- What changes
- One sealed record per decision or agent run: the inputs’ fingerprint, the model version, the outcome and any human review, kept in your own systems with only a salted fingerprint sent to us. Drop-in recorders for your existing logs, LangChain and the OpenAI Agents SDK do it without changing your code’s logic. AI agents and assistants
Sealing shows that a log existed unchanged from a given moment. Whether your system is high-risk, and whether its logs are enough, is yours to establish. What the AI Act asks · GDPR Article 22
Try it in two minutes
- Download a sample decision record (fictional applicant and system).
- Seal it on Seal a file. A free sandbox key is issued on the page; the file is never uploaded.
- Change the outcome in the sample, then check it against its receipt at Check. It fails; the original passes.
In production, the recorders seal every decision as your system writes its log.