I will fix and secure supabase rls policies in your lovable or cursor app

L
lenos_dev
L
lenos_dev
Lenos L.

About this gig

Did Supabase warn you that RLS is disabled or a table is public? Can one user see another user's data? I fix your Row Level Security policies and close the gaps AI coding tools leave behind (Lovable, Bolt, Cursor, Claude Code), then re-test every fix.

AI tools write code that runs, but they often miss what only fails in production: one customer reading another customer's data, secret keys shipped inside the website, credits that break under simultaneous requests, and database writes that fail silently.


I run my own multi-tenant platform on Supabase, and I audit your app against the same 28-point checklist I use on my own system.


What I check:

  • Row Level Security on every table, with no cross-customer reads
  • Keys and secrets exposed in the frontend bundle
  • Auth, roles and permissions enforced on the server, not only in the UI
  • Credits, quotas and counters that are not atomic
  • Storage buckets, webhooks, database functions and rate limits

You get a written report: each finding with a severity, the evidence, why it matters and the exact fix. A sample report is in the gallery.


I work async and in writing, and I never change production without your written approval.

Get to know Lenos L.

Lenos L.

Supabase Audits, Booking System Fixes and AI Voice Agents

  • FromCyprus
  • Member sinceOct 2026
  • Languages

    Greek, English
I find and fix what breaks in apps built with AI coding tools (e.g. Lovable, Cursor, Claude Code) before real users find it: Supabase security gaps, double bookings and calendar sync bugs. I built and run my own AI phone receptionist and booking platform, live in pilot. Before that, I spent 5 years as a Product Specialist for Olympus medical equipment. I work async and in writing: clear reports, focused fixes with tests, and no production change without your written approval.