Blog

What “privacy-first” should mean for a meeting assistant

The Trippi Cue team · 2026-09-07 · 6 min read · facts checked against the product on 2026-09-07

Every meeting tool says it takes privacy seriously, and the phrase has stopped carrying information. What does carry information is a short list of structural questions — the kind with a yes or a no rather than a paragraph. Here are the five worth asking, and what a good answer looks like.

1. Where does the audio go, and does it stop anywhere?

There are three common shapes. The audio can go from your browser straight to a speech provider; it can pass through the vendor’s servers on the way; or it can be stored by the vendor as a recording. These are very different exposures, and marketing copy flattens all three into “encrypted in transit”.

Ask specifically: does the audio reach your servers at all, and is any of it written to disk? “Encrypted” answers neither question.

2. What is kept after the call, and for how long?

Retention is where post-call tools and live copilots genuinely differ. A note taker has to keep the transcript — it is the product. A live copilot does not: once the answer is on screen, the lines it was built from have no further purpose.

The strongest possible answer is that nothing is kept, because then there is nothing to leak, subpoena or misconfigure. The second strongest is a short, stated retention period with a delete path you can use yourself. “Kept securely” is not an answer.

3. Does anything join the meeting?

A bot in the participant list is visible to everyone, is often subject to your organisation’s recording policy, and may require the host’s permission. An extension that reads what your browser already plays joins nothing and asks nobody.

Neither is inherently more private — but only one of them is a decision you make on behalf of everyone else in the room.

4. Is your content used to train anything?

Two layers, and vendors sometimes answer only the first. Does the vendor train models on your meetings? And do their providers — the speech and model APIs behind the product — train on what is sent through them?

A vendor who has thought about this can name their providers and say what their agreements allow. A vendor who cannot name their providers has not thought about it.

5. What could the vendor produce if compelled?

This is the question that tests the previous four, and it is uncomfortable enough that few pages answer it. If the vendor were required to hand over everything they hold about your meetings, what would that be?

Sometimes the honest answer is a genuinely short list: an install identifier, counters of usage, and an email address if you made an account. That is a structural property, not a promise — nothing else exists to hand over.

The part nobody puts on a privacy page

One more, and it is the one people actually get caught by: an overlay that lives in a browser tab is visible to everyone if you share that tab. No amount of server-side privacy changes that, and a vendor claiming their window is invisible during screen sharing is either wrong or describing something that would be worth being suspicious about.

Privacy-first, in the end, is not a feature list. It is which answers stay the same when the questions get specific.