Skip to main content
Stackbastion

Is your Supabase app leaking data?

Free, no signup. The check runs in your browser. Your project URL, key, table names and results go only to your own Supabase project. We count that a check was run, and nothing else.

Your publishable or anon key. It is already public in your app's code. Never paste a secret or service_role key.

Separate names with commas, spaces or new lines. Up to 25. To list your tables, run this in the Supabase SQL editor:

select tablename, rowsecurity from pg_tables where schemaname = 'public' order by tablename;

What this check does

You enter your project URL, your public key and a list of table names. For each table, your browser sends one GET request to your own Supabase project. It asks for a single row and carries your public key.

The page then reads the response and tells you whether that table returned a row. It never shows, logs or stores the data that comes back. You only see the column names.

What it does not do

This is not a security review. It tests reads made with the public key and nothing else. It does not test logged-in users, writes, storage buckets, database functions or your own API routes.

It only tests the tables you list. A table you leave out is not tested. A result here tells you what those reads returned at that moment, not that the rest of your app is in good shape.

Why the public key matters

Your publishable key, or the older anon key, ships in every visitor's browser by design. Anyone can copy it from your app and send the same requests this page sends.

What stands between that key and your data is row level security, a setting on each Postgres table. If it is off, or a policy is too wide, the public key can read rows. AI app builders sometimes leave it off. Read how to fix row level security.

FAQ

Is it safe to paste my Supabase key here?

Yes, if it is your publishable or anon key. That key is already public: it ships in your app's code to every visitor. This page sends it only to your own Supabase project, from your browser. Your project URL, key, table names and results never reach us. We only count that a check was run. If you paste a secret or service_role key, the page refuses it before any request is made.

Why do I have to type table names?

Since April 2026, Supabase no longer lets a public key list the tables in a project. So the page can't discover them for you. The SQL above the table box lists them in a few seconds.

What does "no rows returned" mean?

Either row level security is blocking the public key, or the table is empty. This page can't tell which. Run the SQL above and look at the rowsecurity column: false means row level security is off for that table.

Does this test writes?

No. It only reads, one row per table, so it can't change your data. It also doesn't test inserts, updates or deletes, so a table that blocks reads can still allow writes.