Where Swiss Companies Meeting Data Goes After a Call

Where Swiss companies meeting data goes is a map of copies, not a verdict under Swiss law. After a call, the same conversation can sit in Zoom’s cloud, in a Teams OneDrive folder, in a US notetaker account, on one laptop, or in a browser tab that never uploaded the file. This page names those usual places, using vendor documentation as of September 2026. It is not legal advice. It does not say what the revised Swiss data protection act requires, and it does not call any product compliant, certified, or safe for your contract.

If you need the legal reading (information duty, processors, retention), that is a different article, for counsel. Here the job is narrower: know which copy you created, and which vendor page describes it.

Contents

• Where Swiss companies meeting data goes in practice
• The meeting app’s own cloud
• A notetaker that joined the call
• A file that never left the tab
• A recording that stayed on the Mac
• How many copies a single sitting can create
• What this page does not decide
• Frequently asked questions

Where Swiss companies meeting data goes in practice

A Swiss GmbH, a Treuhand, a consultancy in Zurich, or a team with clients in Germany still uses the same four pipes everyone else uses. The company seat does not move the bits. The product you clicked does.

Ask one question after every meeting that was recorded or summarized: which system has a copy, and what does that vendor say about the copy? Write the answer in the minutes if the sitting was sensitive. “We used Teams cloud recording; file is in the organizer’s OneDrive” is a complete sentence. “It should be fine, we are in Switzerland” is not.

Typical destinations, each documented by the vendor, not by this blog. A tenant’s hosted region can change when an admin updates data-location settings. Check the admin view in the month you fill the form.

Vendor pages change. Recheck them the month you fill a security form. The September 2026 reading is what this article used.

The meeting app’s own cloud

Zoom. Cloud recording lives in Zoom’s web portal. On eligible plans it can include a VTT transcript. Zoom AI Companion is a Zoom feature, not a guest bot. Zoom states that it does not use customer audio, video, chat, or similar communications content to train Zoom’s or third-party AI models, and that it still must process content to provide the feature. Hosted region and optional EEA residency controls are account settings. EEA is not Switzerland. Details and links: Zoom AI Companion privacy.

Microsoft Teams. A cloud recording lands in the organizer’s OneDrive for a private meeting, or in the channel SharePoint library for a channel meeting, according to Microsoft’s recording documentation. Copilot prompts and answers are stored as interaction history. Microsoft lists Switzerland among countries that can have local-region residency for core Microsoft 365 workloads, if the tenant is actually provisioned that way. Microsoft also says customers outside the EU may have Copilot queries processed in the US, the EU, or other regions. Switzerland is not in the EU Data Boundary. Details: Teams Copilot data location in Switzerland.

Google Meet and others. The same pattern: if you used the platform’s recording or summary, the copy is in that platform’s account, under that platform’s retention. Read that vendor’s admin help, not a generic “Swiss cloud” assumption.

None of these products become Swiss-hosted because the participants sat in Zug. The signup country, the admin’s data-location card, and the feature you enabled decide the map.

A notetaker that joined the call

Calendar-linked assistants join as a named participant. Everyone can see them. That visibility is useful. It is also why many client-facing teams ban them.

Otter documents cloud compute and storage with Amazon Web Services in the United States, and describes training of its own models on de-identified audio and transcripts. That is Otter’s page, summarized in is Otter.ai safe. Fireflies and similar products publish their own storage and training terms. Read those pages; do not copy Otter’s sentences onto another logo.

A Swiss company that invites a US notetaker has created a copy in that vendor’s cloud, whatever the GmbH’s register address says. If the invitation said “no AI notetaker,” the bot is the copy you were asked not to make. Meeting notes without a bot explains the roster problem. This page only places the file.

A file that never left the tab

Sometimes the meeting is already over and you hold an M4A or MP3. An upload site creates a new processor. A tab that downloads a speech model and runs it locally does not send the file to Vemoir. Users can watch the Network tab.

The free transcribe recording tool works that way: files up to 15 minutes, three successful runs a week, MP3, M4A, WAV, or MP4. No speaker labels. Swiss German speech usually comes out as Standard German text. It is not a live recorder and it is not a team archive.

That path answers “where does this file go” with “it stays in the browser, plus the original still on your disk.” It does not answer “where did the live call go” if Zoom or Teams already stored a cloud recording.

A recording that stayed on the Mac

Local Zoom recording writes a folder on the computer that clicked Record, typically under Documents, with an audio_only.m4a or similar M4A. Zoom does not keep a cloud backup of that local folder. Delete the folder and that copy is gone.

A menu-bar app can record the Mac’s microphone and system audio while Teams, Zoom, Meet, Slack, or Discord plays. No extra participant appears. After you stop, transcription can run on that Mac with local models. Exports are a later, conscious step. Optional cloud text, if the user turns it on with their own API key, is text, not the audio file.

Vemoir is one such Mac app, made in Oberägeri. It needs Apple silicon and macOS Sonoma 14.2 or later. Intel Macs are not supported. Once the chosen models are installed, the meeting workflow can run offline. Internet is for setup and downloads. That is a location statement: the record stays on the Mac until you share it. It is not a legal clearance.

If two people record locally, you have two folders. Agree who records.

How many copies a single sitting can create

A messy but common pattern for a Swiss client call:

1. The host turns on Teams cloud recording. Copy in OneDrive.
2. Someone enables Copilot recap. Interaction history in Microsoft 365.
3. A colleague’s Otter bot joins. Copy in Otter’s US cloud, plus a visible guest.
4. You also recorded locally “just in case.” Copy on your Mac.

That is four systems, four retention clocks, four deletion chores. The minutes should say which copy is the official one. If the official copy is the Teams file, delete or refrain from the extras next time. If the official copy must stay off cloud recorders, do not press Record in Teams and do not invite the bot.

Cloud is not automatically careless. Plenty of firms pick one approved vendor, read the data-location card, and want a shared library. The failure mode is untracked extras, not the existence of OneDrive.

What this page does not decide

This is not a guide to the revised Federal Act on Data Protection, and it is not a substitute for the FDPIC or for counsel. French- and Italian-speaking readers will see the law abbreviated as nLPD; German speakers often say nDSG. Naming the act does not interpret it.

This page does not say that local processing is required, that US hosting is forbidden, or that a Swiss data center makes a product lawful. It does not call Vemoir, Zoom, Microsoft, or Otter compliant, GDPR-certified, or HIPAA-certified.

Consent to record, how long you keep a file, and whether a processor is allowed remain your decisions. A tidy map of copies only tells you what you already made.

If you already have a short file and you want text without adding a vendor, use transcribe a recording. If you are choosing a live tool, read that vendor’s current privacy page the same week you decide.

Frequently asked questions

Where does Zoom put meeting recordings?

Cloud recordings sit in Zoom’s portal, in the hosted region the account uses. Local recordings sit on the computer that recorded. AI Companion is a further Zoom processing path. See Zoom’s own AI data article and Zoom AI Companion privacy.

Where does Teams put meeting recordings?

In OneDrive or SharePoint, as Microsoft’s recording pages describe. Copilot history is stored separately. See Teams Copilot data location in Switzerland.

Where do Otter and Fireflies store calls?

On those vendors’ clouds. Otter documents AWS in the United States. Read each vendor’s privacy and security pages the month you ask. A starting point for Otter is is Otter.ai safe.

What stays on the Mac?

A local Zoom folder, a menu-bar recording, or an imported audio file that you never upload. Exports create a new copy wherever you send them.

Is this legal advice under the nLPD or nDSG?

No. This is a map of product copies from vendor documentation. Ask counsel for the legal reading.

Does a Swiss company have to use a Swiss host?

This page does not say that. Some vendors offer regional hosting; others do not. Your contract and your counsel decide what is acceptable. A Swiss register address does not relocate a US bucket.

What is a second copy?

Any extra system that received the same audio or transcript: a bot, a second cloud recorder, a forwarded link, a download to a USB stick. Count them. Delete the ones you did not mean to create.

How do I check a vendor this month?

Open that vendor’s privacy, security, and residency pages, note the date, and screenshot the admin data-location view if there is one. Do not rely on a blog after the vendor has changed the page.

If the next file should stay in the tab, use transcribe a recording. If you want the live call to stay on one Mac, record there and write down that this was the only copy.