Skip to content
askTheodor Academy

Keep an audit trail

When your workers write to customers and take instructions from your phone, sooner or later someone asks “who said what, and when?”. The security log answers that. It’s a separate record of every conversation that stays put when chats are deleted, and it can prove that nobody edited it.

What you’ll learn

  • What the security log records, and what it deliberately doesn’t.
  • How to search it and check it with 🛡 Verify.
  • How to export a copy for an auditor and set how long entries are kept.

1. Open it

Go to Settings → Security log (in the Workspace group). Record conversations is on by default.

2. What’s in it, and what isn’t

Recorded:

  • every conversation: your chats with workers and their delegated runs;
  • WhatsApp, e-mail, Signal and Telegram traffic, including phone-console commands and secretary requests;
  • the audit trail of approvals and decisions.

Not recorded: chats you keep private. A WhatsApp number in 🔒 Private mode never stores other people’s messages, so there’s nothing to log.

Timing: a message is recorded once it has settled, about 5 minutes after it was written. A reply that streamed in over a minute is logged whole, and exactly once.

3. Why you can trust it

  • Kept separately. Entries go into day files in <app data>/security-log/, outside the database. Deleting a chat or emptying the trash doesn’t touch them.
  • Encrypted. The files are encrypted with this machine’s own key and can’t be read on their own.
  • Chained. Each entry carries a fingerprint of the one before it. Editing, removing or reordering any entry breaks the chain.

Each machine keeps its own log. Your VPS runner records what happens there.

4. Search it

Above the list:

  • the type filter: Everything, 💬 Chats, 📡 Channels (WhatsApp, e-mail…) or 🧾 Audit trail;
  • a from and a to day;
  • Search text, number, worker…, then Search.

Click an entry to see everything recorded about it.

5. Prove it with Verify

Click 🛡 Verify. If nothing was changed, you get a line like:

✅ 1284 entries in 31 day file(s) — chain intact

If something was edited or removed, Verify says so and names the first broken entry, e.g. ⚠️ this entry was edited — at 2026-10-02.jsonl:57 (the day file and the line).

6. Export for an auditor

Pick the days with the from and to fields, then click ⬇ Export. You get a decrypted copy of those days in your workspace, under exports/security-log_<from>_<to>.jsonl, and the app opens it.

7. Choose how long to keep it

Keep for sets the retention: 90 days, 6 months, 1 year (the default), 2 years, 5 years or forever. Older day files are deleted automatically. Pick what your industry or your contracts require, not more.

Try it

  1. Send status from your phone console, wait about five minutes, then search for status under 📡 Channels.
  2. Click 🛡 Verify and read the result.
  3. Export yesterday, open the file and find one of your own chats.

Recap

The security log is a separate, encrypted, hash-chained record of every conversation, channel message and approval, in day files outside the database. 🛡 Verify proves it’s intact, ⬇ Export gives an auditor a decrypted copy, and Keep for decides how long it stays. Private chats are never stored, so they’re never logged. Next: the playbooks, complete setups for who you are.

📖 Reference in the docs: Security log · Security & privacy

➡️ Next: Playbook: company of one