When to use it
Before you share your app with anyone, and after any big change to your data. If your app uses Supabase, the key in your app’s code (the anon or publishable key) is meant to be public. Only Row Level Security keeps your users’ data private, and a table without it can be read by anyone.
What to check afterwards
The before-and-after list is the point of this prompt. Read it. Then test it yourself:
- Open your app in a private window without logging in. You shouldn’t see any user’s data.
- Create two test accounts. Logged in as one, you shouldn’t see anything belonging to the other.
- Check that tables nobody should write to, like settings or prices, can’t be changed by normal users.
If it doesn’t work
Some features may stop working once the rules are on, often because they were quietly relying on anyone being able to read the table. That’s a sign the rules are working. Tell the builder which feature broke and ask it to fix that feature, not to turn Row Level Security off.
The full background is in our guide: Is your vibe-coded app leaking data? 5 things to check.