Three ready-made introductions — copy, paste, done. No bot joins your calls, recipients don't install anything.
For your team
Hey team — I've started using Fly in our meetings. It's a "fly on the wall": it listens along (with everyone's knowledge — you'll see a notice at the start) and hands us a recap the moment we finish: the decisions we took, who does what, and a sharp summary.
Nothing changes for you: no bot joins the call, you don't install anything. You can see exactly what it captures and how to correct or remove anything attributed to you here: [APP-URL]/participants.html
Want to see what the output looks like? Example recap: [APP-URL] → "See an example recap".
For your manager
Proposal: try Fly for our meetings
The problem — decisions and action items evaporate. We re-discuss the same things, follow-ups slip, and writing minutes costs someone 30+ minutes per meeting.
What Fly does — it transcribes the meeting live (with a visible consent notice for the room) and produces an immediate recap: explicit decisions, a capped action list with owners and deadlines, and a one-paragraph summary. Recaps can be shared as a clean client-ready report or kept internal. Everything is also grouped per project, so we get a running dossier per client.
Costs — currently a free beta; a pricing model will follow. No contracts or seats today.
Risks & mitigations — no audio is stored (live transcription only), participants get a public page explaining what's captured, with a correction/removal form; recordings pause with one tap (off the record); data can be exported or fully deleted by us at any time. Details: [APP-URL]/participants.html
Ask — green light to pilot it in our weekly meeting for 4 weeks, then decide.
For IT / security
Fly — standard security questions, short answers
• What is it? A web app (PWA) that live-transcribes meetings and generates structured recaps. No bot joins calls; capture happens on the host's device.
• Where does data live? Text transcripts and recaps in Supabase (per-account, RLS-protected). No audio is stored anywhere — audio is streamed for live transcription and discarded.
• Which processors? Browser speech service (Google/Apple — only on that route), Deepgram (speech-to-text), Anthropic (summarisation; API data not used for training), Supabase (storage), Cloudflare (API proxy with model allowlist, token caps and rate limiting). Full table: [APP-URL]/participants.html
• Retention & deletion? User-configurable auto-delete (30/90/365 days), one-click full export, and a "delete everything" that wipes cloud rows and local storage. Participants can request correction/removal via a public form (rate-limited).
• API keys? Never in the client. A Cloudflare Worker proxies all AI calls (8 req/min, 300/day per IP).
• Shared recap links? Optional, unguessable UUID tokens, read-only via a security-definer function (no listing possible), revocable at any time by the owner.