Why can anyone read my Supabase table?
Because Row Level Security is off on that table. When RLS is off, Supabase lets any request with the public anon key read every row, and that key ships in your app's frontend to every visitor. So 'anyone' really does mean anyone.
This is the default state of a new table until you turn RLS on. It is not a bug; it is a setting that has to be enabled and paired with a policy. Many AI tools build a working app without doing it.
The fix is to enable Row Level Security on the table and add a policy that limits reads to the right users. After you deploy, test again with an anonymous read to confirm the table no longer hands back rows.
Find every table that is currently readable
What it means
Your database tables can be read by anyone, not just logged-in users. Someone could open your app's data — customer emails, orders, private records — without ever creating an account.
Why AI tools cause it
Supabase only protects a table once you turn on Row Level Security (RLS) and write access rules for it. AI tools frequently build a working app without doing that, so the tables are wide open by default.
How xlogs checks it
xlogs finds your public Supabase URL and anon key in your app (the same ones your frontend uses), asks the database as an anonymous user which tables it can read, and flags any that return real rows. Read-only: it never writes or deletes.
How to fix it
The goal: Row Level Security is enabled on every table, with policies so a table only returns rows to users allowed to see them; no table returns private data to an anonymous request.
- Enable Row Level Security (RLS) on every table, especially the affected spot
- Add a policy per table so only authenticated users can read/write their own rows (keep intentionally-public tables public on purpose)
- Re-check that an anonymous request no longer returns private rows
In my app (the spot the scan shows): anyone can read this database table. Please make this true: Row Level Security is enabled on every table, with policies so a table only returns rows to users allowed to see them; no table returns private data to an anonymous request. Steps: Enable Row Level Security (RLS) on every table, especially the spot the scan shows; Add a policy per table so only authenticated users can read/write their own rows (keep intentionally-public tables public on purpose); Re-check that an anonymous request no longer returns private rows. Then tell me exactly what you changed, and do not print any secret values back to me.
Then verify: After you deploy the policies, xlogs repeats the same anonymous read test and confirms the table no longer returns data without a login.
Full step-by-step fix guide, with a copy-paste block for each AI tool →
Common questions
I added a policy but the table is still readable. Why?
Adding a policy does nothing until Row Level Security is actually enabled on the table. Enable RLS first, then the policies take effect. Re-scan afterward to confirm anonymous reads no longer return rows.