I will fix supabase row level security so each user sees only their own data


About this gig
About to put real users on a Supabase app? If its row-level security is off or too loose, one signed-in user can read or change another user's data. I lock it down, with proof.
I turn the rules on and write them for every table that holds user data, tighten your file storage rules, and check database functions that skip the rules. Then I prove it: a test run as two test users shows user B reading or changing user A's rows before the fix and getting refused after it. You approve what "fixed" means before I start.
Basic: up to 6 tables. Standard: up to 9. Premium: up to 12.
I work from a test copy or test accounts, never your real users' records. You get the changes as a migration, with steps to apply and undo it. If you keep building in Lovable or Bolt, I make the changes so they sync back, or I tell you before I start if they can't, and you can cancel for a full refund.
If a fix fails its agreed test on the version I handed over within 90 days, I fix it free. In late 2025 I built a new TypeScript and Supabase back end for PetConnect, with row-level security rules and tests.
Get to know Bryce W.
Senior engineer: I check, fix and build apps before launch
- FromUnited States
- Member sinceMay 2024
Languages
English
Other Software Development Services I Offer
FAQ
What if my app has more than 12 tables?
Message me first. I'll send a custom offer before you order, and you don't pay until you've agreed.
Will this break my app?
It can, if part of the app relied on the open rules. That's why I test on a copy first and check the pages that read data before handing over. If a fix fails its agreed test on the version I handed over within 90 days, I fix it free.
Already bought my Launch Blocker Check here?
Order this within 14 days of my Launch Blocker Check list and the $150 comes off. Message me and I'll send a custom offer at the lower price.
Do you need my live database?
No. A test copy of your Supabase project (a separate project or branch), or an invite to that copy with the narrowest role that can change policies, is enough. I never touch real users' records.
What happens to my code?
I keep it confidential. My AI coding tools (Claude Code and Codex) read it with their training settings off, never your production database or users' records, and I delete my copies when we're done, except a shared Codex history on my computer that I can't clear per project.
What if it's not a fit?
Message me before you order. If you order before we've confirmed fit and it doesn't fit, I'll cancel it for a full refund.
