Use Cases
Thoth for Journalists
A journalist's ability to protect sources depends on what records exist of a meeting and where those records are held. A recording stored on a third-party server can be subpoenaed. A recording that never left your device cannot. The choice of tool is part of the security model.
Why cloud recorders don't work here
- Cloud-stored recordings can be compelled in court. A vendor that receives a subpoena or legal order has no practical choice but to comply, and typically has no obligation to notify the account holder before doing so.
- Bot-based recorders create a visible record of the meeting. For a source appearing under their own name, that entry exists on the vendor's servers and could surface in legal proceedings.
- Transcript text sent to a cloud AI is no longer under your control. If the transcript contains a source's name, quotes, or identifying context, that data is now held by a third party subject to its own legal obligations.
How Thoth fits
- No server-side record exists. Audio and transcripts stay on your Mac. There is nothing held by Thoth that could be compelled in court.
- No bot, no participant list entry. The meeting record beyond your own device is limited to what the call platform itself logs.
- Full transcript and original audio saved locally. Everything stays under your control, on hardware you own.
- On-device AI summaries. Source names and context never leave your Mac. Five local models included, no API key required.
- Record in the field, not only at a desk. The iPhone app runs the same on-device pipeline, so a doorstep interview or a call recorded on the move never reaches a server either. One purchase covers Mac, iPhone, and iPad.
Try Thoth free.
No account required. Free to try. Paid plans have no recording limits.
