How the record is kept.

A platform that asks companies to trust it with their AI record has to show its own working. This page is that working, stated plainly.

The audit trail

Every meaningful action on the platform writes to an append-only audit log: who, what, when, on which record. Reads of sensitive records are logged as well as writes. The trail is not a feature that can be switched off.

Access is held by roles

One account per person; rooms unlock by role, and every check happens on the server, on every call. A company sees its own organization and nothing else. Two carve-outs bind every role, including administrators: individual fluency sentiment is internal to Trocola only, and class notes belong to the trainee.

Documents are referenced, never embedded

Files live in document storage. The platform holds the reference, the class, and the hash, so what is on the record can be proven to be what was filed, without the platform becoming a second copy of everything it tracks.

Verification is public

Any credential Trocola issues can be checked by anyone at the verify window: holder, credential, course, date, and standing, nothing more. The platform's own health is public at status, and the governing policies are in the Legal and Policy Center.