The data-layer equivalent of an aviation Flight Data Recorder. AIDR™ captures every infrastructure fact about your AI interactions, before, during, and after, and writes them to a tamper-evident ledger.
Aviation's Flight Data Recorder captures altitude, speed, heading, and engine state. AIDR™ captures the equivalent for AI-assisted legal work: the infrastructure layer that tells you exactly what happened, at what time, using which model.
Matter number, supervising attorney, client authorization event, session open timestamp. Every record is bound to a specific matter from the first keystroke.
Which LLM, which API endpoint, which model version, and which inference parameters were used on each request. No ambiguity about what answered your question.
The complete anonymization audit trail: which tokens replaced which identifiers, deterministic mapping preserved. Client identity never touches the LLM API.
Every competence acknowledgment, supervision sign-off, hallucination flag, and authority verification result. The complete governance timeline, timestamped.
Original prompt, anonymized-sent, anonymized-received, and re-injected final, four immutable versions per interaction, written at the infrastructure layer.
AIDR™ computes the Chain Score™, Green, Yellow, or Red, at session close and writes it to the tamper-evident ledger. Your compliance posture, locked in at the moment of completion.
AIDR™ does not store a single copy of each prompt and response. It stores four versioned, timestamped records per interaction, the complete chain of what was sent, what was transformed, and what was returned.
The Chain of Legal Custody™ has six links. AIDR™ is the primary recorder for four of them, and co-recorder for the fifth.
Model, version, endpoint, inference parameters, the complete AI identity record.
How and when each AI-assisted work product was delivered, with confirmation and receipt.
Competence acknowledgments, supervision sign-offs, client authorization events.
The deterministic token map that lets AIDR™ re-inject client identity at session end, stored separately from the transmitted data.
RFC3161 timestamps on every event. Merkle root at session close. Immutable. Court-producible.
Prompts, outputs, corrections, and Governance Replay™ are handled by AIDR™'s partner recorder.
Schedule a demo and watch AIDR™ build a complete four-version audit log on a live AI session, from session open to Chain Score.
Request Access