Is My Lovable App Leaking Data? What a Scan of 159,000 Projects Found

If your business runs on an app built with Lovable, there’s one question worth answering this week: is my Lovable app leaking data to anyone who asks for it? A new scan suggests that for thousands of apps the answer was yes, and that most of their owners had no idea.

The good news is that this kind of exposure is usually a settings problem, not a rebuild. Here’s what was found, why it happens, and what to ask whoever maintains your app.

What the researchers found

On November 2, the German business daily Handelsblatt reported on an analysis by Crissy Field, an application-security firm in Hamburg. The researchers collected about 159,000 Lovable projects from a public web archive, covering sites crawled between December 2025 and September 2026. Then they checked whether each app’s database would hand over data without anyone logging in.

As reported by several outlets that reviewed the research:

  • About 34,500 of the projects used Supabase, the database service Lovable apps commonly run on.
  • About 24,700 of those returned database records when the page loaded, with no login.
  • On 7,403 sites, those records included email addresses, spread across more than 10,500 tables.

The examples are the kind of data a business can’t afford to lose: more than 1,000 passport records held by one service provider, about 200,000 private chat messages and 80,000 user profiles on one forum, and roughly 280,000 customer emails in one CRM-style app. Reports also mention invoices, contracts, bookings with home addresses, and payment details.

Two cautions from the coverage itself. The researchers looked at a sample, so the share of exposed sites isn’t a confirmed rate for every Lovable app. And the record counts are a floor, not a total. Handelsblatt also reports that Lovable describes this as a problem across the industry, not one limited to its platform.

Why this happens

A Lovable app’s web pages talk to its Supabase database directly, using a public key that is built into the pages. That key isn’t a secret; anyone can see it in their browser. What keeps data private is a database feature called row-level security: rules on each table that decide who may read or change which rows.

Supabase’s own documentation is blunt about what happens without it: anyone holding that public key can read the whole table. So an app can look perfect on screen, with login pages and all, while the tables behind it answer anyone who asks directly.

Lovable has added a security scan and an AI security reviewer that check apps before publishing. Those help, but the scan results suggest warnings don’t catch every case, especially for apps built quickly and then left alone.

Is my Lovable app leaking data?

You don’t need to read code to find out. Ask whoever built or maintains your app to do three things and show you the result:

  1. Run Supabase’s Security Advisor. It’s built into the Supabase dashboard and flags tables that have no row-level security. Ask for a screenshot.
  2. Run Lovable’s security scan on the latest version of the app, and list every warning that is still open.
  3. Try the app logged out. Open it in a private browser window and confirm that no customer names, emails, orders or files appear anywhere.

If any table holding customer, employee or payment data has no row-level security, treat it as exposed until it’s fixed.

The safe fix

The fix is the same pattern we described in our guide to the Supabase “permission denied” change:

  • Turn on row-level security for every table, not just the ones that feel sensitive.
  • Add a policy that matches how the business works: for example, a customer can read only their own orders, and only staff can read all of them.
  • Grant access to logged-in users by default, and only to logged-out visitors where it is truly public, like a product list.
  • Put the rule in the AI tool’s project instructions, so every new table gets row-level security and a policy in the same change.

If a table was exposed, fixing it stops future access but can’t undo past access. Check whether the data includes anything you’re required to protect, such as passport or payment details, and take advice on whether you need to tell customers. If a private key such as the Supabase service key was ever in the app’s pages, replace it; our guide to rotating API keys after a breach covers the order.

What to ask this week

  • When did someone last run Supabase’s Security Advisor on our app, and what did it flag?
  • Does every table that holds customer or staff data have row-level security and a policy?
  • What can a logged-out visitor see?
  • Who checks this again after the next feature is added?

For a quick outside view, our free Forward Scan looks at an AI-built app’s three biggest risks, and database access is one of the first things we check.

Sources

Does your business run on an AI-built app?

Our free Forward Scan is a 20-minute video walkthrough of your app’s 3 biggest risks, delivered in 2 business days.

← All posts

Free
2 days
Get a free Forward Scan