Introduction
Most AI meeting tools work the same way: a bot joins your video call, records everything, and produces a transcript after the meeting ends. It is effective — but it comes with trade-offs. Participants see a stranger in the room. Recordings sit on third-party servers. And in many jurisdictions, recording a conversation requires explicit consent from every attendee.
There is another way. Meeting transcription without a bot captures audio directly inside your browser — through your microphone or by sharing a meeting tab — and turns it into text in real time. No participant joins, no audio file is stored, and the transcript stays on your side. This guide explains how that pipeline works, where it shines, and where bot-based transcription still wins.
How Bot-Based Transcription Works
Traditional meeting transcription tools follow a familiar pattern:
- You invite a bot, usually by sharing the meeting link or granting calendar access
- The bot joins your call as a visible participant
- It records the audio (and sometimes video) for the full session
- After the meeting, you receive a transcript and an AI-generated summary
This model works well for teams that want a complete, shareable record of every conversation. But the trade-offs are well known:
- Visibility: everyone in the meeting sees the bot. In Fellow.ai’s State of AI Meeting Notetakers 2025, 84% of users say they modify what they say when an AI note-taker is present (Source: Fellow.ai, 2025).
- Storage: the audio file lives on the provider’s servers, sometimes indefinitely.
- Consent: under the EU GDPR, recording a conversation without explicit consent from each participant can lead to fines of up to €20 million or 4% of global annual turnover, whichever is higher (Source: GDPR, Article 83).
- Friction: bots can fail to join, get blocked by IT policies, or require permissions that corporate environments restrict.
How Browser-Based Transcription Works
The alternative captures audio inside the browser itself. The flow looks like this:
- You open the transcription tool in a browser tab next to your meeting
- You grant microphone access, or share the audio of your meeting tab
- The audio is streamed to a speech-to-text engine and turned into text in real time
- Nothing is recorded — the audio is processed and discarded as it flows
This pipeline relies on two standard Web APIs documented by MDN Web Docs: getUserMedia for microphone capture and getDisplayMedia for tab audio sharing. They are the same building blocks that Zoom, Google Meet, and Microsoft Teams use to power their own browser clients.
The defining trait: no bot ever joins your call. The transcription happens entirely on your side, with no extra participant in the meeting UI. For more on the audio capture layer, see tab audio sharing explained.
Why It Matters for Privacy
The privacy implications go deeper than “no recording stored”:
- No file to leak or subpoena: because audio is processed live and immediately discarded, there is no recording that can later be accessed by a third party, an attacker, or a court order.
- Lower GDPR exposure: with no personal data retained on external servers, several obligations (storage limitation, breach notification on recordings, right to erasure on stored audio) are simplified or do not apply. Vendor agreements still matter — see our guide to private meeting transcription.
- No third-party participant: nothing appears in the meeting UI. Transparency with colleagues remains best practice, but you avoid the chilling effect of a visible recording bot.
For professionals in legal, healthcare, or finance, this can be the difference between using an AI tool and not using one at all. On February 11, 2025, Harvard University Information Technology issued formal guidance restricting the use of AI meeting assistants in Harvard meetings to a short list of contractually approved tools, citing “substantial” privacy, regulatory, and legal risks tied to stored recordings (Source: Harvard University Information Technology, 2025).
When to Choose Each Approach
Bot-based transcription is the better fit when:
- You need a complete, permanent record shared with the whole team
- All participants have consented to recording, in writing
- An automated post-meeting summary is more valuable than live text
Browser-based, no-bot transcription is the better fit when:
- Privacy or confidentiality is a hard requirement
- You want personal notes without creating a shared archive
- Some participants are uncomfortable with recording bots
- You need real-time text to follow the conversation as it happens — for accessibility, technical depth, or working in a second language
The two models can also coexist: use bot-based recording for internal team meetings where consent is straightforward, and no-bot transcription for client calls, interviews, or sensitive conversations.
Beyond Transcription: Real-Time Suggestions
Once audio is being processed live in your browser, transcription is only the starting point. The same stream can power real-time, contextual suggestions — definitions of unfamiliar terms, translation hints, or reminders of relevant context — surfaced while the conversation is still happening. That broader category, including transcription plus live AI help, is what we cover in our no-bot meeting assistant guide.
LiveSuggest takes that approach: a browser-based, no-bot tool that combines live transcription with AI-powered suggestions across 12 languages, with no recording stored and no participant added to the call (see pricing for current plans).
Conclusion
Meeting transcription does not have to mean inviting a bot into your calls. By capturing audio directly in the browser through standard Web APIs, you get a real-time transcript without a recording, without a third-party participant, and without the consent overhead that comes with stored audio. The right approach depends on what you need most — completeness and sharing, or privacy and live text — but the no-bot option is now mature, standards-based, and worth knowing.
If a private, no-bot transcript fits the way you work, you can try LiveSuggest in your browser — no install, no bot, and nothing recorded.
Sources
- The State of AI Meeting Notetakers 2025 — Fellow.ai, 2025
- Guidance on AI meeting assistants; data privacy principles — Harvard University Information Technology, February 11, 2025
- GDPR, Article 83 — General conditions for imposing administrative fines — Regulation (EU) 2016/679
- MediaDevices: getDisplayMedia() method — MDN Web Docs, Mozilla