Fireflies.ai Buyer's Checklist: Security, Privacy and HIPAA

Fireflies.ai carries SOC 2 Type II and GDPR coverage on every plan, and its Terms say customer content will not be used to train generative AI models. The risk sits in the defaults. Right after sign-up, a visible bot auto-joins every calendar meeting with a video link, recap emails go to everyone on the invite, and recaps open for anyone holding the link. HIPAA is the hard gate: it exists only on Enterprise, at $39 per seat per month billed annually only, with Private Storage on and a signed BAA. Fix three settings on day one. The checks below then decide which plan your team actually needs.

Consent and the visible bot

The Fireflies.ai Notetaker (invite address fred@fireflies.ai) joins calls as a named participant and cannot be hidden. When it arrives, it posts a chat message linking to the privacy policy. On Zoom, if the host is not a Fireflies user, Zoom itself asks the host to allow recording and plays its own announcement. None of that moves the legal duty. Under the Terms, getting every participant's consent is your responsibility, and capturing without the bot does not change that duty.^[1]

• Change auto-join from the default (all meetings with a web-conferencing link) to meetings you own, meetings with teammates, or invite-only (on a Free account created from September 2026, invite-only leaves only a few transcription credits, within 400 minutes of storage per team).
• Decide on the compliance email: it goes out an hour before the meeting with an opt-out link, it is off by default, and an opt-out keeps the bot away.
• Set a team auto-record policy as admin; by default each teammate chooses.
• Cancelling a paid plan does not stop the bot; the account drops to Free and keeps auto-joining.

Calendar access is the stubborn part. The only way to revoke it completely is to delete the Fireflies account. Short of that, you change the auto-record setting and remove any Recording rules, because those rules override join settings. The steps for each meeting platform, including pulling the bot out of a live call, are in our guide on how to remove Fireflies.ai.

Who can open a recap

Sharing is the default most buyers miss. Every recap starts at Teammates & Anyone with Link, so a forwarded email opens the meeting for whoever receives it.^[2] Separately, the recap email goes to everyone on the calendar invite. Switching that email to Only me changes who gets the message, not who can open the meeting. Sharing with people outside the workspace costs no seat and no credits. That makes wide sharing cheap and easy, which is exactly why it needs a rule.

• Set meeting privacy to Teammates, Participants or Only Owner for people who handle sensitive calls.
• Check external sharing gates: public meeting access and password-protected links with expiry both start on Business.
• On Enterprise, use the Rules Engine to auto-share, set privacy and auto-delete by rule.
• Know that an Enterprise Super Admin, under a signed side letter, can see every meeting, private ones included.

Training, retention and deletion

The Terms say Fireflies will not use customer content to train, retrain, fine-tune or improve generative AI models, and the Privacy Policy adds that vendors are contractually barred from training on it. Two clauses deserve a lawyer's eye. The Terms let Fireflies derive usage and statistical data to improve its services, and the DPA allows deidentified data to improve products. Fireflies keeps zero data retention terms with its AI vendors, OpenAI and Anthropic among them. That protection ends once the MCP server hands meetings to an outside AI tool.

Deleting a meeting is immediate and permanent and returns its storage minutes; only the owner can do it, and bulk delete starts on Pro. Closing the account deactivates it at once and erases the data after a 30-day grace period, during which support can still recover it. The Terms do keep archival, backup and legal copies. Custom retention windows are an Enterprise feature that requires Private Storage, and Enterprise recording modes can discard the audio or transcript after processing.

• Have legal read the usage-data and deidentified-data clauses, not only the training sentence.
• Decide whether staff may connect Fireflies to outside AI tools through MCP.
• Name a backup admin: if the team admin leaves, the account drops to Free.

Certifications, HIPAA and FERPA

SOC 2 Type II and GDPR appear on every plan in the pricing matrix, and the SOC 2 report is available after you sign an NDA. Fireflies says it holds ISO/IEC 42001 certification. The DPA can be signed online, with Fireflies acting as processor for business customers. By default, data is stored and processed in the United States on AWS and GCP, encrypted with AES-256 at rest and TLS 1.2 or newer in transit. The subprocessor list is published at trust.fireflies.ai/subprocessors.

Product pages show HIPAA badges, but the condition is narrow. HIPAA applies only on Enterprise, with Private Storage enabled and a signed BAA, arranged on request.^[3] FERPA follows the same pattern with a Data Sharing Agreement. Private Storage keeps data in a region you choose or in your own AWS S3 or Google Cloud Storage bucket, yet processing still happens in the US. It applies to meetings recorded after it is switched on. A downgrade or storage change switches HIPAA off immediately. Clinical workflows are covered in Fireflies.ai for healthcare.

• Keep protected health information out of Free, Pro and Business; the Terms forbid it without a BAA.
• Get the meeting platform's own BAA too, for example Zoom or Google Meet.
• Keep Fireflies Talk dictation away from health data. No BAA covers it.
• If your storage standard is Azure, stop here: bring-your-own storage supports S3 and Google Cloud Storage only.

Admin controls, SSO and SCIM

Controls arrive in steps. Business adds User Groups with their own settings, Integration Rules that filter which meetings sync to other apps, and granular integration permissions. Enterprise adds SAML SSO (Okta, Azure AD / Entra, Google Workspace, OneLogin, JumpCloud), SCIM 2.0 once SSO is set up, the Rules Engine, the Super Admin role and an audit logs API in beta. Fireflies does not publish a built-in two-factor login; sign-in runs through Google, Microsoft or SSO. It does not publish an uptime SLA either. Ask about both.

The jump from Business to Enterprise is $20 per seat per month on annual billing, or $240 a seat a year by our arithmetic. For ten seats, that is $2,280 a year on Business billed annually against $4,680 a year on Enterprise. If your security review demands SSO or SCIM, only Enterprise passes it, at any team size. The premium is then the price of entry, not an upgrade to weigh. Without that demand, Business already covers user groups, sync rules and external-link controls.

• Turn on automatic adding of domain users only on purpose; each added seat is billed, prorated.
• Restrict who can create AI Skills and who can upload files.

Storage, credits and billing terms

Storage never resets. At the limit, new meetings are still captured, but you must delete older ones to open the new ones. Pro's 8,000 minutes come to about 133 hours per seat, so someone recording five hours a week fills that share in roughly six months. Pro costs $10 per seat per month billed annually or $18 per seat per month billed monthly; Business costs $19 per seat per month billed annually or $29 per seat per month billed monthly.^[4] The full plan math is in our Fireflies.ai pricing breakdown.

AskFred, AI Skills and the Personal Assistant draw on AI credits, a one-time allotment shared by the team: 20 on Pro, 30 on Business, 50 on Enterprise. When credits run out on a paid plan, an account without a credit subscription is subscribed to the lowest tier, $5 a month for 50 credits (a team pool), and one that already has a subscription moves up to the next tier. Auto-Upgrade can be switched off in billing settings. Credits are non-refundable, and a downgrade becomes account credit.

• The trial is 7 days of Business, needs a credit or debit card and bills automatically on day 7; one trial per account.
• Cancel at least 24 hours before a billing period ends to avoid the next charge.
• The Terms send disputes to individual arbitration under Delaware law; opt out by email within 30 days of first use.

The bottom line

Fireflies.ai passes a typical small-business security review once someone owns the configuration. The paperwork is solid: SOC 2 Type II, GDPR, a signable DPA and a clear no-training clause. The defaults are not. Auto-join, invite-wide recap emails and open-link sharing all favor reach over control, so reset them before the first external call. Regulated data changes the answer. Healthcare and education teams need Enterprise with Private Storage and a signed agreement; below that plan, keep protected data out.