Is my Supabase database public?
If Row Level Security is off on a table, then yes, anyone with your app's public key can read it, and that key ships in every browser. The only way to be sure is to test it from the outside, which is what this check does.
Test your database now
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 tell if your database is exposed
You cannot tell from inside your app, because your app is logged in or uses the key as intended. The test that matters is an anonymous one: pretend to be a stranger with only the public key, and ask each table for a row.
That is exactly what this check does. If a table returns real rows to an anonymous request, it is public. You will see the table name and its columns as proof, and a fix that turns on the right protection.
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
Can people see my Supabase data without logging in?
Yes, if the table has Row Level Security off. The public anon key is enough to read an unprotected table. Turning on RLS with policies is what limits reads to the right users. Run the check above to see which of your tables are currently open.