Is Krisp safe? What stays on your computer and what goes to Krisp's cloud

Is Krisp safe? For the thing most people install it for, the noise filter, the answer is yes. Krisp's privacy policy says that when you only use noise cancellation, no audio or video leaves your computer and Krisp has no access to the conversation. The note taker is a separate product on the same app, and once it is on, your transcripts, summaries and recordings live in Krisp's cloud.

So "is Krisp safe" is really two questions. This post answers both from Krisp's own pages, checked 9 November 2026, and says where Krisp's documents disagree with each other.

Is the Krisp app safe to download?

Krisp is made by Krisp Technologies, Inc., based in Berkeley, California. It is an established product with a public security page, a Trust Center that offers its SOC 2 Type II report and pen test summaries, and a bug bounty on HackerOne.

The one download risk is specific to how Krisp works. It installs a Krisp Microphone and a Krisp Speaker, and you select those inside Zoom, Teams or Meet so audio passes through Krisp first. Any app in that position hears every word you say on a call. Get the installer from krisp.ai and nowhere else, and skip anything that promises a cracked paid tier. There is a 7-day trial, so there is no reason to look elsewhere.

Noise cancellation only: what leaves your computer

Very little. The privacy policy, last updated 28 September 2026, says Krisp does not have access to or store any audiovisual data when you use only the noise cancellation feature. Krisp's help article What data Krisp sends to the cloud? says the same thing and adds that when you test noise cancellation inside the app, that test recording also stays on the device.

Two caveats. The same help article says Krisp stores analytics events "to monitor and improve your experience", so usage data does go to Krisp even when audio does not. And Krisp's security page for the AI Meeting Assistant says the desktop and mobile apps need the Krisp backend to run. If the backend is unreachable, the app stops. Read as written, that includes the noise filter: it processes audio locally but still needs a connection to Krisp to run.

If you only want clean audio, you can use Krisp with the note taker off. The recording FAQ says the note taker has to be off before the call starts and stay off to prevent recordings and transcripts.

Once the note taker is on: where your meetings go

Krisp's security page includes a data map. These are its rows for meeting content, as of 9 November 2026:

Data	Processed	Stored in Krisp's cloud
Noise cancellation	On your computer	Never
English transcription in the desktop app	On your computer	Only if you save the meeting
Other languages in the desktop app	In the cloud, by Baseten	Only if you save the meeting
Mobile app and uploaded files	In the cloud, by Baseten	Transcript, summary and audio; non-English audio deleted once the transcript is ready
Recordings (audio, video, screen)	Device, then cloud	Until you delete them
Summaries, action items, AI Chat	Anthropic Claude on AWS Bedrock	Kept with the meeting until you delete it
Integrations and MCP	Cloud	Tokens and the data you choose to sync
Calendar	Cloud	Event titles, times, attendees, if you connect a calendar

Storage is 10 GB on Core, 60 GB on Advanced and unlimited on Enterprise. Data is stored in the United States by default, on AWS. On-device transcripts and recordings, which Krisp calls private mode, are an Enterprise feature.

Krisp's pages do not fully agree on transcription. The security page and the AI Meeting Assistant FAQ say English is transcribed on your device. The help article on cloud data says "your meetings are transcribed in the cloud, and the data used for transcription is deleted immediately after processing." I would treat the security page as current, since it is the more detailed document. Either way, saved meetings end up in the cloud. The on-device step changes where the transcript is made, not where it is kept.

Non-English speech has its own rule. The privacy policy says that in Transcribe only mode, if Krisp detects non-English speech, it may record the audio automatically so it can transcribe it, and deletes that audio from its servers once the transcript exists. If your meetings switch between languages, expect some audio to reach Krisp even in the mode that sounds like it records nothing.

Does Krisp record your conversations?

Only with the note taker on. Krisp's help center lists four modes: Transcribe only, Audio Recording, Screen Recording and Off. Recordings are stored in the cloud, and the help center says deleting your account removes them along with the rest of your data. The security page says deleted transcripts, summaries and recordings are hard-deleted, not archived.

People do get surprised by it. A Reddit thread in r/digitalnomad asks why Krisp kept recording during a trial even after the user disconnected their calendar. The fix in Krisp's own FAQ is the one above: switch the note taker to Off.

The setting worth checking first is sharing. Krisp's Auto-share help page says Auto-Share can send transcripts, notes and recordings to participants from your calendar invite. One option is "All meeting invitees", which the page defines as everyone on the invite, including external guests. Team admins can enforce a choice. The team default is "User's choice", so look at Settings, AI Note Taker, Sharing before your first client call. Krisp's pricing FAQ also says signup asks for a Google or Outlook calendar by default, with a zero-calendar-permission option available, so the calendar row above is less optional than the data map suggests.

Does Krisp use your data to train AI?

Krisp says no, in two places. The pricing page FAQ says "Your meeting data is never used to train Krisp's AI models." The security page says Krisp has opted out of model training with every third-party AI provider, and that meeting content is used only to deliver the features you turned on, not for ads or resale.

The privacy policy adds a line that is easy to miss. In its table of processing purposes, it lists "Improving our proprietary AI models and providing more accurate services", with consent as the legal basis. That does not contradict the pricing page on its face, because the policy covers personal information in general. It does mean Krisp's no-training promises sit on its pricing and security pages, not in the privacy policy. If training is a deal-breaker for you, ask Krisp to put it in your contract.

Has Krisp had a data breach?

Krisp disclosed one incident itself. In a post dated 3 April 2026, Krisp MCP Incident Communication, Krisp says it was notified on 31 March that a user of the AI Meeting Assistant had received content belonging to another user through its MCP API, a feature Krisp says it launched recently that lets AI tools and assistants interact with Krisp. Krisp traced it to two users making requests at exactly the same moment, when the system could deliver one user's response to the other. It called this a technical flaw rather than an attack, and published a timeline from the report at 6:17 PM to a fix in production at 9:45 PM. It said it was reviewing whether other users were affected and would contact them if so.

That is a real cross-account exposure, and Krisp disclosed it publicly with a timeline. It is also a reminder of what the security page says plainly: each account's data is isolated by access controls in the application, and databases and storage are shared infrastructure. A bug in the application layer is the kind of thing that can leak across accounts.

I did not find another publicly reported Krisp breach as of 9 November 2026. The one lawsuit I found, Sanas.AI v. Krisp Technologies (N.D. Cal., No. 3:25-cv-05666), is a patent and trade secret dispute over accent conversion, not a privacy case.

What Krisp publishes about security

From Krisp's security pages, checked 9 November 2026:

• SOC 2 Type II, with the report available through the Trust Center. Krisp's plan table lists SOC 2 report access as an Enterprise control.
• PCI DSS, which Krisp says covers card details people may read out on calls.
• HIPAA safeguards, with Business Associate Agreements on the Enterprise plan for teams of 100 or more seats.
• AES-256 encryption at rest for databases, transcripts, recordings and backups, and TLS 1.2 or higher in transit.
• Standing access to customer data limited to a small group of senior engineering leads, with time-bound approval for anyone else.
• A published sub-processor list in the Trust Center.

Those are the controls you would expect from a business software vendor. The HIPAA line needs care. The BAA is Enterprise-only with a 100-seat minimum, so a solo clinician on Core is not covered by it. Our Krisp pricing breakdown has the plan details.

The consent question

Krisp's note taker is bot-free by default, which means nobody else on the call sees a participant named Krisp. That is the appeal, and it moves the job of telling people onto you.

Krisp has a setting for it. The recording help page says you can turn on Notify others you're using Krisp under Settings, Privacy & Consent. Krisp's release notes for version 3.8.2 say that with notifications on, Krisp plays a short audio prompt and can post a chat message in Zoom, Teams and Google Meet, falling back to the audio prompt if you do not grant it accessibility access. The help page also warns that some platforms block those messages, so tell people another way too. If you send Krisp's optional meeting bot instead, it joins as a participant, and the same release notes say it posts a one-click removal link in the chat. In all-party consent states and much of Europe, that is your legal exposure, whichever tool you use. The details are in our post on meeting recording consent laws.

So is Krisp safe?

For noise cancellation alone, yes. I would be comfortable running the filter on almost any call, including confidential ones, given what the privacy policy and help center say about local processing.

For the note taker, Krisp is a documented cloud service with published controls and one disclosed incident. Your saved meetings sit on Krisp's servers in the US until you delete them. The on-device private mode needs an Enterprise contract. For internal standups that is a reasonable trade. For a client's deal terms or a patient's symptoms, decide whether you want any cloud copy at all, because that copy is the risk left over after every policy has done its job.

Where Private Notetaker fits

We make a competing product, so here is the trade as I see it.

Krisp does things we do not. Its noise filter cleans both sides of the call, it has accent conversion, its help center lists 16 transcription languages, and it has a team workspace with sharing and CRM integrations. Private Notetaker has none of that and works in English only.

What we do differently is where the meeting ends up. Private Notetaker runs on your Mac or Windows PC. It records the call, transcribes it and writes the summary on your machine, and the audio stays on the device. No bot joins the call. There is no cloud archive to share by accident, and the app works with the network off. It costs $15 a month or $149 once, with a 7-day trial and no card.

If you want the side by side, see Private Notetaker vs Krisp. The full Krisp review covers the product beyond privacy, and Krisp alternatives includes tools that are not ours. If local notes are what you were after, you can try it free.

We have run the same check on Otter, Granola and Fireflies.

Krisp claims are quoted from krisp.ai: the privacy policy (last updated 28 September 2026), the security pages, the pricing page, the AI Meeting Assistant page, help center articles on cloud data, recording and auto-share, the 3.8.2 release notes, and Krisp's 3 April 2026 incident post, all checked 9 November 2026. Court details are from the public docket. Vendor pages change, so verify before relying on this.