The meeting ends. You close the laptop, forget the argument about the Friday deadline, and get on with the next thing. Somewhere, a transcript has just acquired a life of its own.
That sounds more dramatic than it is. A transcript is useful precisely because it outlives the call. Someone who missed it can catch up. A manager can find the decision six months later. A client can check what was agreed. Those are good things. The awkward bit is that “the transcript” does not have one obvious owner. The person who spoke is not necessarily the person who started it. The person who started it is not necessarily the person who can delete it. And the people who can open it are sometimes decided by an admin setting nobody in the meeting has seen.
I build a meeting recorder that keeps the recording and live transcript on the computer that made them, so I have a stake here. A local file is not automatically better. If your job is to build a shared institutional memory, a cloud record with a clear team owner may be exactly what you need. I wanted to understand the mechanism instead of calling either choice “private” and moving on.
The useful question is not “who owns the meeting?” It is four smaller questions: where does the record live, who gets the first link, who can share it, and who can delete it? Google Meet, Microsoft Teams and Zoom give three different answers. A recorder that writes to your own disk gives a fourth.
Ownership is four things, not one
In ordinary conversation, “I own the transcript” can mean any of four things. I can find it. I can read it. I can send it to somebody else. I can make it go away. Software turns those into separate permissions because they are separate jobs. That is sensible. It is also why the casual answer “it is in the meeting” tells you almost nothing.
The storage home is the first one to understand. A platform-native record usually follows the organizer or host into that platform's document system. That makes sharing with the team convenient, and it gives the organization policy controls. A bot notetaker usually creates a record in the account or workspace that invited it. A desktop app can create a record in a folder on the recorder's computer. None of those is an ethical judgment. They are different answers to the operational question: what happens when the browser tab closes?
The second question is who receives the first link. That small moment often decides the practical owner. If the organizer gets the link, they become the person everyone asks. If the whole internal invite list gets it, the record behaves more like a shared meeting attachment. If it sits only on the recorder's disk, there is no link until they make one.
Then comes the part teams forget: an organization can have powers that the person who pressed Record does not. This is not sinister. A company may need to retain a customer call, investigate an incident, or apply a deletion schedule. But it means “I recorded it” and “I control it” are different statements.
Google Meet: the organizer's Drive, attached back to the event
Google Meet makes the storage home unusually explicit. Its transcript help says the file is saved in the meeting organizer's Google Drive, in the Google Meet folder, with a subfolder for that meeting.1 When the meeting ends, Google sends a link to the host, co-hosts and the person who started transcription. It also attaches the transcript to the Calendar event.1
That is a strong default for an internal recurring meeting. The record has a predictable home, and the people arranging the meeting get it without someone remembering to mail a file around. But the Calendar attachment is doing real work here. Google's documentation says all invitees in the host's organization can open that attachment, subject to a special rule for events with more than 200 invitees.1 The person who turned transcription on may have made a record whose audience is wider than the people who happened to be speaking when it started.
Google also lets an administrator require explicit participant consent for recording, transcription or “take notes for me”. That setting is off by default, according to its help page.1 Notice what that does and does not answer. It decides whether people must acknowledge capture. It does not replace the access rule after the call. A consent prompt and a sharing policy are two different controls.
Microsoft Teams: the organizer's OneDrive, then the meeting's access policy
Teams takes a similar route, but makes the permission layers more visible. Microsoft's live-transcription documentation says a meeting transcript is stored in the meeting organizer's OneDrive for Business and can be reached through the meeting chat and Recap tab until an organizer deletes it.2 That is the storage answer. It is not the whole access answer.
For eligible Teams Premium or Copilot meetings, the organizer can set transcript and recording access to Everyone, Organizers and co-organizers, or Specific people. Microsoft says Everyone is the default.3 The same page notes that changing the choice during a meeting requires ending and restarting it to take effect. This is the kind of detail that sounds fussy until someone asks why the external consultant cannot see the recap, or why the new hire can.
Teams also separates who can start a transcript from who can see it. Microsoft documents organizer, co-organizer and presenter roles, plus tenant and meeting settings, for starting and downloading transcripts.2 Again, that is not a criticism. A shared team record needs controls. It is simply a reminder that a transcript in a work platform is a work document. It lives inside the organization's account structure, not in the air between the participants.
Zoom: the host's cloud record, under account policy
Zoom has a third shape. A cloud recording stores its video, audio and chat text in Zoom's cloud. Once processing finishes, Zoom says it emails the host and gives the host share options.4 The host can share a link broadly, require sign-in, restrict it to domains, name specific internal or external people, set an expiry date, and decide whether viewers can see the transcript or download files.5
That sounds like the host has full control. Sometimes they do. Zoom's account documentation is clear that an owner or administrator can manage recordings across the account, while a user needs the account owner or admin to grant editing or deletion permission.5 An admin can also configure automatic deletion, prevent hosts from accessing their own cloud recordings, or make the host unable to delete them.6
That is the most useful sentence in this article: the host may be the steward of a recording without being its final authority. For a regulated or carefully managed team, that can be exactly right. For a personal conversation, it may be more machinery than anyone intended to create.
A notetaker workspace can be private first, too
There is another shape between a platform record and a file on your disk: a note inside the notetaker's own workspace. Granola says its notes are private by default and are not automatically shared with meeting participants. When you share one, recipients get Viewer access by default; its documentation also distinguishes between a web viewer, who cannot see the full transcript, and a desktop collaborator with the permissions that come from the note or folder.7 That is a very deliberate answer to “who gets the first link?”: nobody, until the note owner decides.
Notion's AI Meeting Notes takes a different route again. A note inherits the permissions of its parent page, and a note on a private page is private by default. Its optional auto-share feature is limited to calendar participants who are workspace members.8 Neither product is right for every team. The useful point is that “cloud” does not tell you the default audience. You have to ask whether the record follows a calendar event, a host account, a workspace page or the person who made the note.
The local route: a file before it is a shared record
MidMeeting takes the fourth path. It captures the microphone and speaker tracks, transcribes them on the computer, and keeps the audio and transcript on that computer. There is no MidMeeting account that receives the file and no team workspace that gets a link. If the optional advisors are on, transcript text goes only to the model provider you chose. Turn them off and it is a local recorder and transcriber.
That makes the practical owner simple: the person with the computer and its user account has the record. They can export a transcript or report when sharing makes sense. Nobody else gets it by default. It also means the product is not a substitute for a company meeting archive. There is no shared library, no organization-wide search, no administrator who can recover a former employee's notes, and no magical backup beyond the backups you choose for your computer.
That last sentence is not a minor footnote. Local files are easier to keep private by default, but they are also easier to lose, fail to back up, or leave behind in a folder nobody can find. A team that needs a durable record owned by the organization should use the system built for that job, then decide its access and retention policy deliberately.
Choose the owner before the meeting, not after it
I would ask four questions before recording any meeting that matters:
- Where will the record live? A Drive, OneDrive, vendor workspace or one person's computer are different promises.
- Who gets it first? The organizer, the whole internal invite list, a named group or nobody until it is shared?
- Who can share or delete it? Check the role and account policy, not just the button you can see.
- How long should it exist? A transcript is not a harmless diary entry. It is a searchable record of people thinking out loud.
Those questions make the choice less ideological. A sales team may want the Zoom or Teams path because the company should keep the record after the rep moves on. A project team in Google Workspace may want the Calendar attachment because the invite list is the right audience. A freelance designer may want a local transcript because the client does not need a standing copy of every half-formed thought. All three are reasonable. The mistake is taking the default without noticing what it decided.
The trade-offs
A local record is not invisible, and it is not a legal escape hatch. Tell people you are recording. Secure the computer. Think about backups, exports and any AI service that receives transcript text. A file on your disk can still be copied, synced or subpoenaed. “Local” describes the first storage location, not an amnesty from responsibility.
Cloud records make the opposite trade. They make continuity, handover and sharing much easier, but the record belongs to a system with administrators, retention settings and its own access model. If that is the model your team needs, use it proudly. Just make sure everyone knows which system has the meeting when the meeting is over.
MidMeeting is for the moments when you want a sharp set of notes for yourself while the conversation is happening, and you want the raw record to start and stay with you. Three meetings are free. After that it is $39 once, for up to three of your own computers.
Sources
- Google Meet Help, “Use Transcripts with Google Meet”checked 15 September 2026
- Microsoft Support, “Start, stop, and download live transcripts in Microsoft Teams meetings”checked 15 September 2026
- Microsoft Support, “Customize who can access a recording or transcript in Microsoft Teams”checked 15 September 2026
- Zoom Support, “Starting a cloud recording”checked 15 September 2026
- Zoom Support, “Managing and sharing cloud recordings”checked 15 September 2026
- Zoom Support, “Managing cloud recording settings”checked 15 September 2026
- Granola Help, “Sharing notes”checked 15 September 2026
- Notion Help, “AI Meeting Notes”checked 15 September 2026