Fireflies.ai Review: Consent, Notes, and Plan Limits

Fireflies is easiest to judge when the review starts before the meeting, not after a polished summary appears. The first questions are whether the conversation may be recorded, what participants will see, what the workspace will retain, and who will check the resulting notes. Transcription quality matters, but it sits inside that larger process.

This is a documentation-based review of the Fireflies meeting product, checked against current Fireflies product, pricing, security, and help pages on July 17, 2026. HUMAI did not create an account, record a call, upload audio, measure transcription accuracy, compare speakers, or calculate time saved. The five-meeting protocol below is a proposed test that preserves evidence; it is not a completed benchmark.

Fireflies is a plausible candidate for a team that has repeatable meetings, a clear recording policy, and a real use for searchable transcripts or structured follow-up. It is a poor fit when participants cannot be informed, sensitive conversations cannot enter a third-party system, or nobody will verify decisions and action items before they leave the meeting record.

Before the meeting: decide whether capture is allowed

A recording workflow starts with people, purpose, and permission. Fireflies documents both opt-in and opt-out behavior across meeting platforms, plus advance email notices, meeting-chat notices, pause commands, and removal controls in its recording consent guide. Those controls can make capture visible. They do not decide which law, employment rule, client contract, or internal policy applies to a particular call.

The host or workspace owner still needs an approved process. State what will be captured, why it is needed, where it will be stored, who can open it, and how long it will remain. Record the consent step outside the transcript so that a failed join or deleted recording does not erase the evidence that participants were informed. If one participant declines, the workflow needs a non-recorded route rather than a debate inside the call.

Some meetings should be excluded before Fireflies is invited. Legal advice, medical information, employee investigations, credentials, unreleased financial data, customer secrets, and conversations covered by a stricter agreement need the relevant owner to approve the exact setup. A generic security badge is not permission to record them.

Configuration belongs here too. Fireflies' settings guide shows controls for automatic recording, meeting privacy, retention, and recording format. Review those defaults with the calendar connection before the first eligible event. An automatic join rule can otherwise turn a one-time experiment into a workspace-wide habit.

Choose how the conversation enters Fireflies

The familiar route is the Fireflies notetaker joining as a meeting participant. The current invitation guide documents calendar invitations, automatic joins, and adding the notetaker to a live meeting. Fireflies lists Google Meet, Zoom, Microsoft Teams, Webex, and several other services in its supported conferencing guide. Platform support should be confirmed for the exact account and meeting type, not inferred from a logo on an integrations page.

A visible bot is not the only route. Fireflies documents a Chrome extension for Google Meet that can capture without adding the notetaker as a participant. Its current desktop app guide describes system-audio capture across browsers and calling applications. Bot-free capture may reduce meeting clutter, but it also removes an obvious visual cue. Disclosure becomes more important, not less.

An existing authorized recording can also be uploaded. Fireflies' upload guide lists supported audio and video formats, per-file limits, and the outputs created after processing. Uploading does not create permission that was missing when the file was recorded. The uploader should be able to show both the right to use the recording and the reason it belongs in this workspace.

Pick one capture route for the first test and write it in the test log. A bot, browser extension, desktop capture, and uploaded file can produce different failure points. Mixing them without labels makes it impossible to tell whether a problem came from the conversation, the platform, the capture route, or the generated output.

During capture: keep the meeting recoverable

For an evaluation meeting, use an agenda with named speakers, two or three planned decisions, and action items that include an owner and due date. This is not stagecraft for the product. It creates a reference against which the transcript and recap can be checked later.

Keep a human note of decisions even while Fireflies is running. If a participant asks to pause, changes the scope, or shares information that should not be retained, use the documented pause or removal control and note the time. Do not assume that a generated summary will preserve the boundary correctly.

Audio conditions belong in the record. Note the meeting platform, microphones, remote connections, overlap, and any interruption. A transcript error without that context says little about the next meeting. It also should not be converted into a broad claim about a person's accent, a language, or the product's universal accuracy.

After the meeting: separate the outputs

Fireflies presents several artifacts after processing. The transcript is a text representation of the conversation. The summary condenses it. Action items turn selected statements into tasks. AskFred can answer questions about a processed meeting and generate follow-up material from that context. These outputs are related, but a correct sentence in one does not validate the others.

Review the transcript against the approved recording or reference notes. Then check every decision in the summary against a timestamp. Finally, compare each action item with the spoken task, owner, and date. Mark missing items, unsupported additions, wrong owners, and wording that changes a commitment. A follow-up email should be drafted only after that correction pass.

The distinction matters because a neat recap can hide a weak transcript, while a rough transcript may still preserve the exact sentence needed to settle a decision. AskFred is another generated layer, not an independent witness. Its answer should point the reviewer back to the underlying meeting material.

Retaining evidence requires the right plan and authorization. Fireflies' current download guide says transcript, summary, audio, and video downloads are available on Pro and higher plans. If the evaluation cannot export its raw and corrected artifacts, it should not publish a numerical accuracy or productivity claim from memory.

Storage is part of the product decision

Fireflies' storage and transfer guide says the service collects meeting content and metadata and uses US cloud infrastructure by default, with private storage options described for Enterprise. The same guide describes encryption, ownership, and data-transfer practices. These are vendor statements and must be evaluated against the contract and settings available to the actual workspace.

Fireflies also states in its information safety policy that meeting content is not used to train its models and that third-party AI vendors operate under zero-retention terms. That does not mean the Fireflies workspace stores nothing. Recordings, transcripts, summaries, and metadata can remain in the product according to the selected mode, plan, privacy setting, and retention rule.

Current Enterprise documentation describes four recording formats: retaining audio, transcript, and summary; deleting audio after transcription; retaining only a summary; or retaining audio and summary without a transcript. Fireflies labels these as compliance-oriented controls. A team still has to decide whether the chosen format satisfies its obligations and whether a generated summary itself contains sensitive information.

Deletion should be tested rather than assumed. Fireflies documents an Enterprise-only automatic deletion setting with periods from one week to one year. The guide says a new setting applies only to future meetings, not past meetings. Confirm who can change it, what it removes, whether exports and connected systems create other copies, and how participant deletion requests will be handled. A short retention setting cannot remove a transcript already pushed into a CRM or downloaded to a laptop.

Plan boundaries checked July 17, 2026

Fireflies' pricing article dated July 10, 2026 and its live pricing page list the following price and storage baseline. Prices are per seat and may change by billing channel, account, promotion, tax, or contract. Storage is not the same as transcription allowance, and AI features may also use credits.

Both pricing sources describe Free storage as 400 minutes per team. Fireflies' current storage guide instead labels the allowance as 400 minutes per user and says Free and Pro allocations are pooled across the team. Its Free-plan guide calls the same allowance 400 minutes per seat. Confirm the counter in the actual workspace or checkout before deciding how many meetings the plan can retain.

The same documentation split affects AI Skills. The July pricing article lists them as unavailable on Free. The Free-plan guide says each seat receives 20 one-time AI credits and that AI Skills can run while credits remain. The current AskFred guide says Free users receive 20 credits at signup, shared across AskFred and other AI features, and that AI Skills consume credits dynamically. Treat this as limited trial access, not a recurring automation allowance, and confirm the live account before building a workflow around it.

The pricing article and live page say all four plans include unlimited transcription and AI summaries, while storage, exports, automation, analytics, and controls separate the tiers. Confirm the checkout before purchase. A permanent review should date these values instead of presenting them as product constants.

Free is enough to inspect the interface and basic output. Pro is the practical lower boundary for a retained-artifact test because downloads are part of the protocol. Business and Enterprise should be justified by a team requirement such as shared analytics, governance, retention format, or storage, not by the assumption that a higher plan makes every transcript more accurate.

A five-meeting trial that can support a real conclusion

Use five authorized, low-risk meetings. Define the acceptance rule before the first capture. Keep the original agenda, consent record, capture settings, approved source recording or reference notes, raw Fireflies outputs, corrected outputs, and correction log under one meeting ID. Remove or mask names and confidential details before the material enters an editorial archive.

1. Controlled two-person planning call: include five known names or project terms, two decisions, and two action items. This establishes the simplest case.
2. Four-person status handoff: require speaker changes, one reassigned task, and dates stated in two different formats. This tests attribution and task ownership.
3. Technical walkthrough: use approved fictional product names, version numbers, and a short sequence of steps. This exposes whether exact terms survive the transcript and summary.
4. Ordinary remote friction: include one interruption, a brief overlap, and one participant joining from a weaker connection. Record the conditions instead of blaming an unexplained error.
5. Uploaded recording: process an authorized file with the same agenda structure. This separates upload behavior from live meeting capture.

For each meeting, count speaker-label errors, material transcript substitutions, missing decisions, invented decisions, missing action items, wrong owners, and wrong dates. Record correction minutes from first opening the output to approval of the final note. Also record capture failures, processing failures, and any consent or access-control issue. Report the numerator and denominator for every rate so that five meetings do not become an impressive but meaningless percentage.

Do not combine all defects into one star rating. A legal team may care most about retention and access. A project team may care about decision traceability. A sales team may need a CRM field to preserve the customer's exact commitment. The test should rank the errors by the consequence they create in the intended workflow.

The decision is made before the notetaker joins

Fireflies can be evaluated without pretending that HUMAI used it. The documented product can capture meetings through several routes, produce searchable and generated artifacts, and apply different storage and plan controls. Whether that system deserves a place in a team depends on evidence the vendor cannot supply for the buyer: participant acceptance, policy fit, correction effort, and the cost of a wrong decision or task.

Start with the meeting policy. Then run the five-meeting protocol on material that is safe to retain. Keep Fireflies only if the corrected artifacts support the intended handoff and the storage boundary survives review. If the team cannot complete those steps, an automatic transcript is not the missing piece.