Compliance and the audit log

Everything done in your organisation is recorded in an audit log: each message sent and the model it went to, each project, person and invitation managed, and each time someone reads the log itself. Each entry is chained to the one before it, so that nobody - not even Teloneum - can change, remove or slip in an entry without it showing.

The log is for your organisation’s owners and administrators: they find Compliance in the menu of their name, at the bottom of the sidebar, which stays beside the log while they read it and verify it. On a phone, open the sidebar with the menu button at the top left.

What the log shows

At the top, a banner says whether the chain holds: up to which moment it was verified, how many entries it holds, the period it covers and the fingerprint (hash) of its last entry. Each reading verifies the whole chain again.

Each row is one entry: when, the request it belongs to, who acted, what was done, and which provider and model were asked, if any. The last two columns are the chain itself: the entry’s hash, and its previous hash - which is exactly the hash of the row below it, shown in the same colour.

Search by person, action or the start of a fingerprint, and filter by kind: Requests (calls to a model), Log access (conversations, people or the log being read) and Administration (projects, people, invitations, keys), by person and by period. Select a row to see its detail: who, which project, the path of the request, and what was recorded of the call; close ✕ puts it away and gives the log the whole width.

What you write is never in the log. A message is kept only as its fingerprint: given a copy of the text, Teloneum can show that this very text was sent, by whom and to which model - but nobody can read it from the log.

Downloading it

Download the archive gives you the whole log of your organisation as a zip:

• one file of entries per day, one entry per line;
• a manifest - how many entries, the period, the last fingerprint, and the fingerprint of each file;
• a description of every field;
• the verification script.

Downloading it is itself recorded in the log.

Verifying it yourself

Verify explains how the chain is built and shows the verification script in full, with its own fingerprint. It needs Python 3.10 or later and nothing else, runs on your computer without a network connection, and only reads the archive. Run it on the archive you downloaded:

python3 teloneum_verify.py teloneum-logs_acme_2026-10-18.zip

It says the chain is intact, or stops at the first entry that was changed, removed or added and names it.

Keep the last fingerprint of each archive you download, and give it to the script with the next one (python3 teloneum_verify.py <archive> <last fingerprint>): it then also checks that nothing before that point was rewritten since.