Your AI builder optimised for one thing: the demo works. It did not optimise for safe. Here are the three holes I find in almost every AI-built Firebase app β what they are, how they're exploited, and the fix. The full list of twelve, with rules archetypes, a launch checklist and a self-audit, is in a packet I put together (link at the end). These three are free, right here.
1. Open rules: allow read, write: if true
The scaffold's rules grant the world full access. Test-mode rules ( request.time < timestamp.date(...) ) are the same hole with a 30-day fuse.
Firebase config is public by design. A scanner pastes it into a script, lists every collection, and downloads or deletes everything. Automated scanners find new open databases within days of them going live.
The fix: deploy a real rules archetype for your app type today. If you can't map your app yet, deploy a deny-all starter and migrate collection by collection. Then verify with a launch checklist β don't just eyeball it.
2.β¦