A meeting recorder app decides where your recording lives, not whether you are allowed to make it. On Google Meet, participants can only record a meeting if the host has permission to record. On Microsoft Teams, recordings carry a default expiration of 120 days. Meet saves to the organiser's Drive; non-channel Teams recordings normally land in the organiser's OneDrive.

Every roundup of meeting recorder apps ranks them on transcript accuracy, summary quality, and price. Those matter, and they are also the three things you learn in the first ten minutes. The questions that bite turn up in month four: the recording you needed is gone, or it was never yours to begin with.

So this guide skips the ranking and answers the three questions that decide whether a recorder app fits your situation — who may start a recording, whose account holds the file, and how long it survives. If you would rather just try a local-custody option, open MirrorCaption in a browser tab; the first hour is free.

Key Takeaways

Who Is Actually Allowed to Press Record

Native recording permission is a platform setting. A separate local recorder may capture audio outside that native control, but it does not replace participant consent or applicable law.

Google is the most explicit about it. Its support documentation states plainly that participants can only record a meeting if the host has permission to record, and that recording is available on a computer or an Android device. Google's current supported-editions list does not include Business Starter. Meet's native recording controls currently work on a computer or Android device, not in the iPhone app. A guest also needs the host's account to be eligible.

Teams and Zoom also govern native recording through meeting roles, account settings and administrator policy. A separate recorder may bypass a platform's native record button, but that does not settle whether you may legally or contractually record a conversation. Confirm permission and inform participants before capturing audio.

Consent law is genuinely jurisdictional. Germany's § 201 StGB penalises recording another person's non-publicly spoken word without authorisation. France's Code pénal art. 226-1 addresses recording private or confidential speech without consent; for specified acts it presumes consent only when those affected knew, could object, and did not. We keep the full treatment on our guide to what AI meeting tools do with your data rather than repeating it here.

Where the File Lands Is Not Where You Pressed Record

The storage account may differ from the person who presses record. Check the platform and meeting type before assuming you can retrieve the file later.

Google Meet saves the file to the meeting organiser's Drive. If you recorded a vendor's demo call and the vendor scheduled it, the file is in the vendor's Drive. Non-channel Microsoft Teams meetings behave the same way, landing in the organiser's OneDrive. Zoom cloud recordings use storage pooled at the account level, so a recording uses the account's shared allowance.

Bot-based recorders change the custody question rather than answering it. They may store meeting content with a separate vendor, subject to that vendor's terms and settings; check the specific product before assuming where the file lives. Microsoft's own external bots admin documentation is unusually direct about the consequence, warning that such bots may "record or transcribe meetings without participant awareness" and "store meeting data in third-party systems outside of the organization's compliance boundaries." When the platform vendor itself makes the argument, we do not need to.

That same policy is why bots are increasingly conspicuous. Teams places detected external bots "in the meeting lobby irrespective of the lobby configuration," with RequireApprovalWhenDetected as the default mode. Be precise here, because trade coverage has overstated it: Microsoft documents detection and lobby-holding, not an automatic hard block. Either way, a bot is a participant, and participants get noticed — our write-up on live meeting translation without a bot covers the capture side of that trade-off.

How Long Your Recording Actually Survives

Expiry is the most under-reported spec in this category, and Microsoft publishes the clearest numbers.

Teams sets a default expiration time of 120 days for meeting recordings and transcripts. The configurable range runs from 1 to 99999 days, and an administrator can disable expiry entirely through PowerShell. The admin default is not retroactive: changing it today does not update a file recorded in June. Microsoft separately says people can modify the expiration date of recordings they control, and a Purview retention policy may keep content longer.

If automatic expiry is enabled, an expired recording moves to the storage account's recycle bin. Microsoft says work or school OneDrive items are normally deleted after 93 days unless an administrator changes the setting. The often-quoted 120 + 93 days is only an illustration for an unchanged default policy and standard recycle-bin retention; owner edits and other retention policies can change the outcome. Microsoft lists a 30-day maximum default expiration for A1 users.

Zoom's constraint is shaped differently. Cloud recording has a storage allowance — Pro and Business licences include 10 GB per licensed user, Business Plus 15 GB, and Enterprise is unlimited, all pooled across the account. Note that search results still circulate an older 5 GB figure from community threads; Zoom's own knowledge base is the number to trust. Google Meet imposes a different kind of ceiling: an 8-hour cap, after which recording stops on its own.

Want the recording to outlive the meeting platform? MirrorCaption stores session audio and transcripts on your own device, with a retention window you set.

Try MirrorCaption Free

Three Custody Models for a Meeting Recorder App

Strip away the branding and every meeting recorder app sits in one of three custody models. Choosing the model is the decision that matters; choosing the product is downstream of it.

Custody model Who can start it Where the file lands Default lifespan
Platform-native
Meet, Teams, Zoom
Host, or a participant the host has granted permission The organiser's Drive or OneDrive; Zoom's pooled account storage Configurable Teams expiry (120-day default); Zoom storage allowance varies by plan
Cloud recorder bot Depends on the app, meeting admission and admin policy Check the vendor's storage and processing terms Set by the vendor's plan and retention terms
Local device
e.g. MirrorCaption
Whoever is at the keyboard, with consent handled by you Browser storage on your own machine Your setting — 10 recent sessions by default

None of the three is universally better. Platform-native suits a recording that should live inside corporate retention policy. A cloud bot suits a recording that must reach a CRM automatically, where the compliance boundary is already agreed. Local custody suits a working note for one person. The failure mode is landing in a column by accident, because someone connected a calendar and nobody weighed the question.

What Local Custody Looks Like in Practice

MirrorCaption sits in the third column, and it is worth being specific about what that means, because "local" gets used loosely.

Recording is off by default. Turning it on happens in Settings under Capture, and the toggle is gated behind a two-checkbox consent screen that names § 201 StGB and Code pénal art. 226-1 by statute. Both boxes must be checked before the feature switches on. This prompt does not determine which laws apply to your meeting.

Once enabled, the optional session recording is saved in your browser's local database and is not uploaded to MirrorCaption servers. Live audio is separately streamed to the speech-to-text provider for transcription. Retention is a number you choose: the default keeps the 10 most recent sessions, adjustable from 0 to 99, or set to never delete. When a session ages past your window it keeps its transcript and loses only the audio. One honest limitation — recording is not retroactive. If the toggle was off when the meeting started, that session's audio does not exist, and no setting will bring it back.

Capture itself is browser-tab audio in desktop Chrome or Microsoft Edge, so no bot joins the call and nothing appears in the participant list. Alongside the recording you get the live transcription layer running in the same tab — real-time transcription and translation across 50+ selectable languages, which is the part a pure recorder app leaves you to solve separately. If you want the reasoning on reading during the meeting versus reading after it, our piece on real-time versus post-meeting bilingual notes works through the trade-off.

Two Illustrative Workflows

The following two workflows are illustrative examples, not customer case studies. They are written to show how the custody question resolves differently depending on who owns the meeting.

Illustrative workflow 1 — the guest on someone else's call

A procurement lead joins three vendor Google Meet demos in a week. Each call was scheduled by the vendor and their host account permits recording, so a native recording would land in the vendor organiser's Drive. The lead has not been granted native recording permission. She is also on an iPhone for two of the three, where Google's native recording path does not exist.

The custody-correct answer is a local recorder on her own laptop for the calls she can attend from it, plus notes for the rest. What she must not assume is that a recorder app will hand her the vendor's file.

Illustrative workflow 2 — the recording that expired

A team lead recorded a scoping call in Teams in March and looks for it in November. If the tenant kept automatic expiry at the 120-day default and its work-account recycle bin at 93 days, the recording may already have been purged. Another policy or retention rule could change that result.

Raising the administrator default in November would not restore a purged file; changes to that default apply only to new recordings. Before expiry, an authorised owner might have changed that file's date.

Choosing a Meeting Recorder App: the Short Checklist

● Check entitlement before the meeting, not during it. If you are not the organiser, assume the native path is closed until you have confirmed otherwise. Our per-platform walkthrough for transcribing a Zoom meeting in real time covers the steps where they exist.
● Ask where the file lands. "It's saved automatically" is not an answer. Name the account that will hold it and confirm you have access to that account.
● Read the expiry default, then act on it. Export anything you might need in a year out of a system with a retention clock, while it still exists.
● Decide the consent question yourself. No app's terms of service substitute for knowing the rule in your jurisdiction and telling the room.
● Separate the recording from the record. A transcript you own is often more useful than an audio file you do not, and it survives storage quotas.

Frequently Asked Questions

Can I record a meeting if I'm not the host?

On Google Meet, participants can only record if the host has permission to record. Microsoft Teams and Zoom similarly tie the control to the organiser or an admin policy. A local recorder app on your own device sidesteps the platform control but not the consent question.

Where do meeting recordings actually get saved?

Usually not with the person who pressed record. Google Meet saves to the meeting organiser's Drive. Non-channel Teams meetings land in the organiser's OneDrive. Zoom cloud recordings use account-level pooled storage. A bot recorder may store data with its vendor; check the product's terms.

How long do Microsoft Teams recordings last?

Teams uses a configurable 120-day default expiration for new recordings and transcripts when automatic expiry is enabled. Changing the admin default does not update existing recordings, though owners may change dates on files they control. Expired files move to a recycle bin; work or school OneDrive items are normally removed after 93 days unless an administrator changes that setting.

Is it legal to record a meeting without telling everyone?

It depends entirely on jurisdiction. Germany's § 201 StGB penalises recording another person's non-publicly spoken word without authorisation. France's Code pénal art. 226-1 limits when consent may be presumed for a known recording. Check local rules before you press record.

Does a meeting recorder app have to join the call?

No. Bot-based recorders join as a visible participant, which is why Microsoft's Teams policy can detect them and hold them in the lobby. Browser-tab and device-level recorders capture audio locally instead, so nothing appears in the participant list.

The Decision Underneath the Download

A meeting recorder app is not really a recording product. It is a custody decision wearing a record button. Google Meet decides whether you may press it at all; Microsoft Teams decides how long the result lives; Zoom decides how much of it fits. The app you install decides only which of those three regimes you signed up for.

So before comparing feature lists, answer three things. Are you entitled to record this meeting, and under whose permission? Whose account will hold the file? And what default deletes it, on a calendar you did not set? If the honest answers are "I'm a guest," "not mine," and "I don't know," local custody is the model that fits — and a meeting recorder app that writes to your own device is where to start looking.

Keep the recording, and the transcript

1 free hour to try. No bot joins the meeting. Optional session recording is consent-gated and stored on your device; live audio is processed for transcription.

Open MirrorCaption Free