Lovable apps exposed customer data: how to check yours
Researchers found 24,664 Lovable-built sites that sent database records to any visitor without a login. What was exposed and how to check your own app.
On 2 November 2026, the German newspaper Handelsblatt reported that many apps built with Lovable, an AI app builder, expose their data to anyone who opens them. The research came from Crissy Field, a Hamburg security company. Its research report has the latest figures: 24,664 websites sent database records to visitors without a login.
Lovable builds a web app from a description in a chat, without code. If your business made a booking form, a customer portal or an internal tool this way, check who can read its data.
What Crissy Field found in 159,041 Lovable projects
The team examined 159,041 Lovable projects published between December 2025 and September 2026. It found them in Common Crawl, a public web archive. Of these projects, 34,545 used Supabase, a hosted database that Lovable apps can use.
On 24,664 of the Supabase sites, the page sent database records when it loaded, without a login. With the same key, the researchers made more read-only requests. They found email addresses in 10,560 tables on 7,403 sites, about 30% of the 24,664.
The report gives examples of the data:
- more than 80,000 profiles from a German lifestyle forum, with names, email addresses, birth dates and gender, and more than 200,000 chat messages
- tens of thousands of ticket and food sales records from event organizers and restaurants, with contact details, payment information and ticket codes
- more than 1,000 records from a service provider with passport numbers, expiry dates and nationalities
- contracts, invoices, AI summaries of internal emails and WhatsApp messages
What the figures do not prove
The researchers say that "the 30% figure should therefore not be read as a confirmed data leak rate". Some addresses can be public contact details or test data, and the sample is not representative of all Lovable apps.
The study did not examine the database features that Lovable added in late 2025. Techzine reports that nobody could find out if the data was misused. Its article has no statement from Lovable.
Why a Lovable app can expose its database
The report describes the cause as recurring access control mistakes. Techzine calls it "poorly configured Supabase databases".
The page that a visitor loads contains a public key for the Supabase database. The key is safe only when the database has rules that limit what each visitor can read. Supabase calls these rules Row Level Security (RLS). The Supabase documentation says: "Enable RLS on every table in an exposed schema." With RLS on, no data is available through the public key until you create policies. On many projects, a new table without RLS gives every privilege to all roles, the public one included.
According to Lovable's documentation, a Quick scan runs on every publish and flags tables without per-record access control and rules that let everyone through. The documentation says: "Misconfigured RLS rules are a common cause of data leaks." A Deep scan of all code does not run automatically.
Lovable's documentation puts the responsibility on the customer: "You are responsible for ensuring that your app meets the security requirements appropriate for its use case." Crissy Field notes that the terms say the same, while the marketing says no technical knowledge is necessary.
What to do this week
- 01List every app that your business built with Lovable or a similar AI builder.Include test versions and apps on staff accounts.
- 02Run a Deep scan from the Security view of each Lovable project.Fix every critical finding, then turn on the workspace setting that blocks publishing while critical issues are open.
- 03Open the Supabase dashboard of each app and confirm that RLS is on for every table.A table with RLS off, or with a policy that allows everyone, is open.
- 04Open the app in a private browser window, without a login.Customer data on the screen means the app is open; a clean screen does not replace step 3.
- 05If customer data was open, get legal advice.In the EU, under Article 33 of the GDPR, a controller must report a personal data breach to the supervisory authority within 72 hours, unless the breach is unlikely to put people at risk.
- 06Before an app holds real customer data, have a qualified person review the access rules.Crissy Field says that "automated checks are no substitute for a professional security assessment". For a wider baseline, see our article on the NIST small business cybersecurity guide.