Supabase RLS checker
Row Level Security is the switch that decides whether the public anon key can see a table. Supabase puts that key in your browser on purpose. If RLS is off, the key is enough to read the table.
Check it in the dashboard first
Open your project, then the table editor or Authentication → Policies. A table with RLS off is public to anyone who has the anon key, which is everyone who loaded the site.
This SQL lists public tables that still have RLS off. Run it in the Supabase SQL editor on your own project:
select c.relname from pg_class c join pg_namespace n on n.oid = c.relnamespace where n.nspname = 'public' and c.relkind = 'r' and c.relrowsecurity = false;
A policy named “must be logged in” is not enough
using (auth.uid() is not null) lets every account read every row, and anyone can create an account. Prefer auth.uid() = user_id on tables that hold a person's data. A policy of using (true) is the same as leaving the table open.
Enabling RLS with no policies blocks everyone, including your app. Add the policy your screen needs, then test while logged out.
What Plainmend adds
The free scan only notices the project URL and whether a service_role key leaked into the bundle. The live question — does the anon key get rows, and does an empty insert get through — runs after you verify the site. We store a count, not the rows, and we never send the service_role key anywhere.