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

B
bwatsnet
B
bwatsnet
Bryce W.

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.

Bryce W.

Senior engineer: I check, fix and build apps before launch

  • FromUnited States
  • Member sinceMay 2024
  • Languages

    English
I help people who are about to put real users or real money on an app, often one built fast with Lovable, Bolt, Replit or Cursor. I find what could stop a safe launch, like database access rules, sign-in, exposed keys and payments, and I fix it, with a test we agree on first so you can see it worked. I build, fix and harden software for solo founders and teams of every size, at whatever stage you're in. I spent more than a decade as a software engineer at eBay (2013 to 2023), and before that I worked on payments at hyperWALLET.