Is my Lovable app secure?
Lovable, Bolt, Cursor, and Replit will happily ship a working app with the database wide open. The app looks done. The data is sitting on a public API. Here is a pass you can do on your own project before you send the link to customers.
- Open the live URL with https://. If the browser warns about the certificate, stop and fix that first.
- View source and search for service_role, sk_live_, and sk-proj-. None of those should appear. The anon key may appear. That part is normal.
- In Supabase, open each table that holds users, messages, orders, or files. Turn on Row Level Security. Add a policy that matches the signed-in user, not “anyone who is logged in”.
- Try your own logged-out browser on a page that should be private. If the data is still there, the check is in the client only. Move it to the database policy or a server route.
- Visit yourdomain/.env and yourdomain/.git/config. Both should fail. A download means the project files were published.
- Add the usual headers: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options. Hosts and frameworks all have a header setting. The report names the ones that are missing.
Plainmend runs the public half of this list in one pass and writes the fix as a prompt. The database half runs after you prove the site is yours, because that request should not be aimed at a stranger's project.
A clear report is a good sign and not a certificate. Apps that take payment or store private data still deserve a human look.