Supabase RLS checker
Your Supabase public key sits in your app's JavaScript, so anyone can use it. Row Level Security (RLS) is the only thing that decides what a stranger can read with it. Paste your app link and we test it the way a stranger would, read-only. We count rows, we never download them. The free scan finds the project and any secret key in your code; after you verify you own the app, the table and bucket checks run free too.
The 5 most common RLS problems
A table with personal or payment data that anyone can read
With only your public key, a stranger can count the rows of a table named like users, profiles, orders, payments or messages. That means RLS is off or too loose on it. Runs after you verify you own the app. We only count rows.
A Supabase secret or service_role key in your browser code
These keys skip RLS completely. If one is in the JavaScript your visitors download, the whole database is open. The free scan checks this.
Any other table that anyone can read
The same test for every other table we can find in your project and in your site code. Rated high. Runs after you verify.
A storage bucket that lists its files to strangers
A bucket named in your site code answers a file listing without login. Runs after you verify. We never open the files.
Storage buckets that can be listed
Strangers can see the names of your storage buckets. Check nothing private is publicly readable. Runs after you verify.
How to fix them
- 01Run the free scan, then verify you own the app (about a minute) so the table and bucket checks can run.
- 02For every table we name, turn on RLS in Supabase and add a policy that only lets each user see their own rows.
- 03If a secret or service_role key showed up in your code, make a new one in Supabase and keep it on the server only.
- 04Scan again. A table that no longer answers a stranger is gone from the list.
Doesn't Supabase's Security Advisor already check this?
Supabase's Security Advisor lists RLS warnings from inside your project. Greenlight Scan checks from the outside, the way a stranger would, with only your public key, and shows what actually answers. Use both.
Full comparison →Questions
Do you read my data?
No. For tables we only ask Supabase how many rows a stranger could see. No row is downloaded. For buckets we only check whether a file listing is possible.
Do you need my Supabase login?
No. We only need your app's public web address. The Supabase address and public key are found in the code your site already sends to every visitor.
Which checks need me to prove I own the app?
The table and bucket checks. They run after you add a small marker to your site, and then they are free. Before that the free scan only reads what any browser downloads.
Does a clean result mean my database is safe?
No. It means a stranger with your public key could not read the tables we found. We can only test tables we can find, and we do not test what a signed-in user can see of another user's data. Row Level Security is still worth reading about.