One key, every row

Why the key in your app’s page can read every row of a Supabase table when row-level security is off.

·

The player loads from YouTube (youtube-nocookie.com) when you press play.

Transcript

Is your Lovable app one of them? Only a check can tell you. One study found over seven thousand Lovable sites where anyone could read email records, no login needed. How? Your app reaches its database with a key in the page. Anyone can copy it. That’s by design.

The key isn’t the lock. Row-level security is: rules for which rows each user gets. If it’s off, or a rule says yes to everyone, one request gets every row: Maya’s, Leo’s and Ana’s. Tables made in Supabase’s dashboard get RLS on. Tables made with SQL need you to switch it on.

Here’s a test project, checked: one table open to anyone. Check yours free. No sign-up, and it reads settings, never your rows. The link is in the description.

Sources

Where the facts in this video come from. Everything shown on screen is a test project with made-up data.

Check your own project for free.

Generate row-level security policies and check a schema for tables left open.

Open the Supabase RLS Generator

More videos

  • Is My App Open? · Part 2 Check yours in 4 steps Check every table in your Supabase project with the free tool. It reads settings, never your rows.
  • Is My App Open? · Part 3 Fix it without breaking your app Turn row-level security on with the right rules in place, so your app’s lists don’t come back empty.
  • Is My App Open? · Full demo Check and fix Supabase RLS, step by step The whole check on a test project: copy the catalog query, read who can reach each table, apply the fixes, generate policies, test as each user and check again.