ShareLeakAudit

Who it's for

IT/ops admin at 20-200 person companies using meeting-recording bots (tl;dv, Fireflies, Grain, Fathom); today they trust vendor defaults or spot-check a handful of recordings manually and never re-check as new meetings pile up.

The problem

legal exposure — a client contract call or HR discussion set to public-link sharing becomes discoverable/enumerable (as the tl;dv breach showed), and no one currently has time to re-audit sharing settings on every new recording across every tool.

How to build it

web dashboard; OAuth connect to admin accounts of tl;dv, Fireflies, and Grain (v1 covers these 3); scans all recordings nightly, lists any with public/anyone-with-link sharing, direct link to fix each one, weekly email digest of new exposures.

How it makes money

companies pay $99-249/month per workspace because a single leaked client or HR recording risks contract breach or GDPR fines that dwarf the subscription, and free/manual checking doesn't scale or run continuously across every new recording.

Why it doesn't exist yet

incumbent meeting-recording vendors have no incentive to publicly surface their own sharing misconfigurations (it's an admission of risk), and enterprise SaaS-security posture tools (Nudge, DoControl) treat this as a low-priority line item buried in a much bigger, pricier platform indie teams can't justify buying just for this.

First users

post in the same HN/security threads reacting to the tl;dv exposure story, offer a free one-time scan that shows a company how many of their recordings are currently public — the shock number drives signups.

Build size

2 people x 10 weeks — includes OAuth integration + nightly scan + dashboard + weekly email for 3 vendors; excludes building recording/transcription functionality itself and excludes covering video-conferencing platforms directly (Zoom/Meet native recordings).

Biggest risk

if tl;dv, Fireflies, or Grain ship a built-in 'exposed recordings' admin alert in reaction to this week's breach news, the standalone audit layer becomes redundant for those vendors.

Conditions for a hit (all 3 required)

• dashboard lists every recording with 'anyone with the link' or public sharing across connected tl;dv/Fireflies/Grain accounts
• weekly email digest states the count of newly-exposed recordings since the last scan
• one-click action sends a pre-filled lockdown request email to the tool admin to switch sharing to workspace-only

How it's judged (in 6 months)

Product Hunt daily top 5 launch, or the product's own site publicly listing 20+ paying customer logos/testimonials(judgment date 2027-02-11)

AI self-confidence 38/100 — self-reported likelihood of meeting the criterion, not a business success rate