If you are shipping AI-generated apps on Lovable, your database configuration might be wider open than you think. Security firm Crissy Field, in collaboration with Handelsblatt, analyzed 159,041 Lovable projects scraped from Common Crawl data between December 2025 and September 2026. The findings are sobering for builders relying on Supabase defaults: of the 34,545 projects using Supabase, 24,664 were sending records immediately upon page load without requiring authentication. While some public data is expected, the audit identified that 30% of these sites (7,403 projects) exposed tables containing email addresses to anonymous read-only requests.

The Root Cause: RLS and Grant Misconfigurations

The vulnerability stems from how Supabase handles permissions by default. A frontend communicates with the database using a public key, but privacy relies entirely on Row Level Security (RLS) and precise grants. Supabase documentation explicitly states that a table in an exposed schema without RLS is readable and writable by any role with a grant. In many Lovable-generated projects, the 'anon' role (representing signed-out visitors) and 'authenticated' role receive full privileges on new public tables automatically. Adding RLS policies does not automatically revoke these existing grants, leaving a backdoor open for anyone with the public key to query sensitive tables like forum profiles, chat messages, and even identity document details.

A Three-Step Security Check for Builders

Developers need to move beyond the 'it works on my machine' mindset and audit their Supabase instances immediately. First, enable RLS on every exposed table using alter table public.orders enable row level security; in the dashboard or SQL editor. Second, write specific policies that restrict access, such as create policy "Users read own orders" on public.orders for select to authenticated using ((select auth.uid()) = user_id);, and critically, revoke all privileges from the anon role for sensitive tables using revoke all on public.orders from anon;. Third, test your application in a private browser window without logging in to verify what data loads, ensuring you never expose the service_role key in the frontend, as it bypasses RLS entirely.

Key Takeaways

  • 34,545 of 159,041 Lovable projects use Supabase, with 24,664 sending data without login.
  • 30% of those Supabase sites (7,403) exposed email addresses to anonymous users.
  • Default Supabase grants often give 'anon' full access unless explicitly revoked.
  • Lovable's terms place responsibility for data handling and security on the customer.
  • A simple private window test can reveal if your app is leaking data to the open web.

The Bottom Line

AI app builders accelerate development but often ship insecure defaults. If you are handling customer emails or payments, do not trust the generator's configurationβ€”audit your RLS policies and grants today, because an easy builder is no excuse for an easy leak.