Lovable security audit
Lovable's Security view checks your configuration. This check signs in as two of your users on the live app and tries to read, change and delete each other's data, then shows you the request, the response and the fix. Five working days after access.
What gets checked on your app
- Lovable Cloud or your own Supabase Every table, view and function behind your app, read as policies, then tested with two real sessions.
- What the built-in scan leaves to you Lovable's docs describe its Quick and Deep scans as checks on configuration and code. They do not describe signing in as two users and trying each other's rows. That is the test this adds.
- TanStack Start or React and Vite New Lovable apps use TanStack Start; older ones are React and Vite. Either way, anything in a VITE_ variable ships to the browser. We search the live bundle for keys that should not be there.
- Edge functions and Stripe Functions that trust an id from the browser, and a webhook that skips the signature check.
What you receive
- The request sent and the response received for every check
- A short video of any request where one user gets another user's data
- Findings ranked by what a stranger could do, each with the fix
- A one-page note of what was tested and what was left out
- One recheck after you apply the priority fixes
- £449 off the fix invoice if the fix starts within 14 days
See a sample report from a real test, or watch the recording of user A reading user B's note.
Questions
Is Lovable's own security scan enough?
It is a good first pass and you should run it. It cannot know whose data is whose in your app, so it cannot tell you whether user A can open user B's records. The two-account test answers that.
Do you need my Lovable login?
No. We need the live URL, read-only access to the GitHub repository Lovable syncs to, and your written permission. We create our own two test users.
What if you find nothing?
The report shows each request and response proving the check ran. If a check in scope has no request and response, you do not pay.
A Lovable app security audit you can run yourself
The method is free. The check is the run, the evidence and the recheck. It is not a penetration test and does not certify the app as safe to launch.
Book before you launch
At checkout, add the app URL and the date you plan to turn on payments or let real users in. After payment, send read-only repository access and the signed permission. Run by David Salami. Full scope on the 5-Day Two-Account Check.