What we mean by immutable
When Audition AI says its audit logs are immutable, we mean something specific. Here is what we record, what “immutable” covers, how retention works, and where the line is.
What we record
Our audit logs are thread logs: a complete, timestamped record of every conversation, written event by event as it happens.
Every message
What each person asked and every response the AI gave, in order, with timestamps.
Every action the AI took
Each tool call, its inputs and its results, including database queries and their result sets, and code that was run.
Sources and files
The documents, web results and knowledge sources the AI cited, and the files that were uploaded and processed.
Human decisions
Requests for a person to approve a sensitive action before the AI carries it out.
Flags and reviews
Content that was flagged, compliance reviews, and retention actions taken on the thread.
API conversations
Conversations started through the Audition AI API are logged the same way as conversations in the app.
What “immutable” means here
Thread logs are append-only. Once something is recorded, Audition AI never changes it.
Written once, never edited
Every event is saved as its own record with a unique ID. Nothing in Audition AI edits a record after it's written. New activity adds records; it never rewrites old ones.
Never deleted by the application
There is no delete button for thread logs, for users or for administrators. The only thing in Audition AI that removes them is a retention policy your administrators choose to turn on.
Kept forever by default
Out of the box there is no retention policy, so thread logs are kept indefinitely.
Integrity-hashed
The records for each message carry a SHA-256 integrity hash that the application can validate.
In your own Azure storage
Thread logs are stored in Azure Storage in your subscription, not ours, alongside the rest of your Audition AI data.
Your policy, measured from the last chat
Retention is off until your administrators turn it on. When they do, they choose a period from 1 to 3,650 days.
The clock runs from a thread's most recent activity, not from when it started. A thread that began years ago but was used last week keeps its entire history, every record back to the first message.
Purged only after inactivity
A thread is removed only once it has gone the whole retention period with no new activity.
Retain indefinitely
Individual threads can be marked to keep forever, regardless of the retention policy.
Set by your administrators
Only your Administrator and ComplianceAdmin roles can set or change the retention policy.
Enforced by the application
Immutability is enforced by Audition AI itself. Your storage account is not configured with an Azure write-once (WORM) storage policy.
Because thread logs live in your own Azure subscription, your Azure administrators keep the same control over that storage account that they have over any other resource you own. Use your Azure access controls to decide who holds that access.
Common questions
Can a user delete a conversation's log?
No. Nothing in Audition AI deletes thread logs except a retention policy that your administrators turn on.
Where are the logs stored?
In Azure Storage in your own subscription, not ours. You decide who has access to that storage account.
How long are logs kept?
Indefinitely, unless your administrators set a retention policy. If they do, a thread is purged only after it has been inactive for the whole retention period, and threads marked to retain indefinitely are never purged.
Is this the same as Azure immutable (WORM) storage?
No. Today immutability is enforced by the Audition AI application. Your storage account is not configured with an Azure write-once policy, so administrators of your Azure subscription keep their usual control over it.
See also Transparency & Audit Trails, Data Sovereignty and the Security Information Guide.
Walk through your audit trail
Bring your recordkeeping requirements. We'll show you exactly what Audition AI records and how retention is configured in your own environment.