AI notetaker tl;dv left 181,874 meeting recordings open to any logged-in user for 188 days

An AI meeting notetaker held 181,874 recordings behind one missing database rule, and the rule stayed missing for 188 days after the company was told.

The finding

Security researcher bobdahacker found that tl;dv, a popular AI note-taking and transcription app for Zoom, Google Meet and Microsoft Teams, had no tenant isolation in its Firestore database. In practice, any authenticated user could query the full archive rather than only their own meetings: 181,874 recordings across 84,312 users and 35,003 domains, including government agencies in 23 countries. About 1,000 meetings were still live and joinable at the time of testing, meaning an outsider could have dropped into calls in progress.

The timeline

The vulnerability was reported to tl;dv on January 28, 2026. The company acknowledged the report. When bobdahacker went public on August 4, 2026, the flaw was still open. That is 188 days between the company knowing and everyone knowing, and the disclosure came from the researcher rather than from a fix.

Why it matters beyond tl;dv

Every AI meeting assistant that records, transcribes or summarizes calls holds the same class of data: conversations the participants assumed were private. The security of that archive frequently rests on a single access-control rule in a multi-tenant database, the rule that says a user may read only their own organization’s records. When that rule is absent, nothing is hacked in the usual sense. The door is open by design, and the only requirement for walking through it is an account anyone can create.

The presence of government agencies from 23 countries in the exposed set shows how far these tools have spread into sensitive settings. It also shows the asymmetry of the risk: the user who installs a notetaker for convenience is rarely the one who can audit the vendor’s database rules.

For companies using an AI meeting recorder, the useful questions are the ones this case raises directly: whether the vendor enforces tenant isolation at the database level, how it handles vulnerability reports, and how long it has taken to fix reported issues in the past. tl;dv’s 188-day window is the benchmark to measure against, in the wrong direction.