How Wispr Flow Notetaker handles recording notice and consent

Last updated: November 21, 2026

Available on: Mac, Windows

Notetaker records audio on your computer without joining the call as a participant; Wispr transcribes it in the cloud. Its controls help you notify participants and confirm you obtained permission, but do not collect individual participant consent.

Important: This is not legal advice. Consult your own legal or compliance advisors.


Notice and consent are different things

Notice tells participants transcription is happening so they can ask for it to stop. Affirmative consent means each participant accepts before capture, with their audio withheld until acceptance.

Notetaker captures your microphone and the combined audio of remote participants; it cannot isolate one person's audio from that mix. Your meeting platform will not post its own recording notice when Notetaker records.

Transcripts can still name speakers in Google Meet and native Zoom on Mac and Windows, using meeting-participant and calendar information. Uncertain matches remain “Speaker N”; Windows Teams transcripts remain anonymous.

Providing required notices and obtaining required consents before using Notetaker remains your responsibility under Wispr's Terms of Service.

What Notetaker cannot do

  • Collect per-participant opt-in: it cannot prompt someone on their own screen, withhold their audio, or exclude people who decline from the mixed meeting audio.

  • Play an audio announcement to the call: this would still be notice rather than consent, with the same late-joiner gap as the chat notice.

  • Re-post the chat notice when someone joins: joins cannot be detected reliably.


Controls available today

The chat notice and confirmation prompt are independent; enabling one does not enable the other.

Control

Default

What it does

Consent notice in meeting chat

Off

Posts a participant-visible disclosure when recording starts.

Confirmation prompt before recording

Off

Blocks recording until the recorder confirms they obtained participants' consent.

Configure your chat notice

Posting requires a Business/Enterprise organization context or an explicit member opt-in. The desktop setting appears only for qualifying organizations.

Note: Notices support Zoom, Microsoft Teams, Google Meet and Slack huddles, including desktop and browser meetings. Mac browser meetings require Google Chrome; posting on Mac requires Accessibility permission.

  1. Open Flow's Settings → Notetaker → Consent.

  2. Enable the chat notice, if available and not managed by your organization.

  3. Edit the message if needed; the limit is 450 characters.

Organization controls

Organization controls live in the admin portal under Settings → Organization, not desktop Settings. Only admins can change them; editing the organization-wide message also requires the Enterprise plan.

Control access varies by organization. Organizations already requiring consent confirmation retain access; Enterprise admins may see “Contact sales” instead of an editable “Require consent confirmation” control.

An admin-enforced notice locks the switch and text for all members, marked “managed by your organization.” Disabling notices organization-wide stops both automatic posts and manual prompts.

Default messages are translated per member; custom organization text is shown to everyone in English. Restore default restores per-member translation.

How the chat notice behaves

Only people in the call at that moment see the message; late joiners may not, depending on how your platform handles earlier chat.

Posting briefly brings the meeting window forward. On Windows, a minimized Google Meet window is shown without taking focus; your previous foreground window is then restored.

A confirmed notice suppresses another in the same chat for 120 seconds, including a restarted recording. A pending send prevents a duplicate automatic post but, if unconfirmed, still leads to a manual prompt.


Confirm consent before recording

This prompt records your confirmation, not consent from other participants. It appears only for organization members whose admin requires it; there is no personal desktop setting. It does not apply to mobile recordings or the Notetaker tour/demo.

  1. Obtain participants' permission before recording.

  2. Select “Consent obtained” in “Obtain consent to start Notetaker,” or “Cancel” to leave recording stopped.

You have 30 seconds to answer. If time expires or the window closes, reloads or crashes, recording does not start and Flow shows a failed-to-start notification. There is no close button; any other dismissal leaves recording stopped.


If the chat notice does not post

A detected lobby or unsent chat draft delays posting. Host-disabled chat, missing or ambiguous meeting windows/tabs, missing chat boxes, an unreachable browser, missing Accessibility permission or an unsupported platform can prevent posting.

If detection takes 60 seconds or sending cannot finish, Flow requests a manual notice. This includes in-person meetings, Discord and Webex. Manual prompts require a real meeting in progress with notices enabled—not the tour/demo.

The prompt appears as a Flow bar card or a dialog; you cannot choose which. Check chat before sending again because an unconfirmed notice may already have posted.

Warning: If you cannot give notice and choose the discard option, confirming discards the meeting. Clicking outside the dialog will not dismiss it.

  1. Grant Accessibility permission through “Open Settings” if the prompt requests it on Mac.

  2. Check the meeting chat; if the notice is already there, skip to step 5.

  3. Select “Copy” if the notice is missing.

  4. Send the copied notice in the meeting chat.

  5. Select “Done” after confirming the notice appears in chat.


Audio retention and training

Meeting audio deletion

Uploaded audio has a default seven-day retention window after successful upload. Deletion is automatic after that deadline and after processing finishes—not exactly at day seven. Account-specific windows can range from 0–30 days; Wispr staff accounts use 30 days. Contact support if your policy requires a guaranteed deadline.

Local desktop audio remains for 14 days after processing finishes, or at least 30 days while upload or processing is unfinished.

Training on your content

Growth and Enterprise block data sharing organization-wide, overriding personal sharing settings; neither admins nor members can re-enable it. Your meeting content is not used for training. Former members remain excluded from training collection while their last organization blocks sharing.

Retained copies and reporting exceptions

Where collection is enabled, meetings eligible for data sharing can have training copies, including audio, retained until 180 days after meeting creation. Training-copy and report-based evaluation collection are off by default.

Where report-based collection is enabled, a meeting or inline report filed by the meeting owner can result in an evaluation-only copy of audio, transcript and related meeting data until 180 days after meeting creation—even when personal or organization sharing is off, including on Growth and Enterprise. Another person's report or a training upload does not qualify.

An organization's locked Zero Data Retention policy blocks reported-meeting copies. An active HIPAA BAA for you or your organization blocks all training and evaluation copies, regardless of plan or consent.

Turning data sharing off does not withdraw existing copies. Retained copies are also removed in response to account deletion or data-deletion requests; ask support about previously derived datasets.


If your policy requires affirmative consent

Before relying on Google Meet native recording for consent:

  1. Verify your Workspace edition supports recording using Google Meet's recording requirements.

  2. Confirm your Workspace administrator enabled recording for your account and the consent requirement, which is off by default.

  3. Verify the host has recording permission; participants can record only if the host does.

Turn on your meeting platform's native recording, such as Zoom or Google Meet, and run Notetaker alongside it.

Google Meet notifies participants when recording starts or stops and warns late joiners on screen. Explicit consent prompts, including for late joiners, require the enabled admin consent setting; notifications alone are not a consent requirement.

Google Meet recordings are saved in the organizer's Google Drive “Google Meet” folder and count against Drive quota. Recording stops automatically after eight hours; a link is emailed to the organizer and whoever started recording.


Still need help?

Contact your Wispr Flow admin or support if notice delivery still fails after these steps, consent confirmation prevents recording, or your policy needs other controls. Include your platform, meeting app, policy requirement and what you tried.