Trust, shown live: how Fireflies handles your privacy and data

Some context for why this session matters. In August 2026, the cybersecurity publication Cybernews launched its AI Trustworthiness Ranking, scoring 500 AI companies across security, data privacy, organizational transparency, and public perception. Fireflies.ai ranked third overall, alongside names like Google and Salesforce, and was the highest-ranked among AI meeting assistants.

What makes that placement meaningful is the backdrop. Across the 500 companies studied, Cybernews found that security was the weakest area by far and that most companies don't clearly tell you what happens to your data. Nearly two-thirds don't disclose whether they train their models on user data, and about the same share doesn't say how long they keep it. Fireflies is built the other way around: you're told when recording happens, your data isn't used to train AI models, and you decide who sees what and for how long.

So this webinar was about showing that in practice. We walked through exactly what happens to your data at every step, and how to control it. Here's what we covered and where to go deeper.

Here's what we covered and where to go deeper.

You control when the notetaker joins (7:30)

Recording isn't all-or-nothing. As an admin, you can auto-join based on keywords or domains, go fully manual, or set recording rules that decide exactly which meetings get captured. And restriction rules sit above everything: if a meeting matches a restriction, the notetaker stays out, even if another rule would have joined it. That's how internal, legal, and HR meetings stay private automatically.

Everyone knows when recording is on (14:00)

Fireflies is built to make recording visible, not hidden. Participants get a compliance notification by email before the meeting, an in-meeting notice when the notetaker joins, and a watermark on camera during the call. You can also capture without a bot in the meeting using the Desktop App, while still notifying everyone that recording is happening.

Decide who sees what after the meeting (18:30)

After a call, you control access and visibility down to the person. Choose who can open a meeting, from your whole team to only you, set who receives the recap email, and turn off public sharing across your whole workspace. You can also skip video capture entirely and set meetings to auto-delete on a schedule you choose.

Granular control with the Rules Engine (21:30)

For enterprise teams, the Rules Engine takes this further. Set privacy by meeting title, participant, or user group. So whenever someone from legal joins, the meeting locks to owner-only. Auto-delete after 30 days, auto-share to the right team, and route recaps where they belong, all without touching a thing after the call.

Where your data lives (25:00)

By default your data sits in encrypted US cloud infrastructure. Teams with residency requirements can choose EU storage, and enterprise teams can go further with private, isolated storage, including bringing their own storage on AWS or Google Cloud. Your bucket, your keys.

On the fundamentals: Fireflies is SOC 2 Type II certified, your data is encrypted, and it is never used to train AI models. Fireflies is also HIPAA-ready with a BAA on enterprise. For the full picture, our Trust Center lays out our certifications and exactly what happens to your data, and you can even ask AskFred about any of it.

Over to you: What's the trickiest privacy or recording rule you're trying to set up? If you've been there, you know the feeling:

❌ A notetaker joining a meeting it should never have been in
❌ Sensitive calls visible to people who shouldn't see them
❌ No clean way to keep legal or HR meetings private automatically
❌ Compliance or data residency requirements you're not sure Fireflies can meet

👇 Drop the rule or setting you're trying to get right. Be specific. What kind of meeting, who should and shouldn't have access, and what's the requirement? We'll point you to the exact setting, rule, or Trust Center resource to sort it out.

Keep the conversation going: still have a question about consent, data residency, retention, or permissions? Drop it in the comments here or in #Ask the Community, and we'll help you get your setup locked down.