What "on your own computer" actually means, and how to test it

“Runs on your own computer.” “Fully local.” “Offline.” Loads of meeting tools say it now, and it turns out the phrase does not always mean the same thing. If you are the person who has to actually sign off whether a tool is genuinely local, those words on their own will not get you there. So here are the three questions I would ask, and a quick test you can run to get real answers…

Question one: what is actually running the model?

The two heavy jobs in any AI meeting tool, the transcription and the writing up, both need a model, and the only question that matters is where that model runs. There are really three patterns:

• Local program, local model. Something on your machine loads a model file off the disk and runs it on your own CPU. No network call. This is what genuinely local means.
• Local program, remote model. There is an app on your machine, but it ships the audio (or the transcript) off to a server, the model runs there, the answer comes back. It feels offline because the window is local. The work is not. This is most “AI desktop apps”.
• Browser tab, remote everything. A web page uploads the lot. Local in name only.

The way to tell them apart is to watch what the thing actually does. Pull the network cable and see if it still works. A genuinely local tool produces the same output with the network off. Ours builds the models into the installer and runs them on your machine, so the same recording processes the same way whether you are online or not.

Question two: where do the files end up?

A meeting leaves three things behind: the recording, the transcript and the written up document. For a tool that runs on your computer, all three should be on your computer. Obvious, and yet plenty of local feeling tools quietly sync one or more of them to a vendor’s storage.

Things worth checking:

• Open a finished meeting and look at where it is saved. Are the recording, transcript and document sitting there as ordinary files you can open with software you already have?
• Is the folder under your control, or buried in some app managed store you cannot easily back up or move?
• If there is encryption, is it a password you set and hold, or a device key the app quietly manages for you?

Whistle Enterprise keeps the recording, transcript and document in a local workspace, which you can point at a local or a network drive, and exports land wherever you choose at the time. There is no sync to anyone’s cloud. The workspace can be locked with a password you set, and when it is, the contents are encrypted at rest.

Question three: what is it doing on the network?

This is the one that separates marketing from behaviour. A desktop app might reasonably want a few things from the network: software updates, licence checks, telemetry, crash reports, or, the big one for this conversation, quiet background calls to some API for translation or summarising or matching names to voices.

A genuinely offline tool answers each of those without poking a hole in the privacy story. Updates are something you download yourself, not something pulled automatically. Licensing works without phoning home. Telemetry, analytics and crash reporting are off, not opt in. And there are no background AI calls, because the AI is running on your machine.

That is the line we hold. The models ship inside the installer, not fetched at runtime. There is no automated update check and no callback to a server while it runs. If support ever needs a diagnostic file, that is something you choose to send, by hand, not something the app does on its own.

The ten minute test

Do not take anyone’s word for it, including mine. Here is a test that takes about ten minutes and gives you a straight answer on any candidate:

1. Install it on a clean machine. Note the size. A tiny installer with no model bundled is a hint the model gets fetched later, or lives somewhere else.
2. Open it, and before recording anything, disconnect the machine from the network.
3. Record a short meeting (play a video on your phone in front of the laptop). Stop. See if it transcribes and writes up with the network still off.
4. Reconnect, and watch what it does. A reasonable local tool might, at most, check for an update. One that uploads the recording you just made is the opposite of local.
5. Find the workspace folder and check the files are really there and readable.

Pass that and the tool is genuinely on your computer in the way that matters for sensitive work. Fail any step and it is doing something the marketing did not mention.

The security notes cover the same ground in product terms. If you would rather just run the test on Whistle Enterprise, the free 30 day trial is on the product page, and step two onwards works fine on a real recording of your own.