A "SOC2 compliant" AI meeting-notetaker sat on an unpatched cross-tenant data leak for six months

A meeting-notetaker called tl, dv left a Firestore database wide open for six months. Any authenticated user could query every meeting on the platform. That means 181,874 meetings, 84,312 users, and 35,003 domains, including government sessions from 23 countries, sitting there for the taking.

The bug was a missing security rule, the kind of mistake that should get caught in code review. It was reported on January 28, 2026. The CTO never replied substantively through six months of follow-up, even though the company’s marketing site advertises SOC2 and GDPR compliance. The original report walks through the technical detail, but the business lesson is simpler: compliance badges do not equal actual security discipline.

Why this matters to you

You are buying AI tools that touch customer data, employee conversations, and proprietary strategy. Vendor security pages are easy to fake. What matters is whether the engineering team enforces tenant isolation at the database level, before every read and write. This is not abstract. If your meeting notes leak because a third-party tool skipped a Firestore rule, your customers do not care that you were SOC2 compliant on paper.

The tl, dv case is a concrete proof point for why tripwire discipline matters. When we build tools like Omni-Mail into an AI command centre, we enforce tenant checks before every mutation, not because it is hard but because skipping it once is enough. The gap between a security page and actual security practice is where breaches live. Ask vendors how they enforce isolation, not whether they have a badge. If they cannot answer in one sentence, walk.