LeakPatrol › Guides

Lovable data exposure study: is your app one of the 24,664?

By LeakPatrol · Updated 20 November 2026

In November 2026 the Hamburg security firm Crissy Field reported that it had looked at 159,041 apps built with Lovable. On 24,664 of them, the page sent records from the app's Supabase database to anyone who loaded it, without logging in. Press reports (for example Techzine) say that on 7,403 of those sites, the same public key could also read tables containing email addresses. Reported examples include private chat messages and passport details. If you built something with Lovable, here is how to tell whether yours is affected, without waiting for someone else to find it.

What actually went wrong

A Lovable app talks to Supabase straight from the browser, using the anon key. That key is meant to be public. What protects your data is Row Level Security (RLS): rules on each table that say who may read or change which rows. When a table has RLS off, or has a policy like using (true) for reading, anyone with the public key, which means anyone who opens your site, can read the whole table. This is not a secret key leak. It is a missing lock on the table.

Some caveats from the reporting: the sample came from a public web archive, so it isn't every Lovable app, and not every table it reached held private data. A public list of blog posts is fine. A table of users, messages or orders is not.

The 5-minute test

  1. Open your live app in a private browser window, logged out.
  2. Press F12, open the Network tab, filter by rest/v1 and reload.
  3. Click each request and look at the Response. If you see other people's emails, names, messages, orders or anything you wouldn't put on your homepage, that table is open.
  4. In Supabase, go to Database → Tables. Any table with an "RLS disabled" label (or "Unrestricted" in the Table Editor) is readable by anyone with your public key, even if your app never shows it.
  5. Then open Authentication → Policies and look for SELECT policies with true as the condition on tables that hold personal data.

Logged-in users can see more than strangers, so repeat step 3 while logged in as a test user and check you only get your own rows.

How to fix it

-- 1. Lock the table (nothing is readable until a policy allows it)
alter table public.messages enable row level security;

-- 2. Let people read only their own rows
create policy "Users read own messages"
on public.messages for select
to authenticated
using ( (select auth.uid()) = user_id );

-- 3. Same idea for insert / update / delete
create policy "Users write own messages"
on public.messages for insert
to authenticated
with check ( (select auth.uid()) = user_id );

Turning RLS on with no policies blocks everything, so your app may suddenly show empty lists. That is expected: add the policies, then test again. If you get stuck, see why a select returns an empty array and "new row violates row-level security policy".

A prompt to paste into Lovable

Audit my Supabase database security:
1. List every table and whether Row Level Security is enabled.
2. Enable RLS on every table in the public schema.
3. For tables with user data, add policies so users can only
   read and change rows where user_id = auth.uid().
4. Remove any policy that uses "true" on a table with personal
   data, unless that data is meant to be public.
5. Show me the SQL before running it.

If your data was exposed

LeakPatrol's free scan runs a read-only, logged-out check of your live app: it looks for Supabase tables your public key can read, leaked secret keys and public files, and shows you the fix for each one. It takes about a minute. Only scan apps you own.

Check your app in a minute

Free, read-only, no sign-up. Every problem comes with a plain-English fix and a prompt for your AI tool.

Get the 10-point checklist

Every check we run on AI-built apps, with how to do each one yourself. Straight to your inbox.

Questions

What did the Lovable data exposure study find?

The security firm Crissy Field reported that 24,664 of 159,041 Lovable apps it examined sent Supabase database records to visitors without a login, and press reports say 7,403 of those exposed tables with email addresses.

Is the Supabase anon key in my Lovable app a leak?

No. The anon key is meant to be public. Your data is protected by Row Level Security policies on each table, so the fix is to turn RLS on and write policies, not to hide the anon key.

How do I check if my Lovable app exposes data?

Open the app logged out, watch the Network tab for rest/v1 requests, and check whether any response contains data that belongs to other users. In Supabase, look for tables with RLS disabled.

Will enabling RLS break my Lovable app?

Turning RLS on without policies blocks all access, so lists may go empty. Add policies that let users read their own rows, then test again.

More guides