Browse categories
Explore
Fiverr Pro
English
$
USD
I will secure your supabase database with rls policies for lovable or bolt apps
Maki
About this gig
Built your app with Lovable, Bolt or Replit and about to put real users or client data in it?
The most common hole is the database layer: tables anyone can read with the public key, because row-level security is off or a policy allows everything. I check what a stranger can actually reach, review every table, view and function, and hand you a plain-English report with the exact SQL to fix each finding.
New: from 30 Oct 2026 Supabase stops exposing new tables automatically. Apps then fail with "permission denied for table" (error 42501), and the quick "grant everything" fix can reopen your data. The Basic package fixes this the safe way: row-level security first, then only the grants each role needs.
I never read your users' data: leak checks count rows, they don't open them. I only test apps you own or are authorised to test, with your written OK. This is a point-in-time review, not a guarantee or a certification.
Send me your app URL and tell me which package you need.
Get to know Maki
Maki
Google Sheets, Apps Script and AI Automation
- FromPhilippines
- Member sinceApr 2020
- Last delivery2 years
Languages
English
I automate the spreadsheet and ops work that eats your team's day. 9 years in workforce management, where my Google Sheets and Apps Script automations cut manual reporting time by 50 to 85%. I also build AI agents, Python scrapers and WordPress plugins. Every order ships with working files, a short guide and a walkthrough video. I reply within a few hours (GMT+8). Message me before ordering so we agree on scope.
FAQ
My app shows "permission denied for table" (42501). Can you fix it?
Yes, that is the Basic package. Since 30 Oct 2026 Supabase no longer exposes new tables automatically. I turn on row-level security and a policy first, then grant only what each role needs, so the fix does not open your data to everyone.
Do you need my password or service_role key?
No. The leak check uses only the public key that is already in your app. For the audit and fixes I ask you to invite me to your Supabase project, which you can remove afterwards. Never send passwords or secret keys in chat.
Will you look at my users' data?
No. Leak checks count rows with a request that returns a number, never the rows themselves. Tables, policies and functions are reviewed without opening user records.
What if you find nothing wrong?
You still get the report, listing every check that passed, so you know exactly what was tested. It is a point-in-time review, not a guarantee or a certification.
