Is Lovable secure?
Lovable apps ship a browser bundle. That bundle often contains the Supabase project URL and the anon key. The anon key is meant to be public. The database is not.
Crissy Field research, discussed on Hacker News on 14 Nov 2026, found that 24,664 of 34,545 Supabase-backed Lovable apps (out of 159,041 analyzed) sent database records on page load without a login. Not every one is a leak. The usual cause is Row Level Security left off, or a policy that uses true for the anon role. UpGuard separately found 16,326 Supabase databases exposing readable tables in September 2026.
A single scan is not enough. The next prompt can regenerate the client and publish a new policy. Ship Sentinel checks again every week and whenever your deploy webhook fires.
What to do
1. Prove you own the domain.
2. Turn on RLS for every table in the exposed schema.
3. Revoke the anon role's table grants where the table is private.
4. Add policies that compare auth.uid() to the owner column.
5. Rotate any service_role key that ever appeared in client code.
The free check on the homepage only reads the public page. The RLS probe runs after verification.
For the logged-out request you can run yourself, see how to check if your Supabase app leaks data.