How to Turn Off the Krisp AI Note Taker
Krisp includes AI note-taking alongside its noise cancellation. Here is how to review the recording settings, turn off automatic capture, and document your team's approved rules for meeting assistants.
Updated 4 min read
Krisp is primarily a noise-cancellation tool, but it also includes AI meeting notes that can capture and summarize calls. If you want to stop the note-taking while keeping the noise cancellation, or turn off Krisp's meeting capture entirely, the settings are in the Krisp application itself.
For teams where meeting recording is a shared decision, keeping the agreed rules in a shared place matters. A tool like fenbs lets your team record which meeting assistants are approved and under what conditions, so the policy is visible to everyone rather than relying on individual memory.
What Krisp AI note-taking does
Krisp's AI note-taking feature records and transcribes a meeting, then generates a summary. It runs on top of the noise cancellation, so you can have one without the other. When note-taking is enabled, Krisp captures audio from your side of the call and processes it to create the transcript and summary.
This is separate from your meeting platform's own recording. Krisp works at the application level on your device, so it captures what your microphone picks up regardless of which meeting platform you use.
Turn off AI note-taking in Krisp
Open the Krisp application on your device. Find the AI note-taking or Meeting Notes section in the settings. You can toggle note-taking off for all meetings or adjust whether it starts automatically when you join a call. For current navigation steps, check the Krisp help center (opens in a new tab) as the interface updates periodically.
If you want to keep noise cancellation active but stop note-taking, look for a setting that separates the two features. Krisp allows you to run the noise filter without recording the call content.
On a Mac, Krisp runs as a menu bar application. On Windows, it runs in the system tray. The settings panel is accessible from either location.
Review auto-start and permissions
Check whether Krisp is set to start note-taking automatically when a meeting begins. Auto-start is convenient if you always want notes, but it means every call is captured without a manual trigger. If that is not your intention, turn auto-start off so you can choose when to take notes.
Also review the microphone and audio permissions Krisp has been granted on your device. On macOS, these are in System Settings under Privacy and Security, then Microphone. On Windows, check Microphone Privacy settings. Krisp needs microphone access for noise cancellation, so removing that permission will affect both features.
What happens to notes already captured
Notes captured before you turn off the feature are stored in your Krisp account. Review the Krisp app or your account dashboard to see what has been saved. Krisp's settings or their support documentation will describe how to delete stored notes and transcripts.
If your organization has a team Krisp account, check whether meeting summaries are being shared with other team members automatically. The team settings control what is visible to whom.
For a broader review of AI note-taking options, see AI meeting note taker. That guide covers how to choose a tool that fits your team's recording policy.
Set a team policy before the next meeting
If you are turning off Krisp note-taking because it was capturing calls without clear team agreement, write the policy now. Which tools are permitted to record meetings? Does the whole team need to be told when a call is being captured? What is the retention period for notes?
A short written policy removes the ambiguity the next time a team member installs a new meeting tool or enables a feature they were not sure about. It also gives a clear answer when external participants ask whether a call is being recorded.
Your policy should cover more than which tools are permitted. Include how long recordings may be kept, who may access them, and what happens when a team member leaves the organization. A note-taking tool that stores transcripts in a cloud account associated with a former employee is a loose end worth closing.
When you onboard a new team member, include the meeting-recording policy in their setup materials alongside the other tools they will use. That is the point at which habits form. A policy that only surfaces after someone has made a mistake is harder to enforce consistently than one that arrives before their first recorded meeting.
Keep your meeting-assistant policy in one place
Record your approved meeting tools and recording rules as Decisions in fenbs. Every team member and connected AI app reads those rules before starting work, so the policy is visible rather than relying on whoever remembers the last conversation about it.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account. Start a project for your AI governance or meeting-tool rules.
- Add a Decision naming which meeting assistants and recording tools are approved for team use.
- Add a Decision covering what participants must be told before a recording starts.
- Connect your AI apps over MCP from Integrations so they read the Decisions before answering meeting-related questions.
- Review the Decisions when a new meeting tool is proposed or when team members change.
A personal board is free and a good starting point if you are managing your own tool decisions. A team board gives each member a role and keeps History so you can see exactly when and why the meeting-recording policy changed.