Lovable apps expose data: 7,403 sites, passports, 200K chats
Crissy Field scanned 159,041 Lovable projects and found Lovable apps that expose data through open Supabase access rules. Test your app logged out today.
A security firm found many Lovable apps that expose data to anyone who asks the database. Crissy Field, a consultancy in Hamburg, scanned 159,041 Lovable projects. It found passport numbers, payment records and more than 200,000 private chat messages that were readable without a login. If you built a customer-facing app with an AI app builder, do one test today: open it logged out and look at what the database sends.
What actually happened
Crissy Field published the research with updated figures. The firm says the German newspaper Handelsblatt first reported the findings on November 2. The method and the counts:
- The sample. 159,041 Lovable projects found in the Common Crawl web archive, from December 2025 to September 2026.
- The database. 34,545 of them used Supabase. The firm looked at Supabase only. It did not examine Lovable's own database features.
- The open door. 24,664 websites sent database records when the page loaded, with no login. That alone is not a fault. A product catalog is public data.
- The signal. The firm then made more read-only requests with the same public API key. It found email addresses in 10,560 tables on 7,403 websites. That is 30% of the 24,664.
Crissy Field is careful about the 30%. It is not a confirmed leak rate. An email address can be a public contact or test data, and the sample is not representative.
The examples are the important part:
- A German lifestyle forum: more than 80,000 profiles with names, emails and dates of birth, and more than 200,000 chat messages.
- A service provider: more than 1,000 records with passport numbers, expiry dates and nationalities.
- Event organizers and restaurants: tens of thousands of ticket and food orders with phone numbers, addresses and payment information.
- A property manager: AI summaries of internal emails about tenants and owners.
- One provider's archive of 280,000 emails to its customers.
The firm says it retrieved only parts of the datasets and could not establish if anyone misused the data. It describes the cause as access control mistakes that follow recurring patterns.
Lovable did not answer the report on its blog. On November 10 its head of security published a post about scanners that check row-level security policies at publish time, a Fix button and an auto-fix setting. That post says the most common issue is data access rules that are too open, and that users must review the findings.
Why it matters when Lovable apps expose data
A Supabase app talks to the database directly from the browser. The API key in the page is public by design. The only thing between a stranger and your tables is the row-level security policy on each table. If the policy is missing or too wide, the app looks correct and the login page works. The data is still open.
An AI builder makes a working app fast. It does not make you the person who checks the policies. If the app holds customer data, that data is your responsibility under the law, not the builder's.
Do this today:
- Test logged out. Open the app in a private window. Open the browser's network tab. Look at each request to
/rest/v1/. If you see customer rows, you have a problem. - Check each table. In Supabase, confirm that row-level security is on for every table and that each policy names who can read which rows. "Authenticated users can read everything" is not a policy.
- Run the builder's scan, then act on it. A warning that nobody reads is not a control.
- Delete what the app does not need. Passport scans and old chat logs are risk with no benefit.
- Test again after each significant change. A new feature can add a new open table.
Key takeaways
- Crissy Field scanned 159,041 Lovable projects; 34,545 used Supabase
- 7,403 websites had tables with email addresses that were readable without a login
- Exposed examples include 1,000+ passport records, 80,000+ forum profiles and 200,000+ chat messages
- The 30% figure is a signal, not a confirmed leak rate
- Open your app logged out and read the database requests: that test takes five minutes
A prototype becomes a liability on the day it holds real customer data. We audit AI-built apps before launch: access policies on each table, tests as an anonymous user, and a cleanup of data the app must not keep. See how we take vibe-coded apps to production, or send us your app and we will test it logged out with you.
Sources: Crissy Field research, Lovable blog.
- #lovable
- #supabase
- #vibe-coding
- #data-exposure
- #row-level-security
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
TSMC employee data breach traced to a cloud provider
TSMC confirmed an employee data breach in an SEC filing. The leaked data matches records at a cloud service provider. Inventory the HR data your vendors hold.
Read itSignDrop Windows zero-day: SYSTEM access, no patch, no CVE
The SignDrop Windows zero-day uses CLFS and Defender to give a standard user SYSTEM rights. No patch or CVE exists. Keep CLFS authentication on and cut admin rights.
Read it