Launching Aug 2 - the day the AI Act transparency rules start applying

Quick note ahead of our launch next week.

VibeCodersLegal started as a service: I audit vibe-coded products for the gaps regulators actually fine for, then fix them. The free scanner we're launching came out of doing that manually about forty times and realising the first ten minutes were identical every single time.

What it does: paste a URL, about 10 seconds, and you see what an EU regulator would flag on your public page -- trackers firing before consent, whether a consent layer exists at all, privacy policy alive or dead, terms alive or a footer link pointing at nothing.

What it deliberately doesn't do: it won't read your policy and declare you "compliant." It can't see inner pages, anything behind auth, or what your backend does with data. It's a surface scan, labelled as one.

The first version I sketched would have generated scary-looking findings from a randomiser. It would have converted better. It would also have made me exactly the thing I audit people for, so it didn't ship.

Launching on August 2 because that's when the AI Act's transparency rules start applying, and shipping a compliance tool on any other day felt like a lie.

If you're building on Lovable, Bolt, v0 or Cursor -- what's the compliance question you've been putting off? The ones people ask most are what I build the next checks around.