A meeting recording is one of the most personal and most commercially sensitive pieces of data your work produces. It contains who said what, who knew what, what was promised, what was negotiated, and the tone in which all of it was said.

When you upload that to a cloud meeting service, you've handed all of it to a vendor. Their security is now your security. Their breach is now your breach. Their training pipeline, if their terms of service let them, becomes your unwilling contribution to a model someone else gets to use.

For a lot of people this trade is invisible. For some, it isn't a trade you can make.

The kinds of work that can't make the trade

In therapy, a recorded session uploaded to a US cloud provider is, at best, a contractual headache. At worst it's a violation of a code of ethics that a licence depends on.

In law, privilege is a fragile thing. The moment a client conversation passes through a third-party processor with discoverable metadata, the question of whether privilege still attaches stops being a clean yes.

In finance, the exam letter that follows a vendor breach is going to ask you, in writing, what data was disclosed. "All of it" is not a survivable answer.

In healthcare, the same logic applies, sharper.

Why most tools went the other way

Most meeting tools ship with a server in the loop because, until recently, that's where the work had to happen. The model that turns speech into text, the one that figures out who's speaking, and the one that writes the summary used to need more horsepower than a typical laptop could give them.

That has changed. The newer Macs run those models comfortably, at speeds that don't make you wait. The reason most meeting tools still send your audio to a server isn't a technical one anymore. It's that nobody changed it.

What we built

Weeve doesn't have a server that touches your meeting. Recording, transcription, speaker labelling, summarisation — all of it happens on your laptop. Once the app has what it needs, you can use it offline; the summary still gets written.

We can be specific about how committed we are to this. Until April, Weeve let users who wanted to connect their own Anthropic, Google, or OpenAI account to have the summarising done in the cloud instead. Almost no one used it. We removed it anyway. The only place Weeve does its work now is on the laptop in front of you.

This is not the cheapest way to build a meeting tool. It's the only way to say, honestly, that nothing about your meeting goes anywhere it shouldn't.