Krisp Buyer's Checklist: Security, Consent, Seats and Plan Gates

Before a team rolls Krisp out, five questions need a written answer: does the compliance you need sit on a plan you can afford, who owns recording consent, which admin controls are gated, what happens to recordings when someone leaves, and does every laptop run Mac or Windows. On is Krisp safe, the short version: Krisp says it holds SOC 2 Type II on every plan and runs noise cancellation on the device. The SOC 2 report itself, SSO and SCIM are Enterprise items. Teams that need advanced CRM integrations or enforced admin controls land on Advanced, at $15 per user per month billed annually ($30 billed monthly). Others can start on Core.

Compliance claims, and the plan each one lives on

SOC 2 Type II is ticked on all three plans in Krisp's comparison matrix, and Krisp says an independent firm audits it every year. Reading the report is another matter: the matrix lists SOC 2 report access on Enterprise only, and Krisp's security page places the report in its Trust Center. GDPR is marked on every plan, with Standard Contractual Clauses for transfers and a data processing agreement on request. Krisp also says it holds PCI DSS certification, and card numbers are handled by Stripe.

Health data needs one precise sentence. Krisp says it complies with HIPAA; its pricing matrix lists HIPAA compliance on Enterprise only, and BAA signing is available for teams of 100 or more seats.^[1] A smaller practice should raise that with sales before anyone signs. Krisp's HIPAA notice adds that it does not scan meeting content for ePHI, so what staff say on a recorded call remains your governance question.

The audio layer and the notes layer handle data differently. Noise cancellation always runs locally, and Krisp says that audio is neither sent to nor stored on its servers. Meeting content reaches Krisp's cloud once you use notes, recording, the mobile app or an integration, where recordings are encrypted in transit and at rest (AES-256) and stored in the United States by default. Summaries and AI Chat run on Anthropic Claude through AWS Bedrock. Krisp says your meeting data is never used to train its AI models (pricing FAQ, November 2026).

• Decide whether your security review needs the SOC 2 report in hand; on Meeting AI, report access is an Enterprise item.
• Compare your seat count with the 100-seat BAA condition before promising anyone health-data coverage.
• If recordings must stay on laptops or in a chosen region, budget for Enterprise: on-device private transcription and data center choice are listed there.
• Read the subprocessor list in Krisp's Trust Center.

Consent duties, recap emails and outside viewers

Krisp records without a bot by default, capturing audio through Krisp Microphone and Krisp Speaker on your own computer. Other participants may see nothing at all. Under Krisp's Terms, the customer is responsible for guests' consent and for recording laws, and a customer who cannot obtain consent should not use the record or transcribe features. Krisp can notify participants, but some platforms block those chat messages or audio prompts. Tell people yourself. Our Krisp AI Note Taker guide covers the capture modes in detail.

The optional Krisp Bot is more visible: it joins Zoom, Google Meet or Microsoft Teams as a separate participant, and the host has to admit it. One detail surprises teams. Adding assistant@krisp.ai to a calendar invite makes the bot join automatically, even when you are absent. After a meeting, Krisp may email recaps. With a calendar connected, Auto-Share can reach all invitees including external guests, your whole work domain, team invitees only, or nobody until you send it by hand; the admin default is User choice.

• Write a consent script for client and candidate calls.
• Pick the Auto-Share option before the first external call; on Advanced, admins can disable auto share for the whole team.
• Remember that copying a note creates a public link until you unshare it.
• Warn staff who sign up with a work email: if your company already has a Krisp account, Krisp may add them to that workspace.

Plan gates to check line by line

The step from Core to Advanced is $7 per user per month billed annually, or $84 per user a year by our arithmetic; billed monthly, the step is $14 per user per month. For a ten-person team billed annually, Core comes to $960 a year ($96 per user a year) and Advanced to $1,800 ($180 per user a year), by our arithmetic. That gap buys the two advanced CRM integrations, the admin controls, commenting, a team-level webhook and six times the storage. The full plan math sits in our Krisp pricing breakdown.

Core's integration list is wider than many buyers expect: Slack, Notion, Zapier, the Microsoft Teams integration, MCP, the public API and personal webhooks all start there. Identity management does not. On Meeting AI, SSO and SCIM are Enterprise only, so a company that provisions every app through an identity provider should open that conversation first. Enterprise has custom pricing through Krisp's sales team, and above 50 members Krisp offers volume discounts without publishing a percentage.

• List every CRM your team writes notes into. Salesforce means Advanced.
• If IT requires SSO or SCIM for every tool, price Enterprise first.

Seats, storage and what removing a user deletes

Every teammate you add is a paid seat, and team size has no cap. If no empty seat is left, sending an invitation charges the team's card immediately, prorated to the next billing date; Krisp's Terms note that users who invite people can create fees for the account owner, and that this invitation ability can be switched off in account settings. Removing seats is slower. Only unassigned seats can go, the change takes effect next cycle, and removed seats are not refunded.

Storage is per user and is not pooled: 10 GB per seat on Core and 60 GB per seat on Advanced.^[2] Users see a warning above 80%, and above 100% new recordings cannot be saved until an admin buys more. Deleted meetings sit in Trash for 30 days and still count. Krisp does not publish storage add-on prices, and those payments are non-refundable. Someone who records every call hits the ceiling long before a colleague who only transcribes.

The offboarding rule is blunt. Removing a user from the team permanently deletes all of that user's data, including recordings.^[3] A departing account manager's client calls vanish with the account unless someone moves them first. Krisp's HIPAA notice adds that on a corporate subscription, a deactivated account may lose access to recordings tied to the corporate email. Recordings download as MP3, and transcripts export as text files with timestamps and speakers.

• Download or share a leaver's meetings before removing the user. No exceptions.
• Decide who may invite people, or switch off other users' ability to invite.
• Check storage for your heaviest recorders, not the team average.

Renewal, cancellation and the refund rule

Krisp offers a 7-day free trial of its paid features with no credit card, but no free Meeting AI plan; under its Terms, access ends when the trial expires, with 90 days to export content (is Krisp free has the details). Paid subscriptions renew automatically unless canceled before the renewal date. Fees are non-refundable except as the Terms state,^[4] and that exception is narrow: a customer ending the contract for an uncured material breach gets prepaid fees back for the rest of the term.

Canceling happens on the Billing page and is not immediate. Paid features stay until the end of the current cycle. A yearly plan cannot be switched to monthly from the account, so you cancel and resubscribe monthly once the cycle ends. Monthly billing beats a year billed annually only if you stop within 5 months: on Core, $80 per user for five months billed monthly, against $96 per user for a year billed annually, by our arithmetic. On Trustpilot, reviewers most often complain about canceling and support. Plan accordingly.

• Put the renewal date in a shared calendar.
• Keep the billing card current: failed payments are retried on days 3, 10 and 19, then the subscription is canceled.
• Send legal the liability clause, capped at fees paid or payable in the prior 12 months.

Platforms, installs and audio settings

The Meeting AI desktop app runs on Mac and Windows only; Krisp does not support Linux or Chrome OS. Krisp recommends macOS 14 Sonoma or later, or 64-bit Windows 10 or 11, with at least 8 GB of RAM. Installing requires admin rights on Windows, and IT can push it with an MSI installer on Windows or a PKG through Terminal on Mac. Citrix, VMware Horizon and AWS Workspace desktops are supported. Chromebook clients are not.

Noise cancellation works only when Krisp Microphone and Krisp Speaker are selected in the calling app, and Krisp Speaker cannot be used in Firefox or Safari. Krisp's noise cancellation for calls and meetings runs in the desktop app for Mac and Windows; the mobile apps are for recording, notes and transcription. Transcripts and summaries come in 16 languages (Krisp's pricing page says 16+). Firewalls need outbound TCP port 443 open and *.krisp.ai allowed.

• Inventory every machine. Linux users are out.
• Have each user select the Krisp devices in Zoom, Teams or Meet.
• Confirm your meeting languages are among the 16.

The bottom line

Krisp clears a security review more easily than its price suggests, as long as the review asks the plan question. SOC 2 Type II, GDPR, encryption and local noise cancellation come with every plan, while the SOC 2 report, SSO, SCIM and data residency choices belong to Enterprise. Krisp says it complies with HIPAA; its pricing matrix lists HIPAA compliance on Enterprise only, and BAA signing is available for teams of 100 or more seats. Below that line, the decisions are practical: Advanced for gated integrations or admin controls, a written consent routine, and an offboarding step that saves recordings first.