24,664 apps answered without a login
Welcome back to Zero to MVP Weekly. One signal, one tool, one MVP idea — five minutes, every Saturday. This week's test takes less time than reading this issue: open your app in a private window, don't log in, and look at what the database sends you. For more than 24,000 apps, the answer was real records.
1. The signal of the week
Your app may be answering strangers.
Crissy Field, a security firm from Hamburg, crawled Lovable apps that keep their data in Supabase. 24,664 of 34,545 sent database records to a visitor who wasn't even logged in. Among them: a forum with more than 200,000 private chat messages and more than 1,000 records with passport details.
Nobody hacked anything. In apps like these, the browser talks to the database directly, and only the access rules on each table protect the data. In many apps those rules let anyone read.
What to do with it: open your app in a private window without logging in, and check in DevTools what the database sends back. Then make sure every table with user data has row-level security on, with a read rule that checks the user.
One honest caveat: this isn't only a Lovable problem. A hand-written Supabase or Firebase app can make the same mistake.
2. My take
In my view, this is one of the main problems with vibe coding. AI lets people with no experience build full-fledged apps, but it doesn't make them secure. An app can work perfectly and look professional while exposing personal data at the same time. AI has lowered the barrier to building software, but it has raised the bar for security.
That said, those 24,664 apps aren't necessarily vulnerable: some of the data may be public on purpose. But the real leaks of the past few months are worrying. A DevTools check isn't enough: you need to test the API thoroughly, including what one user can see of another user's data. AI may write the code, but security is still the developer's responsibility.
3. Tool of the week
An always-on local server: one model per task.
- The setup: A modular mini PC that also works as my network storage, with my own RTX 4060 Ti 16 GB in its GPU dock. It uses 40 W at idle, a third of my desktop, so it runs around the clock. Models load on request: most in a few seconds, the 125B one in about a minute and a half.
- What runs on it: LightOnOCR 3 (4B) reads documents and screenshots at about 10 seconds a page. Gemma 4 26B summarizes articles at about 70 tokens per second. TranslateGemma 12B translates a 1,200-word article in under a minute. MedGemma 27B handles my family's medical documents. And Qwen 3.8 Flash-Next 125B works on code at about 50 tokens per second, when I can't use the cloud.
- Why it's here this week: on some projects I can't share the materials or the code with any third party. On this server, documents, medical records and the code from those projects stay with me, not in someone else's database.
- Where it falls short: 16 GB of video memory means one model at a time, and even a 125B model is still behind the top cloud models. For code, I wait 5 to 10 minutes per task.
- My verdict: don't look for one model for everything. Pick the right model for each task: small specialized models are where local really wins.
The video: Why I Run 4B and 125B AI Models 24/7
4. MVP idea of the week
A logged-out check for your own app.
- Problem: you can't see your app the way a stranger does. Everything works because you're logged in, and the platform's security scan gives you findings you may not know how to judge.
- Solution: you prove you own the app. The tool opens it as an anonymous visitor, records every database call, tries to read each table with the public key, and reports in plain words: "anyone can read 3,214 rows of profiles, including emails and birth dates." Each finding comes with the rule to fix it.
- For whom: solo founders and small agencies shipping Lovable, Bolt, v0 or hand-made Supabase apps to real users.
- Minimal v1: a command-line tool built on Playwright and Supabase's API that writes a Markdown report, plus a GitHub Action that re-runs it on every deploy. Only for apps you've proven you own.
- Demand check: post the ten-minute manual version on r/Supabase and Indie Hackers, and offer to run it for owners who send their own URL. Count how many do.
- Why now: one crawl found 24,664 such apps, and Lovable itself calls open access rules its most common issue.
5. Useful links
- Crissy Field — Lovable apps expose sensitive data — the full report: how they counted, what they found, and what the numbers don't mean.
- Lovable — Find it, fix it, ship it — what the scan checks on every publish; read the findings before you ship.
- GitHub — secret detection in Copilot code review — flags credentials in pull requests, including ones without a known format.
- Gemini API pricing — on Gemini 4 Carbon or Argon? Your price doubles on December 1.
— Nick
P.S. Outside this newsletter, I help startups and companies build things: products from idea to first release, AI integrations, local or cloud LLM deployments. If you're working on something like that and could use a hand, reply to this email.