AI evidence log for audits

What gets logged

For every request: who made it, which team they belong to, which model received the text, which data categories were detected, which action was applied and what it cost. Without the message content, unless a specific policy requires it and says so.

What it is for on the day it matters

A log like this turns an argument about whether someone uploaded a document into a two-minute query. It serves equally to answer a client asking how you handle their information and to document due diligence to whoever asks.

Exportable, not captive

The log exports to CSV. We do not want to be the only place that information lives: if you stop using us one day, the evidence is still yours.

A two-minute lookup

A client asks whether their contract went through an AI tool. You filter the log by date and team and see how many requests there were, with which model, which data categories were detected and whether they were masked, routed or blocked. Nothing has to be reconstructed from memory, and nobody has to search their own history.

Two logs, not one

One records every request: who, model, categories, action, tokens and cost, without content. The other records configuration changes: who modified a policy, a cap or a permission, and when. Acotia's own actions on a company account are marked as such in the log its administrator sees.

Official sources

EU Artificial Intelligence Act, Regulation (EU) 2024/1689: official text on EUR-Lex.

Supervisory authority in Spain: Spanish Agency for the Supervision of Artificial Intelligence (AESIA).